Install Rudder root server on SLES

If you are working on a test system, you can use the quick install script:

curl https://repository.rudder.io/tools/rudder-setup | bash -s setup-server 6.2

That will automatically execute the installation, and you can go directly to the Initial configuration section below.

Before installation

Before all, you need to setup a server according to the server specifications. You should also configure the network.

As Rudder data can grow really fast depending on your number of managed nodes and number of rules, it is advised to separate partitions to prevent /var getting full and break your system.

Configure the package manager

You may encounter a segmentation fault in Zypper in the following cases:

  • On SLES 11 when trying to install Rudder rpm files locally with Zypper (for example with 'zypper install rudder-agent-version.release-1.SLES.11.x86_64.rpm')

  • On SLES 12 GA when installing Rudder packages, locally or from the repository

This is due to a bug (bnc#929483 on SUSE bugtracker) in Zypper’s RPM headers parsing. You can either:

  • Only for SLES 11, install the packages directly from the repository, as described below

  • Upgrade your libzypp package to a version including the fix provided by SuSE (upgrade for SLES11SP3 and for SLES12)

  • Use the rpm command to install packages locally (for example with rpm -i rudder-agent-version.release-1.SLES.11.x86_64.rpm)

Zypper seems to be quite tolerant to missing dependencies and will let you install rudder-server-root even if you are missing something like git-core for example, if nothing provides it or you did not install it beforehand.

Special care should be taken during initial installation not to say "Continue anyway" if Zypper does complain a dependency can not be resolved and asks what to do.

Add the Rudder packages repository

Installation

Each official package is signed with our GPG signature. To ensure the packages you will install are official builds and have not been altered, import our key into rpm using the following command:

rpm --import https://repository.rudder.io/rpm/rudder_rpm_key.pub

Our key fingerprint is:

pub  1024R/6F07D355 2012-11-09 Rudder Project (RPM release key) <security@rudder-project.org>
      Key fingerprint = 1141 A947 CDA0 4E83 82C1  B9C4 ADAB 3BD3 6F07 D355

Add the Rudder packages repository:

  • on SLES 15:

zypper ar -n 'Rudder 6.2' http://repository.rudder.io/rpm/6.2/SLES_15/ Rudder

If you have an active subscription, use the following to get access to long term support (you need to replace the user name and the password by your Rudder account):

zypper ar -n 'Rudder 6.2' https://LOGIN:PASSWORD@download.rudder.io/rpm/6.2/SLES_15/ Rudder
  • on SLES 12:

zypper ar -n 'Rudder 6.2' http://repository.rudder.io/rpm/6.2/SLES_12/ Rudder

If you have an active subscription, use the following to get access to long term support (you need to replace the user name and the password by your Rudder account):

zypper ar -n 'Rudder 6.2' https://LOGIN:PASSWORD@download.rudder.io/rpm/6.2/SLES_12/ Rudder

Update your local package database to retrieve the list of packages available on our repository:

zypper refresh

Install Rudder root server

To begin the installation, you should simply install the rudder-server-root metapackage, which will install the required components:

zypper install rudder-server-root

Initial configuration

User account

Now the installation is complete you need to create a first user account. The easiest way is to use the dedicated command to create a local admin user:

# Replace USERNAME by the user you want to create
rudder server create-user -u USERNAME

It will ask you a password twice and will create the user.

Read more about user account options in the dedicated section.

First connection

Once all these steps have been completed, use your web browser to go to the server URL. Use your first user credentials to connect.

Now you should go to Settings → General → Allowed Networks and check that the networks listed there properly include all your nodes network addresses. By default this will contain your server’s attached networks.

The setup of the Rudder server is now over. If you plan to manage hundreds or thousands of nodes, please note that some performance tuning can be necessary on the system.


← on RHEL/CentOS on Debian/Ubuntu →