3 Expanded Support

As root install spacewalk-utils on your SUSE Manager server:

zypper in spacewalk-utils

Important: Supported Tools

The spacewalk-utils package contains a collection of upstream command line tools which provide assistance with spacewalk administrative operations. You will be using the spacewalk-common-channels tool. Keep in mind SUSE only provides support for spacewalk-clone-by-date and spacewalk-manage-channel-lifecycle tools.

Run the spacewalk-common-channels script to add the CentOS7 base, updates, and Spacewalk client channels.

{prompt.root}spacewalk-common-channels -u admin -p`secret`-a x86_64 'centos7'{prompt.root}spacewalk-common-channels -u admin -p`secret`-a x86_64 'centos7-updates'{prompt.root}spacewalk-common-channels -u admin -p`secret`-a x86_64 'spacewalk26-client-centos7'

Note: Required Channel References

The /etc/rhn/spacewalk-common-channels.ini must contain the channel references to be added. If a channel is not listed, check the latest version here for updates: https://github.com/spacewalkproject/spacewalk/tree/master/utils

From the Web UI select Main Menu › Software › Manage Software Channels › Overview. Select the base channel you want to synchronize, in this case CentOS7 (x86_64). Select Repositories › Sync. Check the channels you want to synchronize and then click the Sync Now button or, optionally, schedule a regular synchronization time.

Copy all relevant GPG keys to /srv/www/htdocs/pub. Depending on what distribution you are interested in managing these could include an EPEL key, SUSE keys, Red Hat keys, and CentOS keys. After copying these you can reference them in a comma-delimited list within your bootstrap script (see Procedure: Preparing the Bootstrap Script).

Install and setup a CentOS 7 client with the default installation packages.

Ensure the client machine can resolve itself and your SUSE Manager server via DNS. Validate that there is an entry in /etc/hosts for the real IP address of the client.

Create an activation key (centos7) on the SUSE Manager server that points to the correct parent/child channels, including the CentOS base repo, updates, and Spacewalk client.

Create/edit your bootstrap script to correctly reflect the following:

# 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-centos7

ORG_GPG_KEY=res.key,RPM-GPG-KEY-CentOS-7,suse-307E3D54.key,suse-9C800ACA.key,RPM-GPG-KEY-spacewalk-2015

FULLY_UPDATE_THIS_BOX=0

yum clean all
# Install the prerequisites
yum -y install yum-rhn-plugin rhn-setup

Add the following lines to the bottom of your script, (just before echo “-bootstrap complete -”):

# This section is for commands to be executed after registration
mv /etc/yum.repos.d/Cent* /root/
yum clean all
chkconfig rhnsd on
chkconfig osad on
service rhnsd restart
service osad restart

Continue by following normal bootstrap procedures to bootstrap the new client.

Add the Open Build Service repo for Salt:

{prompt.root}yum-config-manager --add-repo http://download.opensuse.org/repositories/systemsmanagement:/saltstack:/products/RHEL_7/

Import the repo key:

{prompt.root}rpm --import http://download.opensuse.org/repositories/systemsmanagement:/saltstack:/products/RHEL_7/repodata/repomd.xml.key

Check if there is a different repository that contains Salt. If there is more than one repository listed disable the repository that contains Salt apart from the OBS one.

{prompt.root}yum list --showduplicates salt

Install the Salt minion:

{prompt.root}yum install salt salt-minion

Change the Salt configuration to point to the SUSE Manager server:

{prompt.root}mkdir -p /etc/salt/minion.d{prompt.root}echo "master:`server_fqdn`" > /etc/salt/minion.d/susemanager.conf

Restart the minion

{prompt.root}systemctl restart salt-minion

Proceed to Main Menu › Salt › Keys from the Web UI and accept the minion’s key.

Ensure that you have the appropriate software channels available on your system. In the SUSE Manager Web UI, navigate to Software › Channel List › All. You should see a base channel and a child channel for your architecture, for example:

 ubuntu-18.04-pool for amd64
 |
 +- Ubuntu-18.04-SUSE-Manager-Tools for amd64

Create custom repositories to mirror the Ubuntu packages. For example:

For main:

Create custom channels under the pool channel, mirroring the vendor channels. Ensure the custom channels you create have AMD64 Debian architecture.

For example:

 ubuntu-18.04-pool for amd64 (vendor channel)
 |
 +- Ubuntu-18.04-SUSE-Manager-Tools for amd64 (vendor channel)
 |
 +- ubuntu-18.04-amd64-main (custom channel)
 |
 +- ubuntu-18.04-amd64-main-updates (custom channel)

Associate the custom channels with the appropriate custom repositories.

Synchronize the new custom channels. You can check the progress of your synchronization from the command line with this command:

To use bootstrap with Ubuntu, you will need to create a bootstrap repository. You can do this from the command line with mgr-create-bootstrap-repo:

mgr-create-bootstrap-repo --with-custom-channels

On the client, edit the sudoers file:

sudo visudo

Grant sudo access to the user by adding this line to the sudoers file. Replace <user> with the name of the user that will be used to bootsrap the client in the Web UI:

<user>   ALL=NOPASSWD: /usr/bin/python, /usr/bin/python2, /usr/bin/python3