Red Hat Bugzilla – Bug 846691
Confusing and inconsistent references to Satellite vs RHN Hosted/Classic
Last modified: 2015-05-11 18:08:31 EDT
Those familiar with the product know that RHN Satellite is intimately connected with RHN Hosted (and specifically what is currently known as RHN Classic). However, the RHN Satellite documentation shows this relationship too strongly at times, with confusing references to RHN (with the implication of RHN Hosted) instead of Satellite.
Note that we (Red Hat) have often meant "RHN Hosted" when we say "RHN"; this is supported by the Guide itself, see the screenshot in Figure 2.3 for example where it states "You may connect your system to Red Hat Network (https://rhn.redhat.com/) or to a Red Hat Network Satellite" (i.e. an either/or relationship). However, the Guide often uses "RHN" as a synonym for "RHN Satellite". In general, I would strongly suggest that terminology is used more consistently, for example:
RHN: used sparingly to refer to the whole network and system for delivering updates
RHN Hosted: the Red Hat-hosted version, rhn.redhat.com (now RHN Classic)
RHN Satellite: the customer's satellite server.
The majority of references to "Red Hat Network" would benefit from being made more specific and using the appropriate term. This is all the more important since what was RHN (now RHN Classic) has undergone significant changes over time.
Repeated references to the document itself as the "RHN Reference Guide" instead of the "RHN Satellite Reference guide". Example in the Introduction: "Welcome to the Red Hat Network Satellite 5.4 Reference Guide. The RHN Reference Guide guides you through registering systems with Red Hat Network and using its many features."
(should be: "Welcome to the Red Hat Network (RHN) Satellite 5.4 Reference Guide. The RHN Satellite Reference Guide guides you through registering systems with your Red Hat Network Satellite server..."
Section 1.1: talks about buying subcriptions for the Update entitlement from a URL that no longer exists and in a way that is inappropriate for Satellite-managed systems
Section 1.2: talks about creating RHN accounts to entitle systems for subscriptions on rhn.redhat.com instead of on Satellite.
Section 1.6: "Your System Profile, available at http://rhn.redhat.com...". Should clearly be a reference to the Satellite web interface.
Section 2.1: discusses registering to RHN Hosted. again, this is the *Satellite* guide so it should not do this, instead it should guide the user to register to Satellite specifically.
Section 4.2.1: talks about entering a "Red Hat username and password". This is potentially highly confusing since many Satellite users (at least administrators) will typically have both Red Hat (RHN Hosted/redhat.com) logins and Satellite logins. We should be really clear that we are talking about *Satellite* usernames and passwords.
Section 5.4: refers to troubleshooting a client connected to Satellite by connecting to xmlrpc.rhn.redhat.com.
Section 7: a large portion (although, confusingly, not all) refers to RHN Hosted instead of RHN Satellite, with some confusing text e.g. section 7.1 "...only RHN Satellite customers see the Monitoring and Admin tabs" - well, this is the Satellite reference guide so that note is not necessary.
Searching for "Red Hat Network" and "rhn.redhat.com" in the document shows *many* more examples.
For the Satellite 5.5 docs/release, we have made some effort on this. I'm assigning to docs for review, to see if any of this was overlooked and if they can act on it (I think we may have time still).
I should note though, that we do not have resources to re-vamp the Reference Guide totally, just specific points of pain/error. We did though re-write the Satellite Installer Guide, so that should be a lot better/consistent.
Moving back to assigned, to be addressed in v.next.
Standardized all mention of RHN Satellite as Red Hat Satellite and checked that most content would point towards Satellite and not Hosted.
Satellite 5.6 Documentation is published, as part of the 5.6 release and can be found here:
Closing this bug out. Please open a new bug, if there is further issues/concerns with the Satellite Documentation.