Documentation survey

Proxy Migration from 4.3 to 5.1

1. 要求和注意事项

  • To migrate a SUSE Manager 4.3 Proxy to SUSE Multi-Linux Manager 5.1, you require a new machine with SL Micro 6.1 or SUSE Linux Enterprise Server 15 SP7 and mgrpxy installed.

  • An in-place migration from SUSE Manager 4.3 to 5.1 is not supported, regardless of whether the chosen host operating system is SL Micro 6.1 or SUSE Linux Enterprise Server 15 SP7.

Before migrating from SUSE Manager 4.3 to 5.1, any existing traditional clients including the traditional proxies must be migrated to Salt. For more information about migrating traditional SUSE Multi-Linux Manager 4.3 clients to Salt clients, see https://documentation.suse.com/suma/4.3/en/suse-manager/client-configuration/contact-methods-migrate-traditional.html.

  • SUSE Multi-Linux Manager 5.0 及更高版本不再支持传统联系协议。

Before migrating a SUSE Manager 4.3 Proxy to SUSE Multi-Linux Manager 5.1, the SUSE Manager 4.3 Server needs to be migrated first, see 将 SUSE Multi-Linux Manager 服务器迁移到容器化环境.

2. Introduction

In SUSE Multi-Linux Manager 4.3, the proxy can be deployed using three different methods:

  • RPM based

  • containerized running on Podman

  • containerized running on k3s

In SUSE Multi-Linux Manager 5.1, RPM based support was removed, and only the containerized version running with podman or k3s is supported. Furthermore, the management of the containerized proxy running with Podman was re-designed and made simpler with the mgrpxy tool.

3. Deploy a New SUSE Multi-Linux Manager 5.1 Proxy

Because an in-place migration is not supported, a deployment of a new SUSE Multi-Linux Manager proxy with a new FQDN is required. For more information on deploying a new proxy on SL Micro 6.1 or SUSE Linux Enterprise Server 15 SP7 see 安装 SUSE Multi-Linux Manager 代理 .

4. 将客户端迁移到新代理

Before migrating the clients, ensure that the new SUSE Multi-Linux Manager 5.1 Proxy is already deployed and fully functional.
Procedure: Migrating Clients from old to new Proxy

  1. 登录到 SUSE Multi-Linux Manager 服务器 Web UI。

  2. 在左侧导航栏中，选择系统  系统列表。

  3. 导航到旧的 4.3 代理页面，然后单击代理选项卡。

  4. 在“SSM”中选择所有系统。

  5. 在左侧导航栏中，选择系统  系统集管理器。

  6. 选择子菜单其他  代理。

  7. 从下拉列表中选择要迁移到的新代理。

  8. 单击 更改代理。

所有选定的客户端现在都将迁移到新代理。您可以检查日程安排进度，以确认所有客户端是否已成功迁移。

After a few minutes, the clients will start to show the new connection path. When all clients have the connection path under the new proxy, the old SUSE Manager 4.3 Proxy system is not needed anymore and can be removed.

5. TFTP files synchronization

Containerized proxies do not use tftpsync mechanism to transfer tftproot files. Instead these files are transparently downloaded and cached on demand.

To prevent false positive errors during cobbler sync run, migrated 4.3 proxies need to be removed from tftpsync mechanism.

If you previously configured a 4.3 proxy to receive TFTP files, one of the following configuration option is required:

要在容器内访问外壳，请在容器主机上运行以下命令：

mgrctl term

In the SUSE Multi-Linux Manager 5.1 server container, run configure-tftpsync.sh with the list of remaining 4.3 proxies as arguments. If no 4.3 proxies remain, run configure-tftpsync.sh with no arguments.

In the SUSE Multi-Linux Manager 5.1 server container, manually remove the relevant proxy from the proxies setting in the /etc/cobbler/settings.yaml file. If there are no 4.3 proxies remaining, then manually remove the proxies list completely.