Getting started with IBM Cloud Pak for Multicloud Management V2.1

Operator-based installation

The IBM Cloud Pak for Multicloud Management installation is now operator-based. You can choose either a simple or advanced installation method. When you choose the simple installation, the following default services are installed.

• Console
• Governance, risk, and compliance
• Global search
• Cluster management
• Application management
• IBM Cloud Platform Common Services
• License Advisor

With the advanced installation mode, you can choose to enable or disable these modules and services:

• Infrastructure management operators, which include Policies and Profiles (ibm-management-infra-grc), Provisioning virtual machines and Instances (ibm-management-infra-vm), Managed services (ibm-management-cam-install), and Creating and managing services (ibm-management-service-library).
• Operations operator, which is ChatOps (ibm-management-sre-chatops).
• Monitoring operator, which is Monitoring (ibm-management-monitoring).
• Security services operators, which include Notary service for image signing (ibm-management-notary), Image signing support for image policies (ibm-management-image-security-enforcement), Mutation Advisor (ibm-management-mutation-advisor), and Vulnerability Advisor (ibm-management-vulnerability-advisor).
• Runtime (ibm-management-manage-runtime) operator, which is a technology preview code.

Self-service capabilities

Additional self-service capabilities enable developers to provision infrastructure and application components from a predefined service flow. This means providing a full-service library feature for developers to access on-demand.

SRE tools for hybrid applications

The IBM Cloud Pak for Multicloud Management supports the implementation of an SRE operating model. Some of these tools are:

• Bastion control - A new single point of access terminal supports secure remote access to managed systems. This centralized bastion host simplifies the troubleshooting process across regions and deployment models with increased visualization and remediation tools, such as audit and replay.

• Session replay - Replay sessions for auditing, compliance, and SRE postmortem reviews, which allows SRE teams to have a consistent source of review and feedback for future incident response and resolution.

• ChatOps - A ChatOps interface that connects with your preferred tools, including PagerDuty and Slack. This further accelerates the SRE’s ability to receive and react to incidents immediately using the tools they use every day.

Hybrid Policy Model

The updates to Governance, Risk, and Compliance policies allow for a faster, more flexible solution for both VMs and containers. This hybrid approach to policy applications allows operators to apply a policy that is enforced, even as applications are edited and moved by development teams. These enhancements also include templated policy-as-code for industry standards such as HIPAA, FISMA, NIST, and PCI. This policy-based Governance and Risk dashboard is ready out of the box and is versatile and adaptable for your unique compliance and governance requirements.

Cost and license management

Managing cloud costs is a priority in any organization. IBM Cloud Pak for Multicloud Management cost modeling and asset management now provide a more seamless experience. The capabilities that are included are:

• IT Cost Modeling, Showback, and Chargeback are enhanced with new visibility features to find resources and more detailed report generation.

• Chargeback generation steps are simplified to three key steps: Define rate cards, assign rate cards, and generate the chargeback report.

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 that is 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 permission as an administrator 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 IBM Cloud Pak for Multicloud Management. Ensure that this resource group exists in IBM Cloud and that the user ID that is used in the IBM Cloud Provider cloud connection has access to this resource group.

Supported upgrade paths

IBM Cloud Pak for Multicloud Management supports upgrading within the the main version. It does not support upgrading between main versions. For example, you cannot upgrade from Version 1.x to Version 2.x. The supported IBM Cloud Pak for Multicloud Management upgrade paths within the main version are:

• IBM Cloud Pak for Multicloud Management Version 1.2.0 to Version 1.3.0
• IBM Cloud Pak for Multicloud Management Version 1.3.0 to Version 1.3.1, 1.3.2
• IBM Cloud Pak for Multicloud Management Version 1.3.1 to Version 1.3.2
• IBM Cloud Pak for Multicloud Management Version 2.1.0 to Version 2.1.5

Minimum hardware requirements

Minimum storage requirements

Mandatory: 240GB of persistent storage.

Procedure

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

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.

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 administrator username and password which were generated when the workspace was created.

   • To get the administrator username, run oc get secret platform-auth-idp-credentials -n ibm-common-services -o jsonpath='{.data.admin_username}' | base64 -d; echo ""

   • To get the administrator password, run oc get secret platform-auth-idp-credentials -n ibm-common-services -o jsonpath='{.data.admin_password}' | base64 -d; echo ""

2. For more information about changing the password after IBM Cloud Pak for Multicloud Management is installed, see Changing the cluster administrator password.

3. Optional: After installation, you can choose to enable or disable additional operators and services such Infrastructure Management, Operations, Monitoring, and other services. For instructions, refer to Advanced configuration.

Uninstalling IBM Cloud Pak for Multicloud Management from the IBM Cloud console

1. Access https://cloud.ibm.com/schematics/workspaces to go to the schematic workspaces for your IBM Cloud Pak for Multicloud Management installation on the IBM Cloud console.

2. Select the workspace where IBM Cloud Pak for Multicloud Management is installed, click the button at the end of the row and click Delete.

3. Select the Delete workspace and Delete all associated resources check boxes and enter the name of the workspace in the field. The workspace name is provided for you, just copy or type it in. Click Delete to delete the workspace.

4. Wait for the uninstall to finish.

5. Verify that the Cloud Pak is uninstalled by accessing the Red Hat OpenShift on IBM Cloud web console and verifying that the IBM Cloud Pak for Multicloud Management components such as the pods and resources are no longer available.

Uninstalling IBM Cloud Pak for Multicloud Management using the 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 IBM Cloud Pak for Multicloud Management.

If the Red Hat OpenShift on IBM Cloud CLI is not 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. Download the uninstall.sh script from github. Run:

curl https://raw.githubusercontent.com/IBM/cp4mcm-samples/master/scripts/cp4mcm-cleanup-utility.sh -o uninstall.sh

2. Identify the path to the kubeconfig file for your cluster, for example: `/root/.kube/config`
3. Change the file permissions on the `uninstall.sh` script so you can run it:
  ``` {: codeblock}
chmod 700 uninstall.sh

4. Run the uninstall.sh script as follows:

./uninstall.sh --mode uninstallEverything --kubeconfigPath ~/.kube/config --cloudpakNamespace <project_name>

5. Verify that IBM Cloud Pak for Multicloud Management is uninstalled by accessing the Red Hat OpenShift on IBM Cloud web console and verifying that the IBM Cloud Pak for Multicloud Management components such as the pods and resources are no longer available.

## Troubleshooting

### Take action page is not displaying data.

  To solve this issue, complete the instructions in [Take Action pages show no data](https://www.ibm.com/support/knowledgecenter/SSFC4F_2.1.0/mcm/troubleshoot/troubleshoot_takeactions.html).