Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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 1RHEL 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.
(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
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?
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.
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.