Bug 1706244

Summary:	[RFE] "Ansible Guide" as we have "Puppet Guide"
Product:	Red Hat Satellite	Reporter:	Waldirio M Pinheiro <wpinheir>
Component:	Documentation	Assignee:	Shweta Naresh <sjalgaon>
Status:	CLOSED DEFERRED	QA Contact:	satellite-doc-list
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.4.2	CC:	dvoss, mawerner, rbertolj, ryandeussing, sjalgaon
Target Milestone:	Unspecified
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	new-title
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-10-18 14:57:27 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Waldirio M Pinheiro 2019-05-03 21:26:16 UTC

Document URL: 
New document (Ansible Guide)


Section Number and Name: 

Describe the issue: 
Currently, we don't have a great document to help the customer from the beginning as we can see on Puppet Guide (https://access.redhat.com/documentation/en-us/red_hat_satellite/6.4/html-single/puppet_guide/index)

Suggestions for improvement: 
Create a new guide (Ansible Guide) and on this one, we can show:
- How to create a basic role that will:
	Examining the Anatomy of an Ansible Role
	Setting up a Ansible Role Development environment
	Generating a New Role Structure
	Installing a HTTP Server
	Running the HTTP Server
	Configuring the HTTP Server
	Configuring the Firewall
	Configuring SELinux
	Copying a HTML file to the Web Host
	Finalizing the Ansible Role

The content related to turn the ansible role available, we have already, should be just removing from the another document to this guide.

Additional information:

Comment 2 dvoss 2019-05-06 12:33:55 UTC

Thank you for raising this bug.

This is a quick note to acknowledge the bug. We are currently evaluating it and looking to see how we can fit this into our schedule. 

Kind regards,

David

Comment 3 dvoss 2019-05-06 12:34:43 UTC

Hi Karie,
Given the 6.6 documentation scope is almost locked down, perhaps we can see what we can do to tackle this adhoc or as part of 6.7.

Comment 5 Karie 2019-05-07 12:47:21 UTC

David

This is a great topic and needs to be fleshed out more. We need to decide how much information needs repeating from the Ansible documents. The best solution would be is we couls start reuse. We need to start investing the compatibility of tools. 

Let's add a investigation and planning line item for 6.6 (which would fall to  me) and then start implementation in 6.7 if possible.

Karie

Comment 6 Waldirio M Pinheiro 2020-07-20 18:01:32 UTC

Hello friends,

Any information or deadline about this reqeust?

Thank you!