Show Table of Contents
2.4. Tools, Repositories, and Practices
Before creating and managing channels, note the differences between the various tools and repositories at your disposal. This is especially important when deploying both an RHN Satellite Server and RHN Proxy Server, as this increases the utilities and storage locations available. Furthermore, a Proxy-Satellite combination offers certain best practices for optimal performance.
First, become familiar with these package management tools:
- RHN Package Manager - Use this to push custom packages into custom channels on your RHN Proxy Server.
- RHN Push - Use this to push custom packages into custom channels on your RHN Satellite Server.
- RHN Satellite Synchronization Tool - Use this to import and synchronize standard packages from Red Hat Network Classic to the RHN Satellite Server with Red Hat Network. This is done via the Internet or CD/DVD ISO images.
Each of these tools has a corresponding package repository. Both RHN Package Manager and RHN Push require the creation of a temporary staging directory for placement of custom packages that are uploaded to the Proxy or Satellite. Delete these staging directories after use.
Note
Red Hat recommends archiving custom packages externally from Red Hat Network.
When using both RHN Proxy Server and RHN Satellite Server, use only RHN Push and RHN Satellite Synchronization Tool. The Proxy-Satellite combination requires custom packages and channels be uploaded to the Satellite only. From there, the Proxy obtains the packages and distributes them to client systems.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.