8.1.4 Master node requirements
Install the Docker directly on the Master Node as for the Worker Node and Proxy Node, See the Book, IBM Watson Analytics and Stored IQ – ISBN 978-93-90684-49-6, Chapter 8: IBM Cloud Private System section 8.5: Installing Docker 18.09.2 on RHEL 8.0.
8.1.4.1 Installation procedure
The first step is to make a complete backup of the cluster system, before attempting an upgrade. The next step is to create the installation subdirectory:
mkdir /opt/ibm-cloud-private-3.2.1
Installation can then be completed in six main steps:
- Install Docker for your boot node only, as described earlier. This is completed as shown in the Book, IBM Watson Analytics and Stored IQ – ISBN 978-93-90684-49-6, Chapter 8: IBM Cloud Private System section 8.5: Installing Docker 18.09.2 on RHEL 8.0.
- Set up the installation environment:
a. Log in to the boot node as a user with full root permissions.
b. Download the installation file or image.
c. For IBM Cloud Private Native or Enterprise installation: Download the correct file or files for the type of nodes in your cluster from the IBM Passport Advantage website.
d. For a Linux x86_64 cluster, download the ibm-cloud-private-x86_64-3.2.1.tar.gz file.
See: https://www.ibm.com/docs/en/cloud-private/3.2.x?topic=installing-cloud-private-cloud-native-enterprise-editions (Installing IBM Cloud Private Cloud Native and Enterprise editions – IBM Documentation).
Searching using the text IBM Cloud Private 3.2.1 Installation Packages for IBM Cloud shows the resulting software package list, as shown in Figure 8.7:
Figure 8.7: The Search for software by text is used in the IBM Software Access Catalog
Clicking on the result shown in Figure 8.7 above gives the list of installation software packages as shown in Figure 8.8:
Figure 8.8: The list of IBM software installation packages for IBM Cloud Private 3.2.1
The IBM Download Director java applet program has to be installed as shown in Figure 8.9:
Figure 8.9: The Download Director applet required installation when using the AVG Secure browser
Search the above finds IBM Cloud Private version 3.2.1 in IBM PartnerWorld Software Advantage. (Note that you may now have to use two factor authentication with an IBM app for verification. The IBM app must be installed on your mobile phone in order to provide an authentication code to log into the IBM Software Access Catalog.) The download status from IBM Download Director shows the progress of each file as it is downloaded as illustrated in Figure 8.10:
Figure 8.10: The status of the download can be seen, and it shows the size of each file downloaded
On completion of the Download Director file list, the final date, size, and name of each file downloaded is listed by clicking on the Details button as shown in Figure 8.11:
Figure 8.11: The final date, size and name of each file downloaded is listed
The downloaded ibm-cloud-private-x86_64-3.2.1.tar.gz zipped file is copied to the Windows 10 server hosting the VMware with the RedHat Linux 8.0 server as shown in Figure 8.12:
Figure 8.12: The downloaded ibm-cloud-private-x86_64-3.2.1.tar.gz zipped file is copied
Note: The Docker installer image supports Linux on x86_64 systems, Linux on Power 64-bit LE systems, and Linux on IBM Z and LinuxONE systems.
The Fix Packs for the IBM Cloud Private 3.2.1 base system should also be downloaded as shown in Figure 8.13:
Figure 8.13: The Fix Packs for the base 3.2.1 Installation should also be downloaded
The required fixes can now be selected for download as shown in Figure 8.14:
Figure 8.14: The required fixes for IBM Cloud Private 3.2.1 can now be selected for download
The mouse-over over a Fix Pack entry gives a pop-up window detailing the Base IBM Cloud Private 3.2.1 version(s) for which the Fix Pack can be applied as illustrated in Figure 8.15.
Figure 8.15: The Fix Pack icp-3.2.1.2203-build601095-48411 is selected for download and installation
The Download options can be selected from the list shown in Figure 8.16:
Figure 8.16: The Download options can be selected from the list with a default of Download Director
Although we have no option but to download the full Fix Pack set, which is 52.82 GBytes in size. The actual RedHat Linux install file we need is just 16.7 GBytes because the download has three separate install files, one for RHEL Linux, one for IBM Power servers and one for the IBM 390 server system as shown in Figure 8.17:
Figure 8.17: This fix pack set of files is 52.82 GBytes in size, so requires a large amount of disk space
- The Cluster is created by making the Installation directory and unpacking the downloaded installation as follows:
mkdir /opt/ibm-cloud-private-3.2.1
cd /opt/ibm-cloud-private-3.2.1
cp /mnt/hgfs/IBMCloudPrivate/ICP_3.2.1/ibm-cloud-private-x86_64-3.2.1.tar.gz . - Extract the images from the 3.2.1 base installation and load the images into Docker:
tar xf ibm-cloud-private-x86_64-3.2.1.tar.gz -O | docker load
The first page of downloaded container images is shown in Figure 8.18:
Figure 8.18: The first page of downloaded container images for the support of IBM Cloud Private 3.2.1
The next page of downloaded container images is shown in Figure 8.19:
Figure 8.19: The next page of downloaded container images for the support of IBM Cloud Private 3.2.1
- Remove the old Fix Pack to give some additional disk space:
rm -rf /opt/ibm-cloud-private-3.2.0/cluster/images/ibm-cloud-private-x86_64-3.2.0.1907.tar.gz - Move the new installation file to the cluster //cluster/images folder:
mv /opt/ibm-cloud-private-3.2.1/ibm-cloud-private-x86_64-3.2.1.tar.gz /opt/ibm-cloud-private-3.2.0/cluster/images
cd /opt/ibm-cloud-private-3.2.0/cluster - Check the images for install to the cluster:
docker run -e LICENSE=accept –net=host –rm -t -v
“
$(pwd)
“
:/installer/cluster \
ibmcom/icp-inception-amd64:3.2.1-ee check - The docker run to check the prerequisites for the system installation for IBM Cloud Private 3.2.1 are shown in Figure 8.20:
Figure 8.20: The docker run to check the prerequisites for the system installation for the server cluster
- Install the images for IBM Cloud Private version 3.2.1 to the cluster:
docker run -e LICENSE=accept –net=host –rm -t -v
“
$(pwd)
“
:/installer/cluster \
ibmcom/icp-inception-amd64:3.2.1-ee install
The docker run to check for the system installation for the server cluster is shown in Figure 8.21:
Figure 8.21: The docker run to check for the system installation for the server cluster
- View the container statistics:
docker stats
The docker stats command gives the list of running containers, shown in Figure 8.22:
Figure 8.22: The docker stats command displays the list of running containers
- Restart the docker and kubelet services:
service docker restart
The service docker restart command is used to reload and run the docker system as shown in Figure 8.23:
Figure 8.23: The service docker restart command is used to reload and run the docker system
- The docker container supporting systems and db2graph container are restarted:
systemctl restart kubelet
docker start db2graph
