Applies to SUSE Linux Enterprise Micro 5.5

10 Post-deployment steps #

The chapter describes registration of SLE Micro and covers extensions available for SLE Micro.

10.1 Registration #

Registering the system is possible from the command line using the transactional-update register command. For information that goes beyond the scope of this section, refer to the inline documentation with SUSEConnect --help

Procedure 10.1: Product registration with SUSEConnect #

To register SUSE Linux Enterprise Micro with SUSE Customer Center, run transactional-update register as follows:
```
# transactional-update register -r REGISTRATION_CODE -e EMAIL_ADDRESS
```
To register with a local registration server, additionally provide the URL to the server:
```
# transactional-update register -r REGISTRATION_CODE -e EMAIL_ADDRESS \
--url "https://suse_register.example.com/"
```
Replace REGISTRATION_CODE with the registration code you received with your copy of SUSE Linux Enterprise Micro. Replace EMAIL_ADDRESS with the e-mail address associated with the SUSE account you or your organization uses to manage subscriptions.
Reboot your system to switch to the latest snapshot.
SUSE Linux Enterprise Micro is now registered.

10.2 Managing extensions #

SLE Micro supports the following extensions:

SUSE Linux Enterprise Live Patching: The extension is available only for the x86 (except for the real-time kernel) and IBM Z architectures. Bear in mind that the extension might require an additional subscription.
Package Hub: A free module that provides access to community-maintained packages. Packages in the Package Hub are approved by SUSE for use on SUSE Linux Enterprise Server, thus the packages might not be installable on SLE Micro.

As the extension activation or deactivation is performed as a transactional-update command and thus creates a new snapshot, you need to restart your system to boot to the new snapshot and apply the changes.

10.2.1 Activating extensions #

To activate an extension, proceed as follows:

List available extensions by running:

# transactional-update --quiet register -list-extensions

The output provides you with a command to activate the extensions, for example, for the SUSE Linux Enterprise Live Patching:
```
# transactional-update register -p sle-module-live-patching/15.4/x86_64 \
  -r registration code
```

If you activated the SUSE Linux Enterprise Live Patching extension, you need to perform additional steps as described below:

Procedure 10.2: Completing activation of the SUSE Linux Enterprise Live Patching #

Configure libzypp in the /etc/zypp/zypp.conf file as follows:
multiversion = provides:multiversion(kernel)
to keep the current kernel running while patching the system, otherwise you may get dependency conflicts while kernel updates are being applied.
multiversion.kernels = latest
after applying the live patch, a cleanup of kernels is performed in the new snapshot. If not set, the snapshot keeps the previous kernel and performs kernel updates also on the previous kernel.
Additionally, set LIVEPATCH_KERNEL='always' in the /etc/sysconfig/livepatching file.
Note: Matching version of the kernel-default-livepatch and kernel
To ensure that the live patches will be installed even after the kernel upgrade, install the matching version of the kernel-default-livepatch package.

Now, install the extension by running:

# transactional-update pkg install kernel-default-livepatch

Reboot your system to switch to the new snapshot.

10.2.2 Deactivating extensions #

To deactivate the extension, run the following command:

# transactional-update register -d \
  -p EXTENSION_NAME

For example, for the SUSE Linux Enterprise Live Patching extension, the command is as follows:

# transactional-update register -d \
  -p sle-module-live-patching/15.4/x86_64