Part 2: Installing Terraform & Service Automation Module on IBM Cloud Pak for MultiCloud Management V1.3.0
In Part 1 of the series, we explored the steps involved in completing the prerequisites required for installing the Terraform and Service Automation Module on ICP4MCM.
In this post we will look at the steps involved in the installation. Here we are going to install the module offline on the Openshift 3.11 cluster. There are other methods available for installation which can be accessed in the links given below:
- Installing Terraform & Service Automation Module offline on IBM Managed RedHat OpenShift cluster
- Installing Terraform & Service Automation Module online
- Installing Terraform & Service Automation Module online IBM Managed RedHat OpenShift cluster
There are two ways to install the module:
a) Through UI
b) Using Command Line
In this post we will examine the UI based installation in detail. For details about the Command Line based installation click here and complete activities detailed in step 4.
Complete the below steps to install the Terraform & Service Automation Module.
- Log in to IBM Cloud Pak for Multicloud Management URL and Manage > Helm Repositories
2. Here click on Sync Repositories
3. Click on Sync to start the repository sync process as shown below:
4. Wait for the sync operation to complete as shown below:
5. Go to Catalog and search for ibm-cam
6. Click on the local-charts. This opens the chart as shown below:
7. Review instructions and click Configuration tab (click on Configure button)
8. In the Configuration section, enter the following values and accept the license agreement.
a) Release name — Enter cam in release name.
b) Target namespace — From the drop down list, select Services.
Note: The services namespace already has the resources required for Terraform & Service Automation to install. If you are installing in a different namespace, use these commands to copy over the required resources:
kubectl get secret oauth-client-secret -n services -–export -o yaml | kubectl apply -n <desired namespace> -f -
kubectl get cm oauth-client-map -n services --export -o yaml | kubectl apply -n <desired namespace> -f -c) Select I have read and agreed to license agreements to accept the license agreements.
The below screen grab shows the values provided:
8. In the Parameters > Quick Start > Global section, enter the following values:
a) IAM Service API Key — Enter the IAM service API Key. It is used to generate Terraform & Service Automation specific Service ID and API Key. The Terraform & Service Automation API Key is used to interact with the platform authorization.
9. In the Parameters > All parameters section, enter the following values if not populated already (these are generally auto populated):
a) Worker node architecture: amd64
b) For offline installation, Docker image pull secret is “default”.
c) Platform: icp
d) Product Identifier — Enter the contents of the {{site.data.keyword.icp-cam-prod-id-4.1.txt}} file that you downloaded from IBM Passport Advantage. (This is populated already by default)
10. Keep all other values as defaults except for the persistent volumes for mongo db database, log files, terraform, and Terraform & Service Automation Module Template Designer. In my environment I have used GlusterFS volumes with Dynamic Provisioning enabled. Hence during the install step, I chose the Option of “Use Dynamic Provisioning” and set “Dynamic Provisioning: Storage Class Name” to the “GlusterFS storage” class for all the chart parameters for storage.
11) Once required values have been entered, click on the Install button to start the helm chart installation.
12) The installation starts and deploys the Terraform & Service Automation Module on ICP4MCM on Openshift 3.11.
13) Once installation is completed the Terraform & Service Automation Module can be accessed via the URL: https://cam.apps.<mcm console>. In my installation the URL is https://cam.apps.ose-ose-4.fyre.ibm.com/ and is as shown below after login:
This completes the steps involved in the installation of he Terraform & Service Automation Module on the IBM Cloud Pak for Multicloud Management deployed on OpenShift V3.11
