Red Hat NETWORK 3.6 -, Reference Manual

Page: 104 / 198

92 Chapter 6. Red Hat Network Website
6.4.10.8. Kickstart GPG and SSL Keys —
Lists keys and certificates available for inclusion in kickstart profiles and provides a means to create
new ones. This is especially important for customers of RHN Satellite Server or RHN Proxy Server
because systems being kickstarted by them will need to have the server key imported into RHN and
associated with the relevant kickstart profiles. Import it by creating a new key here and then make the
profile association in the
GPG and SSL keys
subtab of the
Kickstart Details
page.
To develop a new key/certificate, click
create new cryptokey
in the upper-right corner of the page.
Enter a description, select the type, upload the file, and click the
Update Key
button. Note that a
unique description is required.
6.4.10.9. Kickstart Distributions —
Enables you to identify custom installation trees that may be used for kickstarting. (Satellite users
should note that this does not display Red Hat distributions provided to them. They can be found
within the
Distribution
dropdown menu of the
Kickstart Details
page.) Before creating a distribu-
tion, you will need to make an installation tree available, as described in the Kickstart Installations
chapter of the Red Hat Enterprise Linux 3 System Administration Guide . This tree will need to be
located in a public directory on a Web server.
Important
RHN Satellite Server users should note that channels imported with
satellite-sync
are made
available automatically and do not require the creation of a separate installation tree. For instance,
if you have imported
rhel-i386-es-3
and the current release is
rhel-i386-es-3-u1
, this option
will appear within the Distribution dropdown menu of the Kickstart Details page. You need only
select the correct distribution. These trees are available to client systems that kickstart through the
Satellite. While you may be able to access the files from a non-kickstarting client, this functionality is
not supported and may be removed at any time in the future.
To create a new distribution, enter an intuitive label (without spaces) in the Distribution Label field,
such as
my-orgs-rhel-as-3
. In the
External Location
field, paste the URL to the base of the
installation tree. (You can test this by appending "README" to the URL in a Web browser, hitting
return, and ensuring the distribution’s readme file appears.)
In the
Autokickstart RPM field, enter the auto-ks kernel image for the distribution. You can find all
of the available packages by searching RPMs for "auto-kickstart". Identify the appropriate package
based upon the distribution to be kickstarted. It should look something like, "auto-kickstart-ks-rhel-
i386-as-3". Then, strip everything preceding the "ks" to derive the boot image. For instance, in the
above example, you would put "ks-rhel-i386-as-3" in the Autokickstart RPM field.
Then select the matching distribution from the
Base Channel
and
Installer Generation
dropdown
menus, such as
Red Hat Enterprise Linux AS (v.3 for x86)
and
Red Hat
Enterprise Linux 3
, respectively. When finished, click the
Create
button.
6.4.10.10. Kickstart File Preservation —
Collects lists of files to be protected and re-deployed on systems during kickstart. For instance, if you
have many custom configuration files located on a system to be kickstarted, you can enter them here
quickly as a list and then associate that list with the kickstart profile to be used.
To use this feature, click the
create new file preservation list
link at the top and enter a relevant label
and all files and directories to preserved on the resulting page. Make sure you enter absolute paths to
all files and directories. Then click
Create List
.