On the server, create a bootstrap repository for each distribution/architecture with <br/> <tt>mgr-create-bootstrap-repo</tt> <br/> Ensure that this script finishes properly, and if not, re-check the channel sync.

+

On the server, create a bootstrap repository for each distribution/architecture with <br/> <tt>mgr-create-bootstrap-repo</tt> <br/> Ensure that this script finishes properly, and if not, re-check the channel sync. You can optionally include all the channels under the parent with this command option - <br/> <tt>mgr-create-bootstrap-repo --with-custom-channels</tt> <br/>

−

You can safely re-run this command, and you should whenever a new version of salt-minion is released, and your tools channel gets updated. The repositories are created under <br/> <tt>/srv/www/htdocs/pub/repositories</tt> <br/> , and are meant to be used in the registration/bootstrap process only.

+

You can safely re-run this command at any time, and you SHOULD whenever a new version of salt-minion is released, and your tools channel gets updated. The repositories are created under <br/> <tt>/srv/www/htdocs/pub/repositories</tt> <br/> , and are meant to be used in the registration/bootstrap process only.

== Minion Registration using a bootstrap script ==

== Minion Registration using a bootstrap script ==

−

1. If needed, regenerate the bootstrap script on the server with the Salt option enabled

+

1. If needed, regenerate the bootstrap script on the server with the Salt option enabled

This places the script in <tt>/srv/www/htdocs/pub/bootstrap</tt> by default.

This places the script in <tt>/srv/www/htdocs/pub/bootstrap</tt> by default.

−

2. Copy this for your specific use case and edit the script to reflect the correct activation key, and any other relevant content. Here are some examples of changes:

+

2. Copy this for your specific use case, editing the script to reflect the correct activation key, and any other relevant content. Here are some examples of changes:

a. Add an activation key reference like this:

a. Add an activation key reference like this:

Line 42:

Line 49:

This prevents interference in some cases with proper channel certification.

This prevents interference in some cases with proper channel certification.

−

3. Download and run the appropriately edited bootstrap script after adding correct activation key, etc. This validates installation of the necessary Salt packages, sets the proper activation key, and starts the <tt>salt-minion</tt> service.

+

3. Download and run the appropriately edited bootstrap script after completing the edits. The bootstrap script validates installation of the necessary Salt packages, sets the proper activation key, and starts the <tt>salt-minion</tt> service.

It also creates this file on the minion: <tt>/etc/salt/minion.d/susemanager.conf</tt> with content that looks like this:

+

The script also creates a file on the minion: <tt>/etc/salt/minion.d/susemanager.conf</tt> with content that looks like this:

master: <server FQDN>

master: <server FQDN>

grains:

grains:

Line 52:

Line 59:

4. Go to the Server web UI to Salt -> Onboarding and accept the minion's key. After a few minutes, the new minion will appear in your list of systems with the channels assigned in the activation key you specified in the bootstrap process.

4. Go to the Server web UI to Salt -> Onboarding and accept the minion's key. After a few minutes, the new minion will appear in your list of systems with the channels assigned in the activation key you specified in the bootstrap process.

Bootstrap salt minions with bootstrap scripts

Since SUMA 3.0.2, you can create salt-specific bootstrap scripts that can be incorporated into your onboarding or build processes. While there are other ways to onboard a salt minion, this method provides consistency and scalability.

Bootstrap repositories

On the server, create a bootstrap repository for each distribution/architecture with mgr-create-bootstrap-repo Ensure that this script finishes properly, and if not, re-check the channel sync. You can optionally include all the channels under the parent with this command option - mgr-create-bootstrap-repo --with-custom-channels
You can safely re-run this command at any time, and you SHOULD whenever a new version of salt-minion is released, and your tools channel gets updated. The repositories are created under /srv/www/htdocs/pub/repositories , and are meant to be used in the registration/bootstrap process only.

Minion Registration using a bootstrap script

1. If needed, regenerate the bootstrap script on the server with the Salt option enabled

This prevents interference in some cases with proper channel certification.

3. Download and run the appropriately edited bootstrap script after completing the edits. The bootstrap script validates installation of the necessary Salt packages, sets the proper activation key, and starts the salt-minion service.

4. Go to the Server web UI to Salt -> Onboarding and accept the minion's key. After a few minutes, the new minion will appear in your list of systems with the channels assigned in the activation key you specified in the bootstrap process.

Automatic Minion Registration using a bootstrap script in AutoYast

1. Do all of the above to set up the bootstrap repository and scripts.