1. Manuals
  2. Brands
  3. Red Hat Manuals
  4. Software
  5. NETWORK SATELLITE 5.1.0 - CHANNEL MANAGEMENT
  6. Manual

Red Hat NETWORK SATELLITE 5.1.0 - CHANNEL MANAGEMENT Manual

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

Advertisement

Quick Links

Download this manual See also: Reference Manual, Configuration Manual
Red Hat Network Satellite
Channel Management
Guide 5.1.0
5.1
ISBN: N/A
Publication date:

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the NETWORK SATELLITE 5.1.0 - CHANNEL MANAGEMENT and is the answer not in the manual?

Questions and answers

Related Manuals for Red Hat NETWORK SATELLITE 5.1.0 - CHANNEL MANAGEMENT

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

  • Page 1 Red Hat Network Satellite Channel Management Guide 5.1.0 ISBN: N/A Publication date:...
  • Page 2 Red Hat Network Satellite...
  • Page 3 All other trademarks referenced herein are the property of their respective owners. The GPG fingerprint of the security@redhat.com key is: CA 20 86 86 2B D6 9D FC 65 F6 EC C4 21 91 80 CD DB 42 A6 0E...
  • Page 4 Red Hat Network Satellite...

  • Page 5: Table Of Contents

    1. Introduction ......................1 2. Introduction to RHN Channels ................. 3 1. Base Channels and Child Channels ..............3 2. Subscribing to Channels ................. 3 3. Channel Availability ..................4 4. Tools, Repositories, and Practices ..............4 3. Building Custom Packages ..................7 1.

  • Page 7: 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 9: 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.

  • Page 10: Channel Availability

    Chapter 2. Introduction to RHN Channels with a custom channel so that systems registering with those keys are automatically associated with the custom channel. For more information on using these applications, refer to the respective chapter of the RHN Reference Guide for your entitlement level (Management or Provisioning).
  • Page 11 Tools, Repositories, and Practices • RHN Satellite Synchronization Tool - Use this to import and synchronize standard packages from Red Hat Network to your RHN Satellite Server with Red Hat Network. This is done via the Internet or CD-ROM. 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.

  • Page 13: 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.

  • Page 14: Rhn Rpm Guidelines

    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 2. When building an RPM for a child channel, build the package on a fresh install of Red Hat Enterprise Linux of the same version as the child's base channel.

  • Page 15: Digital Signatures For Rhn Packages

    Digital Signatures for RHN Packages must be forced to accept them. Signing packages is highly recommended and is covered in Section 2, “Digital Signatures for RHN Packages”. 6. If the package is changed in any way, including changing the signature or recompiling, the version or release must be increased incrementally.

  • Page 16: Generating A Gnupg Keypair

    Chapter 3. Building Custom Packages 2.1. Generating a GnuPG Keypair A GnuPG keypair consists of the private and public keys. To generate a keypair type the following command as the root user on the shell prompt: gpg --gen-key If you execute this command as a non-root user, you see the following message: gpg: Warning: using insecure memory! This message appears because non-root users cannot lock memory pages.

  • Page 17: Signing Packages

    Signing packages Like your account passwords, a good passphrase is essential for optimal security in GnuPG. Mix your passphrase with uppercase and lowercase letters, use numbers, and/or include punctuation marks. Once you enter and verify your passphrase, your keys are generated. A message similar to the following appears: We need to generate a lot of random bytes.
  • Page 18 Chapter 3. Building Custom Packages Replace the key ID value of with the key ID from your GPG keyring that _gpg_name B7085C8A you use to sign packages. This value tells RPM which signature to use. To sign the package , use the following command: package-name-1.0-1.noarch.rpm rpm --resign package-name-1.0-1.noarch.rpm Enter your passphrase.

  • Page 19: 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 20: Managed Software Channel Details

    Chapter 4. Custom Channel and Package Management In addition to the buttons and pages available to standard RHN Management-level users, RHN Satellite Server and RHN Proxy Server customers also have access to Manage Software Channels on the left navigation bar. This button opens the Software Channel Management interface, where all custom software channel management work occurs.
  • Page 21 Managed Software Channel Details Channel Administrators automatically have management access to all channels. • Errata — Provides the errata associated with each of your custom channels. Just as Red Hat Network produces and delivers errata updates to Red Hat Enterprise Linux software, you deliver errata updates to your custom channels as part of updating your servers with the latest code.

  • Page 22: Manage Software Packages

    Chapter 4. Custom Channel and Package Management When satisfied with the changes, click Clone Errata. Review the impending changes on the confirmation page and click Update Errata. • Packages — Provides the packages associated with each of your custom channels. This tab contains subtabs that allow you to view, add, and remove packages: List/Remove, Add, and Compare.

  • Page 23: Creating A Software Channel

    Creating a Software Channel Management for instructions. To remove packages from the database, in the Software Package Management page, select an option containing them from the View dropdown menu and click View. Then select the appropriate checkboxes and click Delete Packages. A confirmation page appears with the packages listed.

  • Page 24: Cloning Software Channels

    Chapter 4. Custom Channel and Package Management When packages are initially uploaded, they can be assigned to a custom channel, multiple custom channels, or no channel at all. Refer to Chapter 6, Uploading and Maintaining Custom Packages for instructions. Once uploaded, packages may be reassigned between custom channels and the No Channels repository.

  • Page 25: Deleting Software Channels

    Deleting Software Channels exclude certain errata and associated update packages. Select the option you desire using the radio buttons within the Clone field, identify the target channel using the Clone From dropdown menu, and click Create Channel. On the New Software Channel page, complete the fields as described in Section 5, “Creating a Software Channel”.

  • Page 27: 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.

  • Page 28: Managed Errata Details

    Chapter 5. Custom Errata Management 2. Managed Errata Details If you click on the advisory of a managed errata alert in the Published or Unpublished pages, its Managed Errata Details page appears. This page is further divided into three tabs: Details, Channels, and Packages.

  • Page 29: Assigning Packages To Errata

    Assigning Packages to Errata RHN Satellite Server administrators may also create errata by cloning an existing one. This cloning preserves package associations and simplifies issuing errata. Refer to Section 5, “Cloning Errata” for instructions. To edit an existing errata alert's details, click its advisory in the Errata Management page, make your changes in the appropriate fields of the Details tab, and click the Update Errata button.

  • Page 30: Cloning Errata

    Chapter 5. Custom Errata Management changes are made available. To initiate your changes to the cache manually, follow the directions to commit your changes immediately at the top of the page. 5. Cloning Errata You may clone errata for easy replication and distribution as part of RHN Satellite Server. Only errata potentially applicable to one of your channels can be cloned.

  • Page 31: 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 32: Configuring And Using The Rhn Package Manager

    Chapter 6. Uploading and Maintaining Custom Packages 1.1. Configuring and Using the RHN Package Manager Before you can use RHN Package Manager to upload packages into RHN, you need to first manually copy the packages to the Proxy server itself. For example, from a development host you can use scp foo.rpm root@rhnproxy.example.com:/tmp When using RHN Package Manager to upload the packages into Red Hat Network, point at the...
  • Page 33 Configuring and Using the RHN Package After uploading the packages, check to see if the local directory is in sync with the RHN Server's image of the channels: rhn_package_manager -s -c name_of_private_channel This option lists all the missing packages, which are packages uploaded to the RHN Server but not present in the local directory.
  • Page 34 Chapter 6. Uploading and Maintaining Custom Packages Option Description Manager 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. Contrast this with .

  • Page 35: Uploading Packages To Rhn Satellite Server

    Manager manual page: man rhn_package_manager 2. Uploading Packages to RHN Satellite Server The RHN Push application allows you to serve custom packages associated with a private RHN channel through the RHN Satellite Server. If you want the RHN Satellite Server to serve only official Red Hat Enterprise Linux packages, you do not need to install RHN Push.
  • Page 36 Chapter 6. Uploading and Maintaining Custom Packages Option Description that is, , and so forth. -vvv Process packages from this directory. -d, --dir DIRECTORY Specify the channel to receive packages. Note that this -c, --channel CHANNEL_LABEL is required and is not the same as the channel's name. Multiple channels may be specified using multiple instances of (e.g.

  • Page 37: Using The Rhn Push Application

    Using the RHN Push application Option Description Their newness 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 38 Chapter 6. Uploading and Maintaining Custom Packages packages. The following command uploads package headers to the RHN Satellite Server and copies the packages to the RHN Satellite Server package repository: rhnpush -c label_of_private_channelpkg-list You can override the settings in your RHN Push configuration file(s) by specifying options and values on the command line: rhnpush -c label_of_private_channel --server localhost pkg-list is the custom channel created to receive these packages.

  • Page 39: Index

    viewing details, 22 Index Managed Channel Details, 14 managed software channels details, 14 channels packages intro, 3 Solaris and UNIX, 29 Channels cloning, 18 deleting, 19 RHN Package Manager, 25 custom packages, 7 channels, specifying, 26 building, 7 configuration file, 26 guidelines, 8 configuring, 26 signing, 11...

Table of Contents