Red Hat NETWORK 3.6 -, Reference Manual

Page: 99 / 198

Chapter 6. Red Hat Network Website 87
6.4.8. Stored Profiles —
RHN Provisioning customers can create package profiles through the
Profiles
subtab of the
Packages
tab within the System Details page. Those profiles end up here, on the Stored Profiles page, where
they may be edited and even deleted.
To edit a profile, click its name in the list, alter its name and description, and click the
Update Profile .
To view software associated with the profile, click the
Packages
subtab. To remove the profile entirely,
click delete stored profile at the upper-right corner of the page.
6.4.9. Custom System Info —
RHN Provisioning customers may include completely customizable information about systems. Un-
like notes, the information here is more formal and can 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 6.4.2.6.1.5 System Details Details Custom Info — for instructions.
6.4.10. Kickstart —
To satisfy the provisioning needs of customers, RHN provides this interface for developing kickstart
profiles by which new systems may be built. This enables systems to be installed to particular speci-
fications automatically.
Warning
Since RHN Proxy Servers typically direct files from the central RHN Servers, and those servers
do not distribute the files necessary for kickstart, systems connected to a Proxy not being served
by an RHN Satellite Server must be kickstarted using an external installation tree. This tree can
be placed on the Proxy itself in one of two non-forwarding directories:
/var/www/html/pub/
and
/var/www/html/_rhn_proxy/
. Refer to Section 6.4.10.9 Kickstart Distributions — for in-
structions on setting up installation trees.
6.4.10.1. Kickstart Prerequisites
Although Red Hat Network has taken great pains to ease the provisioning of systems, some prepara-
tion is still required for your infrastructure to handle kickstarts. For instance, before creating kickstart
profiles, you should have:
•
Installed and have running a DHCP server.
•
Installed and have running a TFTP server.
•
Configured DHCP to assign required networking parameters and the bootloader program location.
•
Specified within the bootloader configuration file the kernel to be used and appropriate kernel op-
tions.