Deploy SUSE Manager 5 as a container using SLE Micro 5.5
In this section, you will gain expertise in setting up and deploying a containerized SUSE Manager 5 Server.
This process encompasses the installation of SLE Micro, and then initiating interaction with the container through the mgradm
and mgrctl
commands.
1. Container Host general Requirements
For general requirements see, General requirements
A SLE Micro or SUSE Linux Enterprise Server server should be installed from installation media. This procedure is described below.
2. Container Host Requirements
For CPU, RAM and storage requirements see, Hardware requirements
To guarantee that clients can resolve the SUSE Manager 5 domain name, both the container server and host machines must be linked to a functional DNS server. Additionally, it is essential to ensure correct configuration of reverse lookups. |
3. SLE Micro 5.5 Installation
Get a copy of the SLE Micro 5.5 install media. You can begin installation on either a virtual machine or on a physical server.
-
Begin installation from media
-
Adjust Keyboard and language. Click the
checkbox
to accept the License Agreement. -
Click
Next
to continue. -
Select your registration method. For this example we will register the sever with SUSE Customer Center.
-
Enter your SUSE Customer Center Email address.
-
Enter your registration code for SLE Micro 5.5.
Base operating system for SUSE Manager 5 containerized ServerFor SUSE Manager 5.0, the base operating system of the container is SUSE Linux Enterprise Server 15 SP6 You can find these keys from your SUSE Customer Center account.
-
Click
Next
to continue. -
Select the SUSE Manager 5 Server extension
Checkbox
. -
Click
Next
to continue. -
Enter your SUSE Manager 5 Server extension registration code.
SUSE Manager as an extensionSUSE Manager 5 is installed as an extension. Therefore, in addition to acquiring SUSE Customer Center registration keys for the base Server, you will also need SUSE Customer Center registration codes for the following extensions:
-
SUSE Manager 5 Server
-
SUSE Manager 5 Proxy
-
Retail Branch Server
-
-
Click
Next
to continue. -
Enter or accept default
NTP Server
. -
Click
Next
to continue. -
Add the
root user
password twice to confirm. -
Click
Next
to continue. -
Adjust
Installation Settings
as required. -
Click
Next
to continue.
This concludes installation of SLE Micro 5.5.
4. Update the host
Once installation completes update the host system.
-
Login to your host.
-
Run the following command"
transactional-update
5. Deploy SUSE Manager 5 as container on SLE Micro 5.5
5.1. Basic and advanced deployment with mgradm
-
from the terminal run the following command as the root user.
mgradm install podman
You must deploy the container as sudo or root. The following error will be displayed at the terminal if you miss this step.
INF Setting up uyuni network 9:58AM INF Enabling system service 9:58AM FTL Failed to open /etc/systemd/system/uyuni-server.service for writing error="open /etc/systemd/system/uyuni-server.service: permission denied"
-
Enter your servers FQDN.
-
Enter a database and certificate password when prompted.
-
Wait for deployment to complete.
-
Open a browser and proceed to your servers FQDN.
In this section you learned the basic method for deploying a SUSE Manager 5 Server container.
-
Prepare an mgradm.yaml file similar to the following example:
# Database password db: password: MySuperSecretDBPass # Certifcate password cert: password: MySuperSecretCAPass # SSL password ssl: password: MySuperSecretSllPassword # If you have these you can provide them to setup your oganization credentials scc: user: ccUsername password: ccPassword # Adminstrators email email: email@example.com
For security, using command line parameters to specify passwords should be avoided: use a configuration file with proper permissions instead.
-
from the terminal run the following command a the sudo user. Replace
uyuni.example.com
with your FQDN.sudo mgradm -c mgradm.yaml install podman <FQDN>
You must deploy the container as sudo or root. The following error will be displayed at the terminal if you miss this step.
INF Setting up uyuni network 9:58AM INF Enabling system service 9:58AM FTL Failed to open /etc/systemd/system/uyuni-server.service for writing error="open /etc/systemd/system/uyuni-server.service: permission denied"
-
Wait for deployment to complete.
-
Open a browser and proceed to your servers FQDN.
In this section you learned how to deploy an SUSE Manager Server container.
5.2. Persistent volumes
If you are just testing out SUSE Manager you do not need to specify these volumes. Specifiying volume locations will generally be used for larger production deployments. |
Many users will want to specify locations for their persistent volumes.
By default Podman
stores its volumes in /var/lib/containers/storage/volumes/
.
You can provide custom storage for the volumes by mounting disks on this path or the expected volume path inside it such as: /var/lib/containers/storage/volumes/var-spacewalk
.
This is especially important for the database and package mirrors.
For a list of all persistent volumes in the container see, Persistent container volumes
6. Container managment
To begin managing your containers see, Container management