Installation guide

/sbin/service taskomatic stop
You may us e custom scripting or other means to establish automatic start-up/failover of the RHN
Task Engine on the secondary Satellite. Regardless, it will need to be started upon failover.
7. Share channel package data (by default located in /var/satellite) between the Satellites over
some type of networked storage device. This eliminates data replication and ensures a consistent
store of data for each Satellite.
8. Share cache data (by default located in /var/cache/rhn) between the Satellites over some
type of networked s torage device. T his eliminates data replication and ensures a consistent store
of cached data for each Satellite.
9. Make the various Satellites available on your network via Common Name and a method suiting
your infrastructure. Options include round-robin DNS, a network load balancer, and a reverse-
proxy setup.
8.7. Changing the Satellite Hostname
If you need to change the hostname or IP address of your Satellite server, the satellite-utils
package contains the satellite-hostnam e-renam e script.
To use the satellite-hostnam e-renam e s cript, you must first ensure that you know your SSL CA
passphrase by performing the following command:
openssl rsa -in path/RHN-ORG-PRIVATE-SSL-KEY
Then enter passphrase when prompted.
satellite-hostnam e-renam e requires one mandatory argument, which is the IP address of the
Satellite server, regardless of whether the IP address will change along with the hos tname or not.
The usage of satellite-hostnam e-renam e is as follows:
spacewalk-hostname-rename <ip address> [ --ssl-country=<country> --ssl-
state=<state>\
--ssl-org=<organization/com pany> --ssl-orgunit=<departm ent> --ssl-email=<em ail
address> --ssl-ca-password=<password>]
If there is a need to generate a new SSL certificate, all necessary information will be as ked interactively
via series of prompts, unles s options are pas sed at the command-line (as in the above example). When
the system hostname has not changed, the regeneration of a new SSL server certificate is not
necessary. However, if at least one SSL option is specified, then satellite-hostnam e-renam e will
generate a certificate.
For more information about using satellite-hostnam e-renam e, refer to the following Red Hat
Knowledgebase entry:
https://access.redhat.com/kb/docs /DOC-32318.
8.8. Conducting Satellite-Specific Tasks
Using a RHN Satellite is quite s imilar to using the hosted version of Red Hat Network. For this reason,
you should consult the RHN Reference Guide to obtain detailed instructions to standard tasks, such as
editing System Profiles and updating packages. Tasks directly related to managing custom channels
and Errata are covered in the RHN Channel Management Guide. T his section seeks to explain activities
available only to Satellite customers.
8.8.1. Deleting Users
Becaus e of the isolated environment in which RHN Satellites operate, Satellite customers have been
granted the ability to delete users. To acces s this functionality, click Users in the top navigation bar of
the RHN website. In the resulting User List, click the name of the user to be removed. This takes you to
the User Details page. Click the delete user link at the top-right corner of the page.
Figure 8.1. User De let ion
A confirmation page appears explaining that this removal is permanent. To continue, click Delete User
at the bottom-right corner of the page.
Note
The Organization Administrator role must be removed from the user's profile before deleting the
user from the RHN Satellite. Failing to do so causes the delete operation to fail.
The Organization Administrator role may be removed by any Organization Administrator
(provided they are not the sole Organization Administrator for the organization) by clicking on the
Users tab and then visiting the Details sub-tab.
Red Hat Network Satellite 5.4 Installation Guide
38