-
Notifications
You must be signed in to change notification settings - Fork 103
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
4.3: migrate traditional (some minor cosmetic edits) (#2853)
- Loading branch information
Showing
1 changed file
with
20 additions
and
23 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,7 +1,7 @@ | ||
[[contact-methods-migrate-trad]] | ||
= Migrate traditional clients to {salt} clients | ||
= Migrate Traditional Clients to {salt} Clients | ||
|
||
To migrate a system from a traditional client to a {salt}, the user can create a {salt} bootstrap script and re-register the client system with it. | ||
To migrate a system from a traditional to a {salt} client, the user can create a {salt} bootstrap script and re-register the client system with it. | ||
|
||
This could be done by: | ||
|
||
|
@@ -10,26 +10,25 @@ This could be done by: | |
* running the bootstrap script to register the client, with the aforementioned reactivation key. | ||
|
||
|
||
|
||
== Generate Reactivation Key | ||
|
||
A reactivation key can be used to re-register the client and regain all {productname} settings. | ||
For more information on how to create reactivation key, see xref:client-configuration:activation-keys.adoc#reactivation_keys[Reactivation Keys]. | ||
// For more information on how to create reactivation key, see xref:client-configuration:activation-keys.adoc[]. | ||
A reactivation key can be used to re-register the client and regain all {productname} settings. | ||
For more information on how to create reactivation key, see xref:client-configuration:activation-keys.adoc#reactivation_keys[]. | ||
|
||
|
||
|
||
== Create Bootstrap Script | ||
.Procedure: Creating Bootstrap Script | ||
A bootstrap script can be created through the {webui} or from the command line. | ||
For more information about creating bootstrap script, see xref:client-configuration:registration-bootstrap.adoc[]. | ||
[NOTE] | ||
==== | ||
Use the activation key created before to generate the bootstrap script. | ||
==== | ||
|
||
. Once the bootstrap script is generated, it's stored on the server in the [path]``/srv/www/htdocs/pub/bootstrap`` directory. | ||
Alternatively, you can access the bootstrap script over HTTPS. | ||
Replace [literal]``<example.com>`` with the host name of your {productname} Server: | ||
+ | ||
A bootstrap script can be created with the {webui} or from the command line. | ||
For more information about creating bootstrap script, see xref:client-configuration:registration-bootstrap.adoc[], and for generating a suitable activation key in advance, see xref:client-configuration:activation-keys.adoc[]. | ||
|
||
Use the activation key you generating in advance when creating the bootstrap script. | ||
|
||
When the bootstrap script is generated, it is stored on the server in the [path]``/srv/www/htdocs/pub/bootstrap`` directory. | ||
Alternatively, you can access the bootstrap script over HTTPS. | ||
Replace [literal]``<example.com>`` with the host name of the {productname} Server: | ||
|
||
---- | ||
https://<example.com>/pub/bootstrap/bootstrap.sh | ||
---- | ||
|
@@ -39,8 +38,7 @@ https://<example.com>/pub/bootstrap/bootstrap.sh | |
Bootstrap script will try to install [package]``venv-salt-minion`` for {salt} clients if it is available in the bootstrap repository, or [package]``salt-minion`` if there is no {salt} bundle in the bootstrap repository. | ||
It is possible to avoid installing {salt} bundle and keep using [package]``salt-minion`` if you need it. | ||
For more information, see xref:client-configuration:contact-methods-saltbundle.adoc[Salt Bundle]. | ||
For more information, see xref:client-configuration:contact-methods-saltbundle.adoc[]. | ||
==== | ||
|
||
|
||
|
@@ -59,16 +57,14 @@ As the final step, run the bootstrap script to migrate and register clients. | |
---- | ||
cd /srv/www/htdocs/pub/bootstrap/ | ||
---- | ||
+ | ||
|
||
. Run the following command to execute the bootstrap script on the client. | ||
Replace [systemitem]``EXAMPLE.COM`` with the hostname of your client, and [systemitem]``REACT_KEY``: | ||
Replace [systemitem]``EXAMPLE.COM`` with the hostname of your client, and [systemitem]``REACT_KEY`` with the reactivation key: | ||
+ | ||
|
||
---- | ||
cat bootstrap-migrate-to-salt.sh | ssh [email protected] REACTIVATION-KEY=REACT_KEY /bin/bash | ||
---- | ||
+ | ||
|
||
. Alternatively, on the client, run the command: | ||
+ | ||
|
@@ -79,10 +75,11 @@ curl -Sks https://server_hostname/pub/bootstrap/bootstrap-migrate-to-salt.sh | R | |
+ | ||
|
||
The script downloads the required dependencies. | ||
+ | ||
|
||
. Make sure to accept the new {salt} key before looking for your new {salt} minion. You can open the {productname} {webui} and navigate to menu:Salt[Keys] to accept the client key | ||
|
||
. When the script has finished running, you can check that your client is registered correctly by opening the {productname} {webui} and navigating to menu:Systems[Overview] to ensure the new client is listed as Salt instead of Management. | ||
. When the script has finished running, you can check that your client is registered correctly by opening the {productname} {webui} and navigating to menu:Systems[Overview]. | ||
Ensure the new client is listed with the Salt instead of the Management system type. | ||
|
||
[WARNING] | ||
==== | ||
|