Preparation
A configured distribution and an autoinstallation profile is required.
-
Provide the files required to start an installation. Unpack an installation medium such as a DVD image on your Server. It contains the Linux kernel, an initrd, and other files required to boot the OS in installation mode.
-
In the Uyuni Web UI, navigate to
. -
In the
Autoinstallable Distributions
dialog, clickCreate Distribution
:-
In the
Distribution Label
field, enter a name to identify your autoinstallable distribution. -
In the
Tree Path
field, enter the path to an installation tree located on your Uyuni Server. -
Select the matching
Base Channel
mirrored on the Uyuni Server. This base channel must represent the distribution you want to install. It can be theVendor
,Custom
, orCloned Channels
. -
The
Installer Generation
should also match. -
Optionally, you can specify kernel options which should be added when booting this distribution. There are multiple places where you can provide kernel options. Only add options here that are generic for the distribution.
-
-
Click Create Autoinstallable Distribution.
For more information, see Distributions.
-
In the Uyuni Web UI, navigate to
. -
In the
Autoinstallation Profiles
dialog, add the profile for your autoinstallation. It can be anAutoYaST
orKickstart
profile. -
There are two ways to create profiles:
-
Create a
Kickstart
profile using a wizard -
Upload an externally created profile (
Kickstart
orAutoYaST
)
-
For more information about the Kickstart
wizard, see Profiles (Kickstart and AutoYaST).
Upload a Profile
Profiles require a label, and an Autoinstallation Tree
(distribution).
Upload the Kickstart
or AutoyaST
profile.
You can write your own kickstart or AutoYaST profile directly in the Web UI, or create the profile and upload it from your local file system.
AutoYaST is able to dump a profile from an existing installation. This can be used as template, but will need to be edited to make it usable by Uyuni.
-
Change the
add-on
section and add Uyuni URLs. The URL must use this format:http://$redhat_management_server/ks/dist/child/<channel-label>/<distribution-label>
-
Replace
<channel-label>
and<distribution-label>
with the correct labels. You can also use a variable fordistribution-label
. Ensure that the distribution label corresponds to the autoinstallable distribution you selected. You can only configure child channels in this file. The channels must be children of the base channel you selected in the distribution you use for this profile. You do not need to specify a base channel. The base channel is defined in the distribution. -
Register the system after it is installed. For this step we provide script snippets that can be used.
For Salt managed clients, use the
spacewalk/minion_script
snippet:<scripts> <init-scripts config:type="list"> $SNIPPET('spacewalk/minion_script') </init-scripts> </scripts>
For traditional clients, use the
spacewalk/sles_register_script
snippet:<scripts> <init-scripts config:type="list"> $SNIPPET('spacewalk/sles_register_script') </init-scripts> </scripts>
For registering Salt clients, you must accept the Salt key on the Uyuni Server before you attempt autoinstallation. |
If you change the distribution label, it will not automatically change the |
For more information about autoinstallation profiles, see Profiles (Kickstart and AutoYaST).
Variables and Snippets
Profiles are not finalized until they are requested by a client. This allows you to use variables in profiles. You can define profile variables in the Web UI by navigating to
.Some common variables are:
- redhat_management_server
-
The server that all clients register to (automatically set). This applies to all clients, not just Red Hat clients.
- org
-
The organization ID where this profile is created (automatically set).
- registration_key
-
The key used in the registration snippets. By specifying this variable, you can set the activation key to be used to register the system.
- dont_register
-
If specified, the registration will be skipped.
- allow_config_actions
-
If set to
1
, it will allow traditional configuration management (traditional only). - allow_remote_commands
-
If set to
1
, it will allow traditional remote command execution (traditional only). - dont_disable_automatic_onlineupdate
-
If set, the automatic online update will stay enabled (SUSE OSes only).
- dont_disable_local_repos
-
If set, local repositories will stay active (not recommended).
Navigate to Autoinstallation Snippets.
to see which snippets are available. For more information, seeSUSE Manager Proxy
A Uyuni Proxy is a SLE client with a special role. You can install it using AutoYaST.
-
Create an autoinstallation tree as outlined in [client-cfg-autoinstallation-prep].
-
Unpack a Unified Installer DVD1.
-
Use
SLE-Product-SUSE-Manager-Proxy-4.1-Pool for x86_64
as the base channel. -
Make sure the
SUSE Manager Proxy 4.1 x86_64
product is completely mirrored.
-
-
Create an AutoYaST profile. You can use the following example as a starting point. Ensure you change the
<password>
to match your own settings.
You can find the AutoYaST file at https://github.com/SUSE/manager-build-profiles/tree/master/AutoYaST.
Then continue with Autoinstallation with AutoYaST.