Red Hat NETWORK 3.6 - CHANNEL MANAGEMENTT GUIDE Manual

Also see for NETWORK 3.6 -: Configuration guide Reference guide

Contents

Red Hat NETWORK 3.6 - CHANNEL MANAGEMENTT GUIDE Manual Manual pdf 25 page image

Chapter 6.Uploading and Maintaining Custom PackagesDepending upon which Red Hat Network service is used, there are two different mechanisms foruploading packages to private channels.Customers of the RHN Proxy Server will use the RHN Package Manager application, which sendspackage header information to the central Red Hat Network Servers and places the package itself intothe local repository of the RHN Proxy Server from which RHN Package Manager is invoked.Customers of the RHN Satellite Server will use the RHN Push application, which sends packageheader information to the local RHN Satellite Server and places the package into the local repositoryof the RHN Satellite Server from which RHN Push is invoked.This chapter discusses both of these tools in detail.WarningRemember, customers using both RHN Proxy Server and RHN Satellite Server should be using onlythe RHN Push because this combination requires custom packages and channels be uploaded to theSatellite only. From there, the Proxies will obtain the packages and distribute them to client systems.6.1. Uploading Packages to RHN Proxy ServerThe RHN Package Manager allows an organization to serve custom packages associated with a pri-vate RHN channel through the RHN Proxy Server. If you want the RHN Proxy Server to update onlyofficial Red Hat Enterprise Linux packages, you do not need to install the RHN Package Manager.To use the RHN Package Manager, install the rhns-proxy-package-manager RPM packageand its dependencies. This package is available to registered RHN Proxy Server systems and may beinstalled by running up2date rhns-proxy-package-manager.Only the header information for the packages is uploaded to the RHN Servers. The headers are re-quired so that RHN can resolve package dependencies for the client systems. The actual package files(*.rpm) are stored on the RHN Proxy Server. For this reason, custom packages cannot be downloadedthrough the RHN website, although they are listed. They must be retrieved by the client system usingup2date.6.1.1. Configuring and Using the RHN Package ManagerNoteIt is recommended that at least one private channel be created to receive custom packages prior toupload, since a channel is required for systems to obtain the packages.The following command uploads the package headers to the RHN Servers and copies the packages tothe RHN Proxy Broker Server:rhn_package_manager -c label_of_private_channel pkg-list