RegisteringClients14

Grant Gainey edited this page Dec 12, 2016 · 2 revisions
Clone this wiki locally

Registering Clients

Instructions for registering client systems you wish to manage with Spacewalk 1.4

Spacewalk 1.3 instructions are available at RegisteringClients13. Spacewalk 1.2 instructions are available at RegisteringClients12.

Before Starting

  1. Create a base channel within Spacewalk (Channels > Manage Software Channels > Create New Channel)

  2. Create an activation key with the new base channel. When creating a registration key do not use the generate function, create a human-readable version. eg: fedora-server-channel. This makes your installation more understandable and provides greater logical consistency to the whole system. On the other hand, if you want to prevent people from getting access to your channels, letting Spacewalk to generate random activation key name is the best way to go.

Note about rhnreg_ks --force

rhnreg_ks is used for registration of clients to Spacewalk. If you need to re-register a client to your Spacewalk server or change registration from one environment or server to another Spacewalk server then use the "--force" flag with rhnreg_ks, otherwise there is no need to use "--force".

Fedora

  1. Install the Spacewalk client yum repository

    • For Fedora 13:

    rpm -Uvh http://spacewalk.redhat.com/yum/1.4/Fedora/13/x86_64/spacewalk-client-repo-1.4-1.fc13.noarch.rpm

    • For Fedora 14:

    rpm -Uvh http://spacewalk.redhat.com/yum/1.4/Fedora/14/x86_64/spacewalk-client-repo-1.4-1.fc14.noarch.rpm

  2. Install client packages

    yum install rhn-client-tools rhn-check rhn-setup rhnsd m2crypto yum-rhn-plugin

    }}} 3. Register your Fedora system to Spacewalk using the activation key you created earlier {{{

    rhnreg_ks --serverUrl=http://YourSpacewalk.example.org/XMLRPC --activationkey=

    }}}

CentOS 5 or Red Hat Enterprise Linux 5 and 6

'''Warning:''' If you are installing these packages on a Red Hat Enterprise Linux installation it will override some of the original base packages and you may well be invalidating your support agreement with Red Hat!

  1. Install the Spacewalk yum repository
 * RHEL5 /CentOS 5
   {{{
# rpm -Uvh http://spacewalk.redhat.com/yum/1.4/RHEL/5/i386/spacewalk-client-repo-1.4-1.el5.noarch.rpm
   }}}
 * RHEL6
   {{{
# rpm -Uvh http://spacewalk.redhat.com/yum/1.4/RHEL/6/i386/spacewalk-client-repo-1.4-1.el6.noarch.rpm
   }}}
 2. The latest client tools bring the upstream development to your client boxes. That means that the packages may have dependencies that are not found in core Red Hat Enterprise Linux. These dependencies can be found in EPEL, just like for the Spacewalk server:
 * EPEL5
   {{{
# BASEARCH=$(uname -i)
# rpm -Uvh http://download.fedora.redhat.com/pub/epel/5/$BASEARCH/epel-release-5-4.noarch.rpm
   }}}
 * EPEL6
{{{
# BASEARCH=$(uname -i)
# rpm -Uvh http://download.fedora.redhat.com/pub/epel/6/$BASEARCH/epel-release-6-5.noarch.rpm
   }}}
  3. Install client packages
    {{{
# yum install rhn-client-tools rhn-check rhn-setup rhnsd m2crypto yum-rhn-plugin
    }}}
  4. Register your CentOS or Red Hat Enterprise Linux system to Spacewalk using the activation key you created earlier
   {{{
# rhnreg_ks --serverUrl=http://YourSpacewalk.example.org/XMLRPC --activationkey=<key-with-rhel-custom-channel> 
   }}}

CentOS 4

Registering a CentOS 4 server to Spacewalk is exactly the same as it would be for CentOS 5, but rhnreg_ks, rhn_check and other related scripts are located in the package '''up2date''', and not in '''rhn-setup'''.

  1. Enable '''spacewalk-tools''' repo for Yum and install '''up2date''' package:
{{{
# rpm -ivh http://stahnma.fedorapeople.org/spacewalk-tools/spacewalk-client-tools-0.0-1.noarch.rpm
# yum install up2date 
  1. Register your CentOS system to Spacewalk using the activation key you created earlier:
# rhnreg_ks --serverUrl=http://YourSpacewalk.example.org/XMLRPC --activationkey=<key-with-centos-custom-channel>

SUSE

  1. Add the spacewalk-tools repo to get access to the tools and install them:

For openSUSE 11.4:

#  zypper ar -f http://download.opensuse.org/repositories/systemsmanagement:/spacewalk:/1.4/openSUSE_11.4/ spacewalk-tools
#  zypper install rhn-client-tools zypp-plugin-spacewalk rhnsd rhn-setup rhn-check yum

For Factory:

#  zypper ar -f http://download.opensuse.org/repositories/systemsmanagement:/spacewalk:/1.4/openSUSE_Factory/ spacewalk-tools
#  zypper install rhn-client-tools zypp-plugin-spacewalk rhnsd rhn-setup rhn-check yum
  1. Register your SUSE system to Spacewalk using the activation key you created earlier

    rhnreg_ks --serverUrl=http://YourSpacewalk.example.org/XMLRPC --activationkey=

    }}}

Debian

Add following line to file /etc/apt/sources.list:
{{{
deb http://miroslav.suchy.cz/spacewalk/debian spacewalk-unstable ./

Note: packages are not signed. We are working on direct inclusion in Debian and proper signing.

Install the packages.

apt-get update
apt-get install apt-spacewalk rhnsd rhnpush

And then register with your Spacewalk 1.3 or above using rhnreg_ks and activation key. In order to get dynamic repositories (as you know them with yum-rhn-plugin) you need to apply the patch to your Apt. Eventually you can use patched version from the above repository.

vim /etc/sysconfig/rhn/up2date
rhnreg_ks --activationkey=1-my-debian-key

When updating the Apt cache you can watch the status of communication between Apt and Spacewalk.

apt-get update

Finally, you rhnpush your favourite Debian packages to your Spacewalk 1.4 in order to be able to apply them using the Spacewalk Web.

# Workaround broken rhnpush for Spacewalk 1.4:
echo 'Fault = xmlrpclib.Fault' \
    >> /usr/share/pyshared/rhn/rpclib.py

Note that for Debian clients neither Spacewalk proxy, satellite-sync, repo-sync, source packages nor staging content will work.

Solaris 8, 9 or 10

See Solaris Support.