Red Hat NETWORK 3.2 - PROVISIONING Reference Manual

Also see for NETWORK 3.2 - PROVISIONING: Reference guide

Contents

Chapter 4. Red Hat Network Website 65creating a new key here and then make the profile association in the GPG and SSL keys subtab ofthe 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.4.4.10.8. DistributionsThe Distributions page enables you to identify custom installation trees that may be used for kick-starting. (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.) Beforecreating a distribution, you will need to make an installation tree available, as described in the Kick-start Installations chapter of the Red Hat Enterprise Linux 3 System Administration Guide. This treewill need to be located in a public directory on a Web server.To create a new distribution, enter an intuitive label (without spaces) in the Distribution Label field.In the External Location field, paste the URL to the base of the installation tree. (You can test this byappending "README" to the URL in a Web browser, hitting return, and ensuring the distribution’sreadme file appears.)In the Autokickstart Boot Image field, enter the auto-ks kernel image for the distribution. You canfind all of the available packages by searching RPMs for "auto-kickstart". Identify the appropriatepackage 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, inthe above example, you would put "ks-rhel-i386-as-3" in the Autokickstart Boot Image field. Thenselect the matching distribution from the Base Channel and Installer Generation dropdown menusand click the Create button.4.4.10.9. Building Bootable Kickstart ISOsCopy the contents of /isolinux from the first CD-ROM of the target distribution. Then edit theisolinux.cfg file to default to ’ks’. Change the ’ks’ section to look like this:label kskernel vmlinuzappend text ks={url} initrd=initrd.img lang= devfs=nomount ramdisk_size=16438 {ksdevice}The URL can be obtained from the Kickstart Details page. It will look something like this:http://my.sat.server/kickstart/ks/org/1271287x2c4682f33b87ed1dd4dbc64ef860bea8/label/my-rhel3-as-ksIP addressed-based kickstart URLs will look something like this:http://my.sat.server/kickstart/ks/mode/ip_rangeThe kickstart distribution selected by the IP range should match the distribution you are building from,or errors will occur. {ksdevice} is optional, but looks like:ksdevice=eth0It is possible to change the distribution for a kickstart profile within a family, such as RHEL AS3 toRHEL ES3, by specifying the new distribution label. Note that you cannot move between versions(2.1 to 3) and between updates (U1 to U2).Next, you may customize isolinux.cfg further for your needs, such as by adding multiple kickstartoptions, different boot messages, shorter timeout periods, etc.