Table of Contents
Advertisement
Chapter 5. Using RHN Bootstrap
Use the
•
--activation-keys
ment requirements identified in Section 5.1 Preparation.
Use the
•
--gpg-key
tion. Otherwise, use the
Red Hat recommends retaining this security measure.
Include the
•
--allow-config-actions
ment on all client systems touched by the script. This feature is useful in reconfiguring
multiple systems simultaneously.
Include the
•
--allow-remote-commands
systems. Like configuration management, this feature aids in reconfiguring multiple sys-
tems.
When you're done, your command will look something like this:
rhn-bootstrap --activation-keys KEY1,KEY2 \
--gpg-key /var/www/html/pub/MY_CORPORATE_PUBLIC_KEY \
--allow-config-actions \
--allow-remote-commands
Obviously, include the actual key names. Refer to Section 5.4 RHN Bootstrap Options for
the complete list of options.
5.3. Script Use
Finally, when you're finished preparing the script for use, you are ready to run
it. Log into the RHN Satellite Server or RHN Proxy Server, navigate to the
/var/www/html/pub/bootstrap/
the hostname and name of the script as needed to suit the system type:
cat bootstrap-EDITED-NAME.sh | ssh root@CLIENT_MACHINE1 /bin/bash
A less secure alternative is to use either
ery client system. Log into each client machine and issue the following command, altering
script and hostname accordingly:
wget -qO - \
https://your-satellite.example.com/pub/bootstrap/bootstrap-EDITED-NAME.sh \
| /bin/bash
Or with,
:
curl
curl -Sks \
https://your-satellite.example.com/pub/bootstrap/bootstrap-EDITED-NAME.sh \
| /bin/bash
option to include keys, taking into account the entitle-
option to identify the key path and filename during script genera-
option to turn off this verification on client systems.
--no-gpg
directory and run the following command, altering
wget
flag to enable remote configuration manage-
flag to enable remote script use on all client
or
to retrieve and run the script from ev-
curl
29
Advertisement
Table of Contents
