Provide documentation on how to migrate with SUMA

[mlaguilharre]

4 Cluster Updates:

https://documentation.suse.com/suse-caasp/4.5/single-html/caasp-admin/#_cluster_updates

My customer like to have a procedure that outline step to migrate when yu have a SUSE Manager server. Currently the information is scattered among different documentation, CaasP, SLE, SUSE Manager ..

Draft proposal:

1.First unlock the client:
https://documentation.suse.com/external-tree/en-us/suma/4.1/suse-manager/client-configuration/system-locking.html#_syste
m_locks_on_salt_clients

2.Build a Content Lifecycle Management for SLES15SP2 Base and Caasp 4.5 https://documentation.suse.com/external-tree/en-us/suma/4.1/suse-manager/administration/content-lifecycle.html

3.Modify the base channel on admin and cluster note to point to new base channel.

3.Run zypper migration on admin first then cluster node.

4. If needed sync containers https://documentation.suse.com/suse-caasp/4.5/single-html/caasp-airgap/#airgap-container_registry .

5.Run skuba update from admin node.

skuba cluster upgrade plan
skuba addon upgrade plan
skuba addon upgrade apply

[Martin-Weiss]

I believe instead of "zypper migration" we have to run "zypper dup" as "migration" would like to change channel assignments against SCC/SMT/RMT and might not work against SUSE Manager..

[r0ckarong]

@chabowski This sounds like a "Best Practice" document since this spans across several products. I am not aware of another good way to handle this. I wouldn't think this can go straight into the CaaSP docs since it involves so much of SUMA.

cc / @kkaempf @qnetter

[kkaempf]

This has already been discussed on engineering level and I'm all for having this properly documented. It's mostly channel management and no 'dark magic' 😉

I'd like to get buy-in from @qnetter and @BLandorff as this needs cycles from both engineering groups.