IBM Cloud Docs
Getting started with IBM Cloud Pak for Multicloud Management V1.3

Getting started with IBM Cloud Pak for Multicloud Management V1.3

The IBM Cloud Pak for Multicloud Management, running on Red Hat OpenShift, provides consistent visibility, governance, and automation from on-premises to the edge. Enterprises gain capabilities such as multicluster management, event management, application management, and infrastructure management. Enterprises can use this Cloud Pak to help increase operational efficiency that is driven by intelligent data, analysis, and predictive golden signals, and gain built-in support for their compliance management. For more details, see the documentation.

What's inside this Cloud Pak

In addition to the default features for managing multicloud environments, the IBM Cloud Pak for Multicloud Management includes the following installable modules that you can add to your cluster to manage applications and infrastructure, and to automate tasks:

  • Monitoring Module for monitoring the performance and availability of cloud applications in hybrid cloud environments.
  • Terraform & Service Automation Module for cluster security, operating efficiency, and appropriate service level delivery.
  • CloudForms for controlling and managing cloud infrastructures.
  • Red Hat Ansible Tower for running your automation tasks.

Before you begin

  • Before you can install the Cloud Pak, you must purchase a license through IBM Passport Advantage. For part numbers, see Passport Advantage part numbers.

  • You must have a supported version of Red Hat OpenShift on IBM Cloud Container Platform installed by using IBM Cloud Kubernetes Service so that the managed Red Hat OpenShift on IBM Cloud service is supported. For the list of supported versions, see Supported Red Hat OpenShift on IBM Cloud versions and platforms.

  • You must have a pre-configured StorageClass in Red Hat OpenShift on IBM Cloud that can be used for installing the IBM Cloud Pak for Multicloud Management.

  • You must have the required user and resource group permissions to install the IBM Cloud Pak for Multicloud Management:

    • You must have permission as an admin user on the cluster where you are installing the IBM Cloud Pak for Multicloud Management.
    • You must have at least viewer access permission to the resource group that includes the cluster where you are installing the IBM Cloud Pak for Multicloud Management. Ensure that this resource group exists in IBM Cloud and that the user ID that is used in IBM Cloud Provider cloud connection has access to this resource group.

Minimum hardware requirements

Nodes Memory CPU
3 32 GB 16 cores

Notes: If you are going to install the Monitoring Module and Terraform & Service Automation Module with the IBM Cloud Pak for Multicloud Management, you need another two nodes.

Minimum storage requirements

Mandatory: 2 PV

Component PV
MongoDB 1
IBM Multicloud Manager etcd 1

Optional: 4 PV

Component PV
Logging 1
VA 3

Step 1. Configure your installation environment

From the Create tab on the Cloud Pak for Multicloud Management installation page, specify where you want to install the IBM Cloud Pak for Multicloud Management:

1. Select the Red Hat Red Hat OpenShift on IBM Cloud cluster where you want to deploy the IBM Cloud Pak for Multicloud Management.
2. Enter or select the project where you want to deploy IBM Cloud Pak for Multicloud Management.

Step 2. Configure your workspace

Specify how to track and manage your installation from your IBM Cloud Schematics workspace:

1. In the _Configure your workspace_ section, update the name and tag of the installation workspace.
2. Specify any tags that you want to use for the installation. Specify multiple tags as a comma-separated list.

Step 3. Complete the pre-installation check

A Red Hat Red Hat OpenShift on IBM Cloud cluster administrator must complete this step.

  • If you are not an administrator, use the Share link to share the script with your cluster administrator.

  • If you are a cluster administrator, click Run script to run the pre-installation check. Confirm that the script completes successfully.

  • For any certificate signing requests (CSRs) that are generated on your cluster nodes, approve all of the CSRs on your nodes before you install. Run the following commands on each of your cluster nodes to approve your CSRs:

    1. Find all CSRs for your cluster nodes:

      oc get csr
      
    2. Approve the CSRs for the cluster nodes:

      oc adm certificate approve <CSR name>
      

    For more information, see the Approving the CSRs for your machines topic in the OpenShift documentation.

Step 4. Set the deployment values

Override the default values by configuring the required deployment values for the Red Hat OpenShift on IBM Cloud cluster that you have installed:

Table 1. Deployment values
Parameter Description Default
defaultAdminUser Configure default admin user name. admin
defaultAdminPassword Configure default admin user password. Password must be at least 32 characters by default, and can include only number, letter, and hyphens.

Note: The password that you set during installation might be available as plain text in some pods and logs. You must change the default_admin_password after you successfully install IBM Cloud Pak for Multicloud Management. For more information about changing the password after IBM Cloud Pak for Multicloud Management installation, see Changing the cluster administrator password.

storageClass Configure storage class. ibmc-block-bronze

Step 5. Install the IBM Cloud Pak for Multicloud Management

  1. Ensure that you have assigned a license for the IBM Cloud Pak for Multicloud Management to the deployment.
  2. Confirm that you have read and agree to the license agreements.
  3. Click Install.

Post-installation

To interact with the IBM Cloud Pak for Multicloud Management by using the management console from your local machine, perform the following steps:

  1. Run kubectl cluster-info to get the Kubernetes API server address and port. Example output:

    kubectl cluster-info
    Kubernetes master is running at https://honest-gryphon-master.purple-chesterfield.com:7443
    

    Note: From the kubectl cluster-info output, make a note of the host and port for the Kubernetes master. In the example, the host is honest-gryphon-master.purple-chesterfield.com and the port is 7443.

  2. Run kubectl edit cm ibmcloud-cluster-info -n kube-public. Example output:

    apiVersion: v1
    data:
      cluster_address: icp-console.chee-ocp-fae6c235d7a3aed6346697c0e75f4896-0001.us-east.containers.appdomain.cloud
      cluster_ca_domain: icp-console.chee-ocp-fae6c235d7a3aed6346697c0e75f4896-0001.us-east.containers.appdomain.cloud
      cluster_endpoint: https://icp-management-ingress.kube-system.svc:443
      cluster_kube_apiserver_host: honest-gryphon-master.purple-chesterfield.com
      cluster_kube_apiserver_port: "7443"
      cluster_name: mycluster
      cluster_router_http_port: "8080"
      cluster_router_https_port: "443"
      edition: Enterprise Edition
      openshift_router_base_domain: chee-ocp-fae6c235d7a3aed6346697c0e75f4896-0001.us-east.containers.appdomain.cloud
      proxy_address: icp-proxy.chee-ocp-fae6c235d7a3aed6346697c0e75f4896-0001.us-east.containers.appdomain.cloud
      proxy_ingress_http_port: "80"
      proxy_ingress_https_port: "443"
      version: 1.2.0
    
  3. Verify the cluster_kube_apiserver_host and cluster_kube_apiserver_port are correctly set with the host and port values from step one for the Kubernetes master and then save the file.

Next steps

When the installation completes, you can access your IBM Cloud Pak for Multicloud Management deployment with the provided URL.

1. Log in the IBM Cloud Pak for Multicloud Management management console by using the admin user name and password that you configured during the installation.
2. Optional: Install any optional modules for the IBM Cloud Pak for Multicloud Management. For instructions, see [Installing, configuring, and upgrading the modules](https://www.ibm.com/support/knowledgecenter/en/SSFC4F_1.3.0/install/install_modules.html).

Uninstalling the IBM Cloud Pak for Multicloud Management

To uninstall IBM Cloud Pak for Multicloud Management, you can use the IBM Cloud Pak for Multicloud Management console or the command-line interface (CLI).

Uninstalling the IBM Cloud Pak for Multicloud Management from the console

  1. Enter the workspace of your installed IBM Cloud Pak for Multicloud Management.

  2. Click the Actions button in the upper right corner. Then, click the delete button to trigger a delete.

  3. Choose Delete workspace and Delete all associated resources and input the name of the workspace to confirm. Click the delete to delete the workspace.

  4. Waiting for the uninstall finish.

  5. Verify that the Cloud Pak is uninstalled:

    Access the {{site.data.keyword.open_s}} web console and verify that the components that are related to the IBM Cloud Pak for Multicloud Management, such as any related pods, are no longer installed.

Uninstalling the IBM Cloud Pak for Multicloud Management on with command-line

If the delete operation failed from the console or you want to use command-line, you can use the oc command-line interface to complete the steps to uninstall. When you use the command-line, you need to remove the resources on your Red Hat OpenShift on IBM Cloud Container Platform cluster that are associated with the IBM Cloud Pak for Multicloud Management.

If you do not have the Red Hat OpenShift on IBM Cloud CLI installed, download and install the CLI from the Red Hat Customer Portal.

When you are running the commands to remove the associated resources, use the project that you selected during the installation of your OpenShift Container Platform cluster. Replace the <project_name> parameter in the following commands with your project name.

  1. Delete the resources for the custom resource definition (CRD):

    oc -n <project_name> delete IBMServicesPlatform default
    
  2. Delete the deployment:

    oc -n <project_name> delete deployment ibmservices-operator
    
  3. Delete the custom resource definition:

    oc -n <project_name> delete CustomResourceDefinition IbmServicesPlatforms.operator.ibm.com
    
  4. Delete the ClusterRoleBinding:

    oc -n <project_name> delete clusterrolebinding ibmservices-operator
    
  5. Delete the pull secret:

    oc -n <project_name> delete secret ibmplatform-image-pull-secret
    
  6. Delete the admin-credential:

    oc -n <project_name> delete secret admin-credential
    
  7. Delete configmap cloudpak-foundation:

    oc -n kube-system delete configmap cloudpak-foundation
    
  8. Verify that the Cloud Pack is uninstalled.

    Access the Red Hat OpenShift on IBM Cloud web console and verify that the components that are related to the IBM Cloud Pak for Multicloud Management, such as any related pods, are no longer installed.