Changing the Base OS for SUSE Multi Linux Manager 5.0

SUSE Manager 5.0
SUSE Multi Linux Manager 5.0
SUSE Linux Enterprise Micro 5.5
SUSE Linux Enterprise Server 15 SP6

IMPORTANT - This TID is specifically for SUMA5.0/SMLM5.0.  For SMLM 5.1, see TID#000021990.

SMLM5.0 initially deployed on a SLEM container host can be "migrated" to a SLES container host.

This can be done by re-pointing the persistent storage data store (/var/lib/containers/storage/volumes/) from the SMLM5 instance running on the SLEM container host to an instance running on a SLES15SP6 container host.

Example 1, useful in Hypervisor scenarios...
1. Assuming all channel sync is complete, shut down the SUMA5/SMLM5 container:
# mgradm stop.
2. Make a note of the persistent storage entries from the SLEM container host /etc/fstab to the SLES container host /etc/fstab, for example:
UUID=91ca0129-315b-4776-bb59-51c27833ff25 /var/lib/containers/storage/volumes xfs defaults,nofail 1 2

3. In the Hypervisor, detach the disk storage devices from the SLEM container host VM and present them to the SLES container host VM.
4. Install and configure SLES, ensuring the <fqdn> and IP match that of the original SLEM container host. 
5. Copy the persistent storage entries from the SLEM container host /etc/fstab noted from above and apply to the SLES container host /etc/fstab

6. Deploy SUMA5/SMLM5 on SLES15SP6 as per the official SUSE documentation, ensuring the <fqdn> and IP are the same as that of the original SLEM container host.

IMPORTANT: skip the mgr-storage-server section.  The installer will automatically detect and configure the persistent storage accordingly.  If mgr-storage-server is run, it may render the persistent storage unusable.

Example 2, useful for limited disk space/server instance scenarios...
1. Assuming all channel sync activity is complete, shut down the SUMA5/SMLM5 container:
# mgradm stop
2. Copy the contents of the persistent storage devices from the SLEM container host to a temporary storage location, for example:
# rsync -Pav /var/lib/containers/storage/volumes/ <<temp_mount_point>>
3. Shut down the SUMA5/SMLM5 system:
# mgradm stop && shutdown -P
4. Install and configure SLES the official SUSE documentation, ensuring the <fqdn> and IP are the same as that of the original SLEM container host.
5. Deploy SUMA5 on SLES as per the official SUSE documentation.
6. Shut down the SUMA container:
# mgradm stop
7. Copy the contents of the <<temp_mount_point>> to the SLES container host:
# rsync -Pav <<temp_mount_point>> root@<sles-fqdn>:/var/lib/containers/storage/volumes
8. Start SUMA5/SMLM5 on SLES:
# mgradm start
SUMA5/SMLM5 will automatically use the persistent storage accordingly.

These procedures are to be used as guidelines, as customer environments may differ in complexity.

IMPORTANT - This procedure has been tested moving persistent data stores from SUMA 5.0.x to SUMA 5.0.x instances.  Do not use it to move from SUMA 5.0.x to SMLM 5.1 instances, it will fail.

Please note the mgradm migrate command is for migrating SUMA4 to SMLM5, but will NOT migrate SMLM5 on SLEM to SMLM5 on SLES.

Also please note that while a subscription of SLE Micro 5.5 is included with SUMA5/SMLM5, to run SUMA5/SMLM5 on SLES15SP6, a separate SLES15 subscription is required.