Register Clients with a Bootstrap Script
Registering clients with a bootstrap script gives you control over parameters, and can help if you have to register a large number of clients at once. This method works for both Salt and traditional clients.
To register clients using a bootstrap script, we recommend you create a template bootstrap script to begin, which can then be copied and modified. The bootstrap script you create is executed on the client when it is registered, and ensures all the necessary packages are deployed to the client. There are some parameters contained in the bootstrap script, which ensure the client system can be assigned to its base channel, including activation keys and GPG keys.
It is important that you check the repository information carefully, to ensure it matches the base channel repository. If the repository information does not match exactly, the bootstrap script cannot download the correct packages.
All clients need a bootstrap repository. It is automatically created and regenerated on the SUSE Manager Server when products are synchronized. A bootstrap repository includes packages for installing Salt on clients, and for registering Salt or traditional clients.
For more information about creating a bootstrap repository, see Bootstrap Repository.
GPG Keys and Uyuni Client Tools
The GPG key used by Uyuni Client Tools is not trusted by default.
When you create your bootstrap script, add a path to the file containing the public key fingerprint with the
openSUSE Leap 15 and SLE 15 use Python 3 by default. Bootstrap scripts based on Python 2 must be re-created for openSUSE Leap 15 and SLE 15 systems. If you register openSUSE Leap 15 or SLE 15 systems using Python 2, the bootstrap script fails.
1. Create a Bootstrap Script with
mgr-bootstrap command generates custom bootstrap scripts.
A bootstrap script is used by Uyuni client systems for simplifying their initial registration and configuration.
--script, are the only mandatory arguments.
On the Uyuni Server, as root at the command line execute it with the mandatory arguments.
<EDITED_NAME> with your values:
mgr-bootstrap --activation-key=<ACTIVATION_KEYS> --script=bootstrap-<EDITED NAME>.sh
mgr-bootstrap command offers several other options, including the ability to set a specific hostname, set specific GPG keys, and set the registration method (traditional, salt-minion, or salt-bundle).
For more information, see the
mgr-bootstrap man page, or run
2. Create a Bootstrap Script from Web UI
You can use the Uyuni Web UI to create an editable bootstrap script.
In the Uyuni Web UI, navigate to.
SUSE Manager Configuration - Bootstrapdialog, uncheck the
Bootstrap using Saltcheckbox if you are installing a traditional client. For Salt clients, leave it checked.
The required fields are pre-populated with values derived from previous installation steps. For details on each setting, see Bootstrap Script.
Click Update to create the script.
The bootstrap script is generated and stored on the server in the
/srv/www/htdocs/pub/bootstrapdirectory. Alternatively, you can access the bootstrap script over HTTPS. Replace
<example.com>with the host name of your Uyuni Server:
Do not disable SSL in your bootstrap script.
For more information about custom certificates, see SSL Certificates.
3. Edit a Bootstrap Script
You can copy and modify the template bootstrap script you created to customize it. A minimal requirement when modifying a bootstrap script for use with Uyuni is the inclusion of an activation key. Most packages are signed with GPG, so you also need to have trusted GPG keys on your system to install them.
In this procedure, you need to know the exact name of your activation keys.
Tasks box, click
Manage Activation Keys.
All keys created for channels are listed on this page.
You must enter the full name of the key you wish to use in the bootstrap script exactly as presented in the key field.
For more information about activation keys, see Activation Keys.
On your Uyuni Server, as root at the command line change to the bootstrap directory with:
Create and rename two copies of the template bootstrap script for use with each of your clients.
cp bootstrap.sh bootstrap-sles12.sh cp bootstrap.sh bootstrap-sles15.sh
bootstrap-sles15.shfor modification. Scroll down until you can see the text shown below. If
exit 1exists in the file, comment it out by typing a hash or pound sign (#) at the beginning of the line. This activates the script. Enter the name of the key for this script in the
echo "Enable this script: comment (with #'s) this block (or, at least just" echo "the exit below)" echo #exit 1 # can be edited, but probably correct (unless created during initial install): # NOTE: ACTIVATION_KEYS *must* be used to bootstrap a client machine. ACTIVATION_KEYS=1-sles15 ORG_GPG_KEY=
When you have finished, save the file, and repeat this procedure for the second bootstrap script.
By default, bootstrap script will try to install
For more information, see Salt Bundle.
4. Connect Clients
When you have finished creating your script, you can use it to register clients.
On the Uyuni Server, log in as root. At the command prompt, and change to the bootstrap directory:
Run this command to execute the bootstrap script on the client; replace
EXAMPLE.COMwith the host name of your client:
cat bootstrap-sles15.sh | ssh root@EXAMPLE.COM /bin/bash
Alternatively, on the client, run this command:
curl -Sks https://server_hostname/pub/bootstrap/bootstrap-sles15.sh | /bin/bash
To avoid problems, make sure the bootstrap script is executed using
This script downloads the required dependencies located in the repositories directory you created earlier.
When the script has finished running, you can check that your client is registered correctly by opening the Uyuni Web UI and navigating toto ensure the new client is listed.
If you used the script to register the Salt client, open the Uyuni Web UI and navigate toto accept the client key.
When new packages or updates are installed on the client using Uyuni, any end user license agreements (EULAs) are automatically accepted. To review a package EULA, open the package detail page in the Web UI.