Distributions page enables you to find and create custom installation trees that may be used for automated installations.
Installation data must be made available prior to creating a distribution, as described in the SUSE Linux Enterprise Deployment Guide SUSE Linux Enterprise Deployment Guide or, respectively, Red Hat Enterprise Linux Installation Guide : chap-kickstart-installations This tree must be located in a local directory on the Uyuni server.
To create a distribution, on the
Autoinstallable Distributionspage click
Create Distributionin the upper right corner.
Create Autoinstallable Distributionpage, provide the following data:
Enter a label (without spaces) in the
Distribution Labelfield, such as
In the Tree Path field, paste the path to the base of the installation tree.
Select the matching distribution from the
Installer Generationdrop-down menus, such as
SUSE Linuxfor SUSE Linux Enterprise, or
Red Hat Enterprise Linux 7for Red Hat Enterprise Linux 7 client systems.
When finished, click the Create Autoinstallable Distribution button.
Autoinstallation variables can be used to substitute values into Kickstart and AutoYaST profiles.
To define a variable, create a name-value pair (
name/value) in the text box.
For example, if you want to autoinstall a system that joins the network of a specified organization (for example the Engineering department) you can create a profile variable to set the IP address and the gateway server address to a variable that any system using that profile will use.
Add the following line to the
Variables text box.
To use the distribution variable, use the name of the variable in the profile to substitute the value.
For example, the
network part of a Kickstart file looks like the following:
network --bootproto=static --device=eth0 --onboot=on --ip=$IPADDR \ --gateway=$GATEWAY
$IPADDR will be resolved to
192.168.0.28, and the
There is a hierarchy when creating and using variables in Kickstart files. System Kickstart variables take precedence over Profile variables, which in turn take precedence over Distribution variables. Understanding this hierarchy can alleviate confusion when using variables in Kickstarts.
In AutoYaST profiles you can use such variables as well.
Using variables are just one part of the larger Cobbler infrastructure for creating templates that can be shared between multiple profiles and systems.
For more information about Cobbler and templates, see client-configuration:cobbler.adoc.