Upgrading IBM Cloud Pak for MultiCloud Management from V1.2.0 to V1.3.0 on OCP3.11
In this post, we will go through the steps involved in upgrading IBM Cloud Pak for Multicloud Management V1.2.0 to V1.3.0 on Openshift 3.11. The mode of upgrade is offline.
The infrastructure used in this case is for demo purpose and the details are as below:
All steps involved are performed from the ansible node.
Before upgrading the IBM Cloud Pak for Multicloud Management instance ensure that following steps are completed.
1) IBM Cloud Pak for Multicloud Management V1.2.0 is installed and the console is accessible
2) Login to the ansible node (or node that was used in the installation of V1.2.0 )
3) Login to OCP Master using the below command:
oc login <openshifturl> -u <username> -p <password>
The user should have cluster-admin authority
4) Download the Installer Package from the IBM Passport Advantage site. For our upgrade we will be using the following image:
Once the pre-requisites are verified and the required installation images are downloaded, complete the following steps to upgrade IBM Cloud Pak for Multicloud Management on OCP 3.11
1) cd to the directory where the “ibm-cp4mcm-core-1.3-x86_64.tar.gz” file is kept on the ansible host
2) Load the container images to the local docker registry by running the below command:
tar xf ibm-cp4mcm-core-1.3-x86_64.tar.gz -O | sudo docker load
The image load progresses as shown below:
3) Once the container images are loaded to the docker registry, create a installation directory and copy the cluster directories from the previous installation directory to the new cluster folder. Use a different installation directory than you used for the previous version. This is done by executing the following commands:
mkdir /opt/ibm-multicloud-manager-1.3
cd /opt/ibm-multicloud-manager-1.3
cp -r /opt/ibm-multicloud-manager-1.2/cluster .
/opt/ibm-multicloud-manager-1.2 is the full path to your previous installation directory
4) Change to the cluster directory within your new installation directory by executing the below command:
cd /opt/ibm-multicloud-manager-1.3/cluster
5) Set the multicluster-hub.etcd.accessModes to ReadWriteMany and multicluster-hub.etcd.persistenceto true in the config.yaml file, which is located in the cluster folder. Add the below lines to the config.yaml file if it is not present already:
When persistence is set to true, either the storageClassName or the local directory (default is /var/lib/etcd-mcm) for persistence volume in all management nodes for etcd is required. In our case, the storageClassName is the default dynamic storage class that is available in the environment.
6) Upgrade the instance by running the upgrade command:
sudo docker run -t — net=host -e LICENSE=accept -v $(pwd):/installer/cluster:z -v /var/run:/var/run:z -v /etc/docker:/etc/docker:z — security-opt label:disable ibmcom/mcm-inception-amd64:3.2.5 upgrade
(the above command should be run in the /opt/ibm-multicloud-manager-1.3 directory)
The upgrade starts as shown in below screen:
7) The upgrade completes with a Play Recap (failed = 0 confirms that there were no failures in the playbook) and access information for your cluster is displayed as shown below :
8) Access the URL to connect to the IBM Cloud Pak for Multicloud Management console as shown below:
9) Login with the User admin and Password as given in default_admin_password in the config.yaml file.
The system is now ready for use.
