Bug 1134129

Summary: [doc] how to get started with Config Mgmt /using Puppet
Product: Red Hat Satellite Reporter: Xixi <xdmoon>
Component: DocumentationAssignee: Dan Macpherson <dmacpher>
Status: CLOSED CURRENTRELEASE QA Contact: Russell Dickenson <rdickens>
Severity: high Docs Contact:
Priority: high    
Version: 6.0.3CC: adstrong, ahumbe, aupadhye, bhamrick, bkearney, chorn, daobrien, hhudgeon, istvan.cebrian, jalviso, michele, mmccune, nerawat, nshaik, pdwyer, sudo, xdmoon
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-10-25 13:11:22 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:
Bug Depends On:    
Bug Blocks: 1115190    

Description Xixi 2014-08-26 22:51:01 UTC
Description of problem:

Satellite 6 Documentation is missing documentation on Configuration Management: overall process, steps to perform config content creation and deployment from start to finish, so customers can start using the functionality.  

Suggested topics include:

- How to build module from scratch for any custom configuration file?
^^ Understandable we're not going to provide developer support on how to write Puppet modules, however just like kickstarts, cobbler, API and other functionalities we ship, should include basic how-to get started tips and key information, and reference upsream documentation such as https://docs.puppetlabs.com/puppet/latest/reference/modules_fundamentals.html which is also used in the SOE Guides 

- How to upload and publish existing Puppet modules or import from GIT repo
Can re-use content from [1] and [2] 

- Making changes or adding content to existing configuration files.

- How to deploy config content on client system during provisioning
Can re-use some from existing docs

- How to deploy config content on client system registered to Satellite after kickstart i.e. outside of provisioning
This is a docs gap right now, though some in the works

- Client/server side configuration for config management.
Key configuration both on server side and client system side, what user needs to install/setup/configure, what config options they may need to tweak and what not to touch

[1] https://access.redhat.com/articles/1169613 Red Hat Satellite 6: Core Standard Operating Environments (SOE) Recommended Practices
[2] https://access.redhat.com/articles/1138393 Red Hat Satellite 5 and 6 Puppet Guide

Version-Release number of selected component (if applicable):
Satlelite 6.0.3 (Beta/pre-GA)

How reproducible:
always

Steps to Reproduce:
1. (see above)
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 RHEL Program Management 2014-08-26 22:52:58 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 3 Xixi 2014-08-26 22:55:36 UTC
created kbase Solution https://access.redhat.com/solutions/1173803 "Satellite 6 Beta Configuration Management Quick Start Guide" in the meantme based on [1] and [2]

Comment 6 Athene Chan 2014-08-27 21:50:49 UTC
Thanks Xixi, I'll put it in for potential 6.1 or post-GA docs!

Comment 9 Bryan Kearney 2015-04-14 22:06:34 UTC
I have provided the info I wanted.

Comment 11 RHEL Program Management 2015-04-21 16:10:41 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 13 Hayley Hudgeons 2015-06-09 16:50:40 UTC
*** Bug 1226181 has been marked as a duplicate of this bug. ***

Comment 15 Hayley Hudgeons 2015-06-18 17:38:21 UTC
*** Bug 1225166 has been marked as a duplicate of this bug. ***

Comment 16 Magnus Glantz 2015-06-18 20:27:13 UTC
If you like customer feedback, I hereby raise my hand. I have both Satellite 6 and Puppet based SOEs.

Comment 17 David O'Brien 2015-06-22 02:49:30 UTC
(In reply to Magnus Glantz from comment #16)
> If you like customer feedback, I hereby raise my hand. I have both Satellite
> 6 and Puppet based SOEs.

Hi Magnus

Yes PLEASE :-)

Feedback is very welcome on any and all aspects of this. The beta version is here:

https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html/Puppet_Guide/index.html

We'll be developing this further as we move to GA and beyond so the more customer feedback we get the better.

Thanks again.
David

Comment 20 Dan Macpherson 2015-08-24 05:59:52 UTC
Request from Ashish Humbe:

Thank you for the Puppet Guide for Sat6.1 which is really good. Here I
see that we have steps to deploy modules on host built from satellite
but the missing part is to deploy puppet modules on the system which is
already installed. I had a customer case requesting these steps in the
guide.

Can we add them to the guide? Should I create new bz for it?

Comment 22 Dan Macpherson 2015-08-27 17:57:49 UTC
These instructions have been added to the Puppet Guide and pushed to the devel server:

http://documentation-devel.engineering.redhat.com/site/documentation/en-US/Red_Hat_Satellite/6.1/html/Puppet_Guide/sect-Red_Hat_Satellite-Puppet_Guide-Client_and_Server_Settings_for_Configuration_Management-Configuring_Puppet_agent_on_Provisioned_Systems.html

Just to note, these instructions are pretty much the same instructions from the User Guide.

Comment 30 Bryan Kearney 2015-10-25 13:11:22 UTC
his was delivered in the October Async drop. I am moving this to closed/currentrelease. If the customer is still seeing issues please feel free to re-open or ot open new bugs with the specific issues.

Comment 31 Bryan Kearney 2015-10-25 13:11:47 UTC
his was delivered in the October Async drop. I am moving this to closed/currentrelease. If the customer is still seeing issues please feel free to re-open or ot open new bugs with the specific issues.