Red Hat Bugzilla – Bug 101199
Satellite Installation docs improvement - continued
Last modified: 2009-08-19 23:03:26 EDT
Description of problem: This bug is being created to track the tasks deferred from feature 98103 (Documentation Requirement to enable user install) in the 2.6.0 release: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=98103 In a nutshell, these are the outstanding changes: * Address Proxy/Sat. combos in setup (SSL certs.) and use (channels) * Attempt to better define the three package repositories and management tools, as this will require altering several docs * Recommend use of Activation Keys for client registration * Provide best practices about creating custom channels for staging and developing user groups based upon function, area of expertise, etc. * Describe Sat. installs over SSH to satsisfy bug 81183 * Provide recommendations for use of specific custom channels for staging and testing In addition to the Satellite Installation Guide, these changes will likely affect the Client Configuration and Channel Management guides. A similar bug will be created to track Todd's many suggested changes to the Proxy Installation Guide.
Here is a cross reference to the Proxy Guide bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=101200
I've made the following changes: Satellite Installation Guide * Added Example Topologies chapter containing suggested architectures, including Proxy-Sat. combinations * Added example of rhn.conf Client Configuration Guide * Added a Registering with Activation Keys section to the Client Applications chapter recommending use of keys * Added a Sharing certificates section to the SSLCertificates chapter explaining how to use a single pair across an organization, including with Proxy-Sat combos Channel Management Guide * Added recommendation for creating beta channels for staging of new custom packages * Added Tools, Repositories, and Practices section to the Intro describing the three primary package management tools (such as rhnpush) and the related repositories. This section also states that custom channels and packages in a Proxy-Satellite environment must be uploaded only to the Satellite. * Added a similar Warning regarding packages in Proxy-Sat combos to the Uploading chapter I'm now distributing to Todd for his review.
Incorporated Todd's input. The docs are in CVS.
Looks good.
Docs looks good in prod.