1 Introduction
This Getting Started Guide provides guidance on setting up Uyuni server with KVM. You will learn the fundamentals of managing both traditional and Salt clients.
This guide is intended for system administrators.
Note: Uyuni Version Information
In this manual if not other specified, Uyuni version 3.2 is assumed and this version is required if a feature is discussed. Uyuni 3.2 and Uyuni 3.2 Proxy were originally released as a SLES 12 SP3 extension. Whenever features of the Uyuni3.2 host operating system are documented and not other specified version 12 SP3 is assumed.
1.1 Introduction to Uyuni #
Uyuni is a solution for organizations that require absolute control over maintenance and package deployment on their servers. It lets you manage large sets of Linux systems and keep them up to date, with automated software management, asset management, and system provisioning. Uyuni allows you to maintain a high level of security while effectively managing system life-cycle requirements.
Uyuni uses Salt to provide event-driven configuration and management control. The Salt-master orchestrates thousands of Salt-minions (Uyuni Clients) using remote execution.
Uyuni is fully compatible with Red Hat Satellite Server and offers seamless management of both SUSE Linux Enterprise and Red Hat Enterprise Linux client systems.
Uyuni can be integrated with your network infrastructure in multiple ways. This book will guide you through an initial proof-of-concept setup, using these steps:
Install an operating system (either JeOS or SLES) for use with Uyuni
Install Uyuni Server
Register Uyuni with SUSE Customer Center
Perform initial setup of your Uyuni Server
Register a traditional client
Register a Salt minion
1.2 Prerequisites for Installation #
Before you begin your installation, ensure you have fulfilled these prerequisites:
Current SUSE Customer Center organization credentials
Access to installation media for your chosen operating system
Your environment meets the hardware and networking requirements
You understand the supported client operating systems
This section contains more information on each of these prerequisites.
Note
Uyuni 3.2 is based on SLES 12 SP3 as the host operating system.
1.2.1 Obtaining your SUSE Customer Center Credentials #
You will need to create an account with SUSE Customer Center before you install SUSE Linux Enterprise Server and Uyuni. To obtain your SUSE Customer Center credentials:
Procedure: Obtaining Your SCC Organization Credentials #
Open a browser and direct it to https://scc.suse.com/login.
If you have not done so, create an account now.
Log in to your new SCC account.
Under the widget select .
Click the tab.
Record your login information for use during Uyuni setup.
1.2.2 Obtaining Installation Media #
This book describes installation methods for both JeOS and SUSE Linux Enterprise Server. The JeOS image provides the quickest installation and setup, and is suitable for a test or proof of concept installation. Alternatively, SUSE Linux Enterprise Server provides a more robust installation, which requires a larger initial download. Choose your preferred operating system based on the type of environment you want to install, and the amount of bandwidth and time you have available.
You can find installation images for JeOS and SLES in your SUSE Customer Center account. Log in, then navigate to the URL for your chosen operating system:
1.2.3 Hardware Requirements #
This table outlines hardware and software requirements on x86_64 and IBM Power PC architecture. For installation on z Systems, see:
Table 1.1: Hardware Requirements for x86_64 Architecture #
| Hardware | Recommended |
|---|---|
CPU | Multi-core 64-bit CPU |
RAM: | Test Server Minimum 8 GB |
Base Installation Minimum 16 GB | |
Production Server Minimum 32 GB | |
Disk Space: |
|
| |
|
Table 1.2: Hardware Requirements for IBM POWER8 or POWER9 Architecture #
| Hardware | Recommended |
|---|---|
CPU | Minimum 4 dedicated cores |
RAM: | Test Server Minimum 8 GB |
Base Installation Minimum 16 GB | |
Production Server Minimum 32 GB | |
Disk Space: |
|
| |
|
1.2.4 Network Requirements #
This section details the networking and port requirements for Uyuni.
- Fully Qualified Domain Name (FQDN)
The Uyuni server must resolve its FQDN correctly or cookies will not work properly on the WebUI. For more information about configuring the hostname and DNS, see SUSE Linux Enterprise Server Documentation - Configuring Host Name and DNS
- Hostname and IP Address
To ensure that the Uyuni domain name can be resolved by its clients, both server and client machines must be connected to a working DNS server. For more information about setting up a DNS server, see SUSE Linux Enterprise Server Documentation - The Domain Name System
- Using a Proxy When Installing from SUSE Linux Enterprise Media
If you are on an internal network and do not have access to SUSE Customer Center, you can set up and use a proxy during installation. For more information about configuring a proxy for access to SUSE Customer Center during a SUSE Linux Enterprise installation, see SUSE Linux Enterprise Server Documentation - Using a Proxy During Installation
Important: Naming Your Server
The hostname of Uyuni must not contain uppercase letters as this may cause jabberd to fail. Choose the hostname of your Uyuni server carefully. Although changing the server name is possible, it is a complex process and unsupported.
In a production environment, Uyuni server and its clients should always use a firewall. This table gives an overview of required ports, to be used when you are setting up your firewall rules.
Table 1.3: Required Server Ports #
| Port | Protocol | Description |
|---|---|---|
22 | TCP | SSH |
67 | UDP | DHCP |
69 | UDP | TFTP, used to support PXE services |
80 | TCP | HTTP, used in some bootstrap cases |
123 | UDP | NTP time service |
443 | TCP | HTTPS, used for Web UI, client, Proxy server, and API traffic |
4505 | TCP | Salt, used by the Salt-master to accept communication requests from minions |
4506 | TCP | Salt, used by the Salt-master to accept communication requests from minions |
5222 | TCP | XMPP client, used for communications with the |
5269 | TCP | XMPP server, used for pushing actions to SUSE Manager Proxy |
For more information on disconnected setup and port configuration, see:
1.2.5 Supported Client Systems #
Supported operating systems for traditional and Salt clients are listed in this table.
Table 1.4: Supported Client Systems #
| Operating Systems | Architecture | Traditional Clients | Salt Clients |
|---|---|---|---|
SUSE Linux Enterprise 11 SP4 | x86, x86_64, Itanium, IBM POWER, z Systems | Supported | Supported |
SUSE Linux Enterprise 12 SP3 | x86_64, IBM POWER (IBM Power PC), z Systems, ARM | Supported | Supported |
SUSE Linux Enterprise 15 | x86_64, IBM POWER (IBM Power PC), z Systems, ARM | Supported | Supported |
Latest minor release Red Hat Enterprise Linux Server 6 | x86, x86_64 | Supported | Supported |
Latest minor release Red Hat Enterprise Linux Server 7 | x86_64 | Supported | Supported |
Open Enterprise Server 2015, 2015 SP1, 2018 | x86_64 | Supported | Supported |
Note: Supported Versions and SP Levels
Client operating system versions and SP levels must be under general support (normal or LTSS) to be supported with Uyuni. For details on supported product versions, see https://www.suse.com/lifecycle.