Red Hat NETWORK SATELLITE 5.1.0 - CHANNEL MANAGEMENT, Справочное руководство

Страница: 121 / 300

4.8. Custom System Info —
RHN Provisioning customers may include completely customizable information about their
systems. Unlike notes, the information here is more formal and may be searched upon. For
instance, you may decide to identify an asset tag for each system. To do this, you must create
an
asset
key within the Custom System Info page.
Click create new key at the upper-right corner of the page. Enter a descriptive label and
description, such as
Asset
and
Precise location of each system
, and click the Create
Key. The key will then show up in the custom info keys list.
Once the key exists, you may assign a value to it through the Custom Info tab of the System
Details page. Refer to Section 4.2.9.1.7, “System Details # Details # Custom Info — ” for
instructions.
4.9. Kickstart —
To satisfy the provisioning needs of customers, RHN provides this interface for developing
kickstart profiles that can be used to install Red Hat Enterprise Linux on either new or
already-registered systems. This enables systems to be installed automatically to particular
specifications.
Important
If your systems are connected to the central RHN Servers, you will need an
external installation tree for each distribution to be kickstarted. This tree can be
hosted anywhere that is accessible by the target system via HTTP. If the
systems are connected through an RHN Proxy Server, then you may place the
installation tree in
/var/www/html/pub/
on the Proxy. RHN Satellite Servers
already have a tree for each Red Hat distribution and therefore do not require
separate trees. Even if the system connects through an RHN Proxy Server to get
to the Satellite, these trees will be available for kickstart. Refer to Section 4.9.6,
“Kickstart # Distributions — ” for instructions on setting up installation trees.
Kickstart —
107