Migrating from SUSE Multi-Linux Manager Retail Branch Server 4.3

This guide describes how to migrate one or more SUSE Multi-Linux Manager Retail Branch Server Servers from SUSE Multi-Linux Manager Branch Server 4.3 to the SUSE Multi-Linux Manager Retail Branch Server 5.1

1. Overview

  • Synchronize SUSE Multi-Linux Manager Retail Branch Server channels

  • Backup existing SUSE Multi-Linux Manager for Retail 4.3 Branch Server Proxy

  • Validate branch objects were created

  • Migrate Branch Server Proxy host

  • Validate proxy functionality

4.3 branchserver migration

2. Synchronize SUSE Multi-Linux Manager Retail Branch Server channels

See SUSE Multi-Linux Manager Proxy Deployment how to synchronize product channels for a proxy systems.

Depending on the host operating system:

  • SUSE Linux Micro 6.1 uses SUSE Multi-Linux Manager Retail Branch Server Extension 5.1 channels

  • SUSE Linux Enterprise Server 15 SP7 uses SUSE Multi-Linux Manager Retail Branch Server Extension for SLE 5.1 channels

3. Backup existing SUSE Multi-Linux Manager Retail Branch Server 4.3

SUSE Multi-Linux Manager for Retail 5.1.2 includes automated backup-migration procedure for both kinds of SUSE Multi-Linux Manager Proxy variants. This procedure collects all required data and uploads them to the SUSE Multi-Linux Manager Server. For SUSE Multi-Linux Manager Retail Branch Server this tool also creates and migrates Saltboot related entities.

Squid cache data and POS images are not backed up. Due to change in functionality these data are not migrated and instead redownloaded from the server.

See retail-deploy-terminals.adoc#_synchronize_images_to_the_branch_server how to warm up the cache.

There are multiple ways to initiate SUSE Multi-Linux Manager Retail Branch Server 4.3 migration:

  • API call

    Replace $proxyid by a server id of the branch proxy, or multiple server ids separated by a comma.

    mgrctl api login
mgrctl api post proxy/backupConfiguration '{\"sids\":[$proxyid]}'

  • Salt call

    Replace $proxy in command below by branch proxy minion id or -L proxyminionid1,proxyminionid2,…​ when addressing multiple branch proxies.

    salt $proxy proxy.backup

It is recommended to do a manual backup of the proxy as well, particularly if there are custom modifications present.

SUSE Multi-Linux Manager Retail Branch Server can still be used after backup step as before, however because some formulas were disabled by the backup/migration step, next highstate or image-sync state application will not work properly.

Migrate the server host as soon as possible after backup step is performed.

4. Validate branch objects were created for migrated branches

Backup/migration step will create new Saltboot objects:

  • Saltboot Group formula with settings from the original formulas is assigned to the branch group.

  • New cobbler profile is created for the branch group:

    # mgrctl exec -- cobbler profile report --name $branchid:S:$orgid:$orgname

  • New cobbler systems are created for all assigned terminals:

    # mgrctl exec -- cobbler system find --kernel-options "MINION_ID_PREFIX=$branchid"

5. Migrate SUSE Multi-Linux Manager Retail Branch Server host

You can either upgrade the existing host to SUSE Linux Enterprise Server 15 SP7 using AutoYaST, or perform a fresh installation of SL Micro 6.1.

5.1. Upgrade to SUSE Linux Enterprise Server 15 SP7 using AutoYaST

Create and use AutoYAST profiles to migrate or reinstall the proxy host.

5.1.1. Prepare autoinstallation distribution based on SUSE Linux Enterprise Server 15 SP7

  • Download or obtain SUSE Linux Enterprise Server 15 SP7 installation ISO to the server host

  • Use mgradm distribution copy $path_to_the_iso to copy installation files to the container

  • Register the autoinstallation distribution, see 可自动安装的发行套件.

5.1.2. Prepare autoinstallation profile

For more information, see 自动安装配置文件.

Create an autoinstallation profile based previously created distribution. As a profile use profile provided at https://github.com/SUSE/manager-build-profiles/blob/master/AutoYaST/SUSE-Multi-Linux-Manager/SUSE%20Multi-Linux%20Manager%20Proxy/MLM_RBS-51-SLES-Upgrade.xml - Once profile is created, switch to Variables tab and fill in required variables:

+

org='organization_id'
distrotree='autoinstallation_distribution_label_from_previous_step'
channel_prefix='clm_channel_prefix' or blank for SCC channels
registration_key='activation_key_for_post_upgrade'

  • In tab Autoinstallation File you can see complete rendered profile for additional inspection

5.1.3. Provision autoinstallation of the proxy

Schedule an autoinstallation on the old SUSE Multi-Linux Manager Branch Server 4.3 using the profile created in previous step.

  • Use Web UI interface Provisioning tab at the System view of migrating branch server

  • Or use API call system/provisionSystem to schedule the migration. For example execute following snippet from the SUSE Multi-Linux Manager host:

    mgrctl api login
mgrctl api post system/provisionSystem '{\"sid\":$proxyid,\"profileName\":\"$profileName\"}'

5.2. Reinstall with SL Micro 6.1

SL Micro 6.1 requires a fresh installation on the host.

Perform the backup of the existing 4.3 Branch Server before proceeding with the host reinstallation. For more information see [proxy-backup-43].

5.2.1. 准备 SL Micro 6.1 主机

5.2.1.1. 下载安装媒体
过程：下载安装媒体

  1. 访问 https://www.suse.com/download/sle-micro/，找到 SL Micro 6.1 的安装媒体，并下载相应媒体文件。

  2. Prepare a DVD or USB flash drive with the downloaded .iso image for installation.

5.2.1.2. 安装 SL Micro 6.1

有关虚拟机或物理机的准备工作详细信息，请参见 SL Micro 部署指南。

过程：安装 SL Micro 6.1

  1. 插入包含 SLE Micro 6.1 安装映像的 DVD 或 USB 闪存盘（USB 磁盘或密钥）。

  2. 引导或重引导您的系统。

  3. Use the arrow keys to select Installation.

  4. 调整键盘和语言。

  5. Click the checkbox to accept the license agreement.

  6. Click Next to continue.

  7. 跳过注册步骤。SL Micro 6.1 权利已包含在 SUSE Multi-Linux Manager 权利中，因此不需要单独的注册代码。

  8. 单击 下一步 继续。

  9. On the NTP Configuration page click Next.

  10. On the Authentication for the System page enter a password for the root user. Click Next.

  11. On the Installation Settings page click Install.

将 SL Micro 6.1 和 SUSE Multi-Linux Manager 5.1 安装为扩展的过程到此完成。

5.2.1.3. 更新系统
过程：更新系统

  1. 以 root 身份登录。

  2. 运行 transactional-update：

    transactional-update

  3. 重引导。

SL Micro 设计为默认自动更新，并会在应用更新后重引导。但是，这种行为对于 SUSE Multi-Linux Manager 环境而言是不利的。为了防止服务器自动更新，SUSE Multi-Linux Manager 会在引导过程中禁用 transactional-update 计时器。

如果您希望保留 SL Micro 的默认行为，请运行以下命令来启用计时器：

systemctl enable --now transactional-update.timer

5.2.2. Register and deploy the proxy

Procedure: Registering and deploying the proxy

  1. Once the host is prepared, register the new SL Micro 6.1 system to the SUSE Multi-Linux Manager Server as a client. It is recommended to use the same minion ID as the original 4.3 Branch Server. For more information, see 客户端注册.

  2. On the SUSE Multi-Linux Manager Server, generate the proxy configuration for the new branch server. For more information, see installation-and-upgrade:container-deployment/mlm/proxy-deployment-mlm.adoc#generate-proxy-config.

  3. Transfer the configuration to the SL Micro 6.1 host and install the proxy:

    mgrpxy install podman config.tar.gz

  4. Start the proxy:

    mgrpxy start

  5. Once the proxy is operational, the SUSE Multi-Linux Manager Server will automatically deploy the backed up configuration during the next Hardware Refresh step.

6. Validate proxy functionality

After migration is finished and salt is started first time, backed up proxy configuration is automatically deployed during Hardware Refresh step.

After finishing all onboarding steps, validate required proxy functionality.