OS Migration for SMCP 5.12
1. Run step 1-4 from this document to take the appropriate backup from the cluster, along with etcd backup and cleanup the old cluster
Before cluster destruction, take the backup of /etc/hosts from the nodelet cluster node. Apply the changes once the management cluster is up.
- Backup Current System : Take a fresh backup of the upgraded SMCP cluster (SMCP 5.10) and store it in a secure location.
- Take etcd Snapshot
- Destroy Old Cluster
- Clean Up Configuration
Take the backup of airctl-config.yaml and nodelet-bootstrap.yaml for references.
- Follow next two step from the SMCP installation guide to setup nodelet cluster on the the new OS host.
Ensure the S3 DNS entry 34.35.69.42 s3-us-west-1.amazonaws.com is added to the nodelet-bootstrap.yaml. Also, note that the userImages: section in the nodelet-bootstrap.yaml is not required.
dns corednsHosts34.35.69.42 s3-us-west-1.amazonaws.com isAirgappedtruesystemImages/opt/pf9/airctl/imgs/kubedu-imgs-v-5.10.0-3248001.tar.gz/opt/pf9/airctl/imgs/nodelet-imgs-v-5.10.0-3248001.tar.gzTo enable passwordless access to the workload hosts from the DU, update the ~/.ssh/authorized_keys file on all workload hosts with the public key from the nodelet hosts, if it has been changed
3. Follow step 7-9 from this document to create management cluster and restore the cluster.
If the external IP of the nodelet cluster has changed, we need to update all the attached nodes with the new IP. Run the following command to update the /etc/hosts file without performing any package installation:
/opt/pf9/airctl/airctl configure-hosts --skip-docker-img-import --skip-docker-install --skip-yum-repo-install --config /opt/pf9/airctl/conf/airctl-config.yaml