1. Manuals
  2. Brands
  3. Red Hat Manuals
  4. Software
  5. NETWORK SATELLITE 5.2 - CHANNEL MANAGEMENT
  6. Management manual

Red Hat NETWORK SATELLITE 5.2 - CHANNEL MANAGEMENT Management Manual

Channel management
Hide thumbs Also See for NETWORK SATELLITE 5.2 - CHANNEL MANAGEMENT:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Reference Manual, Configuration Manual
Red Hat Network
Satellite 5.2
Channel
Management Guide
Red Hat Network Satellite

Advertisement

Table of Contents
loading

Related Manuals for Red Hat NETWORK SATELLITE 5.2 - CHANNEL MANAGEMENT

Summary of Contents for Red Hat NETWORK SATELLITE 5.2 - CHANNEL MANAGEMENT

  • Page 1 Red Hat Network Satellite 5.2 Channel Management Guide Red Hat Network Satellite...
  • Page 2 Channel Management Guide Red Hat Network Satellite 5.2 Channel Management Guide Red Hat Network Satellite Edition 5.2...

  • Page 3: Table Of Contents

    1. Introduction 2. Introduction to RHN Channels 2.1. Base Channels and Child Channels ................3 2.2. Subscribing to Channels ....................3 2.3. Channel Availability ...................... 4 2.4. Tools, Repositories, and Practices ................. 4 3. Building Custom Packages 3.1. Building packages for Red Hat Network ................ 5 3.1.1.

  • Page 5: Introduction

    In some instances, this document refers to actions that are performed on the Red Hat Network Web servers. For RHN Proxy Server customers, this refers to the central Red Hat Network Servers at https://rhn.redhat.com. For Satellite customers, this refers to the RHN Satellite Server at your site.

  • Page 7: Introduction To Rhn Channels

    Chapter 2. Introduction to RHN Channels A Red Hat Network channel is a collection of software packages. Channels help you segregate packages by sensible rules: a channel may contain packages from a specific Red Hat distribution, for instance. A channel may contain packages for an application or family of applications. Users may also define channels for their own particular needs;...

  • Page 8: Channel Availability

    Chapter 2. Introduction to RHN Channels 2.3. Channel Availability There are many channels in Red Hat Network. Some are available to all users, some are available to users in a particular organization, and some are available only if you have purchased access to them. Channels fall into these main categories: •...

  • Page 9: Building Custom Packages

    Chapter 3. Building Custom Packages There are many things that might go wrong when building software packages. This is especially true when these packages must be delivered and installed through Red Hat Network. This chapter provides an overview of how to build packages for successful delivery via Red Hat Network. Topics covered include why to use RPM, how to build packages for RHN, and how to properly sign packages.

  • Page 10: Rhn Rpm Guidelines

    RPMs for distribution through Red Hat Network, it is imperative to follow these rules: 1. Learn RPM. It is crucial to have a fundamental understanding of the important features of RPM to build packages properly. For more information about RPM, start with the following resources: http://www.rpm.org/RPM-HOWTO/ • http://www.redhat.com/docs/books/max-rpm/ • http://www.rpm.org/mailing_list/ • http://fedora.redhat.com/participate/developers-guide/ch-rpm-building.html •...

  • Page 11: Digital Signatures For Rhn Packages

    Digital Signatures for RHN Packages 10. A ny pre-install, post-install, pre-uninstall, and post-uninstall scripts should never write anything to stderr or stdout. Redirect the messages to /dev/null if they are not necessary. Otherwise, write them to a file. 11.When creating the spec file, use the group definitions from /usr/share/doc/rpm-<version>/ GROUPS.
  • Page 12 Chapter 3. Building Custom Packages Accept the default option: (1) DSA and ElGamal. This option allows you to create a digital signature and encrypt/decrypt with two types of technologies. Type 1 and then press Enter. Next, choose the key size, which is how long the key should be. The longer the key, the more resistant against attacks your messages are.

  • Page 13: Signing Packages

    Signing packages gpg --export -a 'Your Name' > public_key.txt Your public key is written to the file public_key.txt. This public key is quite important. It's the key that must be deployed to all client systems that receive custom software through up2date. Techniques for deploying this key across an organization are covered in the Red Hat Network Client Configuration Guide.

  • Page 15: Custom Channel And Package Management

    Chapter 4. Custom Channel and Package Management Custom channels allow administrators to use the Red Hat Network infrastructure to deploy packages built and maintained by their organizations. All channel and package management activities take place in the Channels tab of the RHN website. The instructions here are used in conjunction with the RHN website chapter of the RHN Reference Guide.

  • Page 16: Managed Software Channel Details

    Chapter 4. Custom Channel and Package Management from it. Manually managing packages and channels on a Proxy in this combined configuration risks putting your servers out-of-sync. Clicking links within the Software Channel Management list takes you to different tabs of the Managed Software Channel Details page.
  • Page 17 Managed Software Channel Details • Clone — Allows Satellite customers to replicate errata and associated packages for a cloned channel. This subtab immediately appears populated for channels that were cloned with either the original state or select errata option. The Clone tab also gains errata whenever one is issued for the target (that is, originating) channel.

  • Page 18: Manage Software Packages

    Chapter 4. Custom Channel and Package Management • Compare — Enables the comparison of package lists between different channels. To see the differences, select another channel from the Compare to: dropdown menu and click Compare. A list appears showing all packages not contained by both channels and indicating the existing channel location of each.

  • Page 19: Assigning Packages To Software Channels

    Assigning Packages to Software Channels The GPG key URL must be the location of the key on the server, as defined during the client configuration process. Refer to the Red Hat Network Client Configuration Guide. The GPG key ID is the unique identifier, such as "DB42A60E", while the GPG key fingerprint is similar to "CA20 8686 2BD6 9DFC 65F6 ECC4 2191 80CD DB42 A60E".

  • Page 20: Deleting Software Channels

    Chapter 4. Custom Channel and Package Management • Original state of the channel — All of the original packages from the target channel but none of the errata or associated update packages. • Select Errata — All of the original packages from the target channel with the ability to exclude certain errata and associated update packages.

  • Page 21: Custom Errata Management

    Chapter 5. Custom Errata Management Custom errata enables you to issue errata alerts for the packages in your custom channels. All errata management activities take place in the Errata tab of the RHN website. The instructions here are used in conjunction with the RHN website chapter of the Red Hat Network Reference Guide. 5.1.

  • Page 22: Creating And Editing Errata

    Chapter 5. Custom Errata Management solution, keywords, references, and notes. To change any of this information, make your modifications in the appropriate fields and click Update Errata. • Channels — Shows the channels associated with the selected errata. To change these associations, select or deselect the appropriate checkboxes and click the Update Channels button.

  • Page 23: Assigning Packages To Errata

    Assigning Packages to Errata 5.4. Assigning Packages to Errata Follow this procedure to assign packages to errata. After selecting an erratum to edit, click on the Packages tab then the Add subtab. To associate packages with the erratum being edited, select the channel from the View dropdown menu that contains the packages you want in and click View.

  • Page 25: Uploading And Maintaining Custom Packages

    Chapter 6. Uploading and Maintaining Custom Packages Depending upon which Red Hat Network service is used, there are two different mechanisms for uploading packages to private channels. Customers of RHN Proxy Server use the RHN Package Manager application, which sends package header information to the central Red Hat Network Servers and places the package itself into the local repository of the Proxy that invoked RHN Package Manager.
  • Page 26 Chapter 6. Uploading and Maintaining Custom Packages When using RHN Package Manager to upload the packages into Red Hat Network, point at the files you previously copied to the server. Create at least one private channel to receive custom packages prior to upload into Red Hat Network, since a channel is required for systems to obtain the packages.
  • Page 27 Configuring and Using the RHN Package Manager You can also use RHN Package Manager to retrieve a list of packages in a channel, as they are stored by the RHN Server: rhn_package_manager -l -c name_of_private_channel The -l option lists the package name, version number, release number, architecture, and channel Table 6.1, “rhn_package_manager name for each package in the specified channel(s).

  • Page 28: Uploading Packages To Rhn Satellite Server

    Chapter 6. Uploading and Maintaining Custom Packages Option Description Specify RHN password. If not provided, you are prompted --password PASSWORD for the password of a valid Channel Administrator. In the post-upload step, do not copy the packages to their --dontcopy final location in the package tree.
  • Page 29 Configuring the RHN Push Application For instance, you can use the current directory configuration file to specify the software channel to be populated, the home directory configuration file to include the username to be invoked, and the central configuration file to identify the server to receive the packages. Table 6.2, “rhnpush options”...

  • Page 30: Using The Rhn Push Application

    Chapter 6. Uploading and Maintaining Custom Packages Option Description is dependent on their associated binary packages. Using this option with RHN Push and just a source package does upload the package, but the source package does not appear in the RHN Web interface until the associated binary package has been uploaded.
  • Page 31 Using the RHN Push application rhnpush -c label_of_private_channel --server localhost pkg-list The label_of_private_channel is the custom channel created to receive these packages. Be sure you use the precise channel label specified during its creation. If you have one or more channels specified (using -c or --channel), the uploaded package headers are linked to all the channels identified.

  • Page 33: Revision History

    Appendix A. Revision History Revision History Revision 1.0...

  • Page 35: Index

    Index packages Solaris and UNIX, 24 channels RHN Package Manager, 21 intro, 3 channels, specifying, 22 Channels configuration file, 22 cloning, 15 configuring, 21 deleting, 16 copy missing packages to Satellite, 22 custom packages, 5 installing, 21 building, 5 retrieve channel package list, 23 guidelines, 6 rhn_package_manager, 23 signing, 9...

Table of Contents