Proxy Migration from 4.3 to 5.1

1. Requirements and considerations

  • 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 及更高版本不再支持传统联系协议。

在将 SUSE Manager 4.3 代理迁移至 SUSE Multi-Linux Manager 5.1 之前，需要先迁移 SUSE Manager 4.3 服务器，详情请参见 将 SUSE Multi-Linux Manager 服务器迁移到容器化环境。

2. 简介

在 SUSE Multi-Linux Manager 4.3 中，可以使用三种不同的方法来部署代理：

  • 基于 RPM 的部署

  • 基于 Podman 运行的容器化部署

  • 基于 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

由于不支持就地迁移，需要部署一个使用新 FQDN 的 SUSE Multi-Linux Manager 新代理。有关在 SL Micro 6.1 或 SUSE Linux Enterprise Server 15 SP7 上部署新代理的详细信息，请参见 安装 SUSE Multi-Linux Manager 代理。

4. Migrate clients to the new proxy

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 the old to the 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 文件同步

容器化代理不使用 tftpsync 机制传输 tftproot 文件。相反，这些文件会按需自动下载并缓存。

为避免在 cobbler sync 运行期间出现误报错误，需要将迁移后的 4.3 代理从 tftpsync 机制中去除。

如果您之前已将 4.3 代理配置为接收 TFTP 文件，则需要选择以下配置选项之一：

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

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.