Upgrade Using the Content Lifecycle Manager

When you have many SUSE Linux Enterprise Server clients to manage, you can automate in-place upgrades using the content lifecycle manager.

Prepare to Upgrade

Before you can upgrade your clients, you need to make these preparations:

  • Create a content lifecycle project

  • Create an activation key

  • Create an autoinstallation distribution

  • Create an autoinstallation profile

Procedure: Creating a Content Lifecycle Project
  1. Create a content lifecycle project for your distribution. For more information, see administration:content-lifecycle.adoc.

  2. Ensure you a choose a short but descriptive name for your project.

  3. Include all source channel modules that you require for your distribution.

  4. Add filters as required, and set up at least one environment.

Procedure: Creating an Activation Key
  1. Create an activation key for your distribution. For more information, see client-configuration:activation-keys.adoc.

  2. Ensure your activation key includes all filtered project channels.

Procedure: Creating an Autoinstallation Distribution
  1. Create an autoinstallation distribution for every base channel you want to migrate. For more information, see client-configuration:autoinst-setup.adoc.

  2. Give your distribution a label that references the name of the content lifecycle project.

  3. In the Installer Generation field, select the SLES version you are using.

Procedure: Creating an Autoinstallation Profile
  1. Create an autoinstallation profile for every target distribution and service pack you want to upgrade to. For more information, see client-configuration:autoinst-setup.adoc.

  2. You must use a different profile for Salt and traditional clients.

  3. You can use variables in the profile to distinguish between the different lifecycle environments.

For example autoinstallation profiles, see https://github.com/SUSE/manager-build-profiles/tree/master/AutoYaST.

Use these variables in your autointallation profiles for automating in-place upgrades:

Example: Variables for Use in Autoinstallation Profiles
registration_key=1-15sp1-demo-test
org=1
channel_prefix=15sp1-demo-test
distro_label=15sp1-demo-test
Example: Entry for Use in Autoinstallation Profiles
 <listentry>
     <ask_on_error config:type="boolean">true</ask_on_error>
     <media_url>https://$redhat_management_server/ks/dist/child/$channel_prefix-sle-module-web-scripting15-sp1-pool-x86_64/$distro_label</media_url>
     <name>$channel_prefix SLE-Module-Web-Scripting15-SP1 Pool for x86_64 </name>
     <product>Web Scripting Module 15 SP1 x86_64 Pool</product>
</listentry>

Upgrade

When you have prepared the server for the upgrade, you can provision the clients.

Procedure: Provisioning the Clients
  1. In the Uyuni Web UI, navigate to Systems  System List, and select the clients you want to provision to add them to the system set manager.

  2. Navigate to Systems  System Set Manager  Overview and click the Provisioning tab.

  3. Select the autoinstallation profile to use.

For clients that are able to use PXE, the migration is automated as soon as you have provisioned them. For all other clients, you can use Cobbler to perform the upgrade.

Procedure: Using Cobbler to Upgrade Clients
  1. At the command prompt, as root, check the available Cobbler profiles:

    cobbler profile list
  2. Build the ISO file with your chosen profile:

    cobbler buildiso --iso=/tmp/SLE_15-sp1.iso --profiles=SLE_15-sp1:1:Example

For more information about using Cobbler to provision clients, see client-configuration:cobbler.adoc.