With LTS2, it is necessary to migrate existing management server environments running on VMs to be able to run as a management cluster. The following steps walk through that process.
./download.sh v-5.6.0-xxxx
./install.sh v-5.6.0-xxxx
/opt/pf9/airctl/airctl migrate-pre-checks --config /opt/pf9/airctl/conf/airctl-config.yaml
Backup Management Server
/opt/pf9/airctl/airctl backup --config /opt/pf9/airctl/conf/airctl-config.yaml
Ensure that the backup generated has the mongo and mysql data.
/opt/pf9/airctl/airctl stop --config /opt/pf9/airctl/conf/airctl-config.yaml
/opt/pf9/airctl/airctl unconfigure-du --config /opt/pf9/airctl/conf/airctl-config.yaml
Update Airctl config to use new Management Server values
Specifically, the following fields need to be set in**````/opt/pf9/airctl/conf/airctl-config.yaml:``**
installDriver: DDU
kubeCfgPath: /etc/nodelet/airctl-mgmt/certs/admin.kubeconfig
bootstrapCfgPath: /etc/nodelet/airctl-mgmt/airctl-mgmt.yaml
svcDeploymentTimeout: 600
storageProvider: hostpath-provisioner
externalIP: <external-ip>
privateRegistryType: DU
The externalIP needs to be a VIP on the same L2 network as the nodelet host(s), but different from the nodelet host's IP.
Uninstall docker
yum remove docker-ce containerd
Install libcgroup-tools
yum install libcgroup-tools
Deploy nodelet cluster
/opt/pf9/airctl/airctl advanced-ddu create-mgmt --config /opt/pf9/airctl/conf/airctl-config.yaml
Initialize airctl
/opt/pf9/airctl/airctl init --config /opt/pf9/airctl/conf/airctl-config.yaml
Deploy Management Cluster
/opt/pf9/airctl/airctl start --config /opt/pf9/airctl/conf/airctl-config.yaml
Wait for Management Cluster services to be up
The airctl status command reports the state of the Management Server. Wait until the status command reports the task state as ready.
[centos@airctl-host ~]$ /opt/pf9/airctl/airctl --config /opt/pf9/airctl/conf/airctl-config.yaml status
------------- deployment details ---------------
fqdn: airctl-1.pf9.localnet
cluster: airctl-1.pf9.localnet
task state: ready
-------- region service status ----------
task state: ready
desired services: 42
ready services: 42
Migrate Management Server data to Management Cluster
/opt/pf9/airctl/airctl migrate --backup-file <tar.gz-of-cdu-backup> --config /opt/pf9/airctl/conf/airctl-config.yaml
Same version upgrade of Management Server
/opt/pf9/airctl/airctl upgrade --config /opt/pf9/airctl/conf/airctl-config.yaml
Wait for Management Server services to be up
The airctl status command reports the state of the Management Server. Wait until the status command reports the task state as ready.
[centos@airctl-host ~]$ /opt/pf9/airctl/airctl --config /opt/pf9/airctl/conf/airctl-config.yaml status
------------- deployment details ---------------
fqdn: airctl-1.pf9.localnet
cluster: airctl-1.pf9.localnet
task state: ready
-------- region service status ----------
task state: ready
desired services: 42
ready services: 42
Configure PMK hosts to work with Management Cluster
/opt/pf9/airctl/airctl configure-hosts --reset-pf9-managed-docker-conf --skip-docker-img-import --config /opt/pf9/airctl/conf/airctl-config.yaml
Upgrade PMK hosts to new components of Management Cluster
/opt/pf9/airctl/airctl upgrade-hosts --config /opt/pf9/airctl/conf/airctl-config.yaml
Wait for Task State to report Ready again
[centos@airctl-host ~]$ /opt/pf9/airctl/airctl --config /opt/pf9/airctl/conf/airctl-config.yaml status
------------- deployment details ---------------
fqdn: airctl-1.pf9.localnet
cluster: airctl-1.pf9.localnet
task state: ready
-------- region service status ----------
task state: ready
desired services: 42
ready services: 42
Migrate previous clusters to run on Management Cluster
/opt/pf9/airctl/airctl migrate-clusters --config /opt/pf9/airctl/conf/airctl-config.yaml
Push Docker images to Management Cluster docker registry
sudo /opt/pf9/airctl/airctl --config /opt/pf9/airctl/conf/airctl-config.yaml advanced-du push-images --img-tar /opt/pf9/airctl/imgs/docker-imgs-<airctl-release-version>.tar.gz