Red Hat NETWORK SATELLITE 5.1.1 - RELEASE NOTES Manual de usuario Pagina 27

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 38
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 26
Chapter 6.
23
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.
Customers of RHN Satellite Server use the RHN Push application, which sends package header
information to the local RHN Satellite Server and places the package into the local repository of the
Satellite that invoked RHN Push.
This chapter discusses both of these tools in detail.
Warning
If you use both RHN Proxy Server and RHN Satellite Server, use only RHN Push. The Proxy-
Satellite combination requires custom packages and channels be uploaded to the Satellite only.
From there, the Proxy servers obtain the packages and distribute them to client systems.
6.1. Uploading Packages to RHN Proxy Server
RHN Package Manager allows an organization to serve custom packages associated with a private
RHN channel through the RHN Proxy Server. If you want the RHN Proxy Server to serve only official
Red Hat Enterprise Linux packages, you do not need to install RHN Package Manager.
To use the RHN Package Manager, install the rhns-proxy-package-manager RPM package and
its dependencies. This package is available to registered RHN Proxy Server systems and is installed
by running up2date rhns-proxy-package-manager.
Note
Only the header information for the packages is uploaded to the RHN Servers. The headers
are required 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 downloaded through the RHN website, although they are listed. They must be
retrieved by the client system using up2date.
6.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:
scp foo.rpm [email protected]:/tmp
When using RHN Package Manager to upload the packages into Red Hat Network, point at the files
you previously copied to the server.
Vista de pagina 26
1 2 ... 22 23 24 25 26 27 28 29 30 31 32 ... 37 38

Comentarios a estos manuales

Sin comentarios