Red Hat NETWORK SATELLITE 5.1.1 Installation Manual

Also see for NETWORK SATELLITE 5.1.1 - RELEASE NOTES: Release note Reference guide

Contents

Red Hat NETWORK SATELLITE 5.1.1 Installation Manual Manual pdf 48 page image

Chapter 6. Importing and Synchronizing441.Populating the tables describing common features for channels (channel families). This can also beaccomplished individually by passing the --step=channel-families option to satellite-sync.2.Creating a particular channel in the database and importing the metadata describing the channel.Individually, use the --step=channels option.3.Moving the RPM packages from the temporary repository into their final location. Individually, usethe --step=rpms option.4. Parsing the header metadata for each package in the channel, uploading the package data, andassociating it with the channel. Individually, use the --step=packages option.5.Identifying Errata associated with the packages and including them in the repository. Individually,use the --step=errata option.After running the preceding sample command, the population of the channel should be complete. Allof the packages should have been moved out of the repository; this can be verified with the commandcd /var/rhn-sat-import/; ls -alR | grep rpm. If all RPMs have been installed and movedto their permanent locations, then this count will be zero, and the administrator may safely remove thetemporary repository (in this case, /var/rhn-sat-import/).6.3. SynchronizingAn update channel is only as useful as the freshness of the information in that channel. Since the RHNSatellite Server is designed to be a standalone environment, any update advisories published by RHNmust be manually imported and synchronized by the administrator of the RHN Satellite Server.During synchronization over the Internet, the RHN Satellite Synchronization Tool performs thefollowing steps:1. Connects over SSL to central RHN Servers, authenticates itself as an RHN Satellite Server, andtriggers an export of RHN data — unless a local mount point for RHN-exported data is specified,in which case no connection is necessary. Refer to Section 6.3.2, “Synchronizing Errata andPackages via Local Media” for an explanation.2. Examines the export and identifies differences between the RHN Satellite Server data set and theexported RHN data set. For a particular channel, the following information is analyzed:• Channel metadata• Metadata of all packages in that channel• Metadata for all Errata that affect that channel