Updating the deployment type (IBM Cloud Pak for AIOps on OpenShift)

Learn how to switch between the base deployment and extended deployment types.

Overview

After IBM Cloud Pak® for AIOps is installed, you can change your deployment type from a base deployment to an extended deployment, or from an extended deployment to a base deployment. For more information about the base deployment and extended deployment types, see Incremental adoption.

If you have log or ticket integrations configured that require an extended deployment, you are prevented from changing to a base deployment until these integrations are removed.

Important: If you are changing from a base deployment to an extended deployment, ensure that you meet the additional hardware requirements. For more information, see Hardware requirements.

You can change your deployment type with the Red Hat® OpenShift® Container Platform console or CLI.

Switching deployment type with the Red Hat OpenShift console

From your Red Hat OpenShift console, click Operators > Installed Operators.
From the Project dropdown menu, select the project that IBM Cloud Pak for AIOps is deployed in.
Select the IBM Cloud Pak for AIOps operator, then click the IBM Cloud Pak for AIOps tab.
Click the IBM Cloud Pak for AIOps deployment that is displayed in the Installations section, and then switch to the YAML view.
If the section spec > pakModules > logAnomalyDetection does not exist, then add it. Otherwise, find and edit the logAnomalyDetection section under spec > pakModules.

Set the value of enabled to one of the following options and then click Save:
- false for a base deployment without log anomaly detection and ticket analysis capabilities.
- true for an extended deployment with log anomaly detection and ticket analysis capabilities.
Example pakModules excerpt for a base deployment:
```
pakModules:
 - enabled: true
   name: aiManager
 - enabled: true
   name: aiopsFoundation
 - enabled: true
   name: applicationManager
 - enabled: false
   name: connection
 - enabled: false
   name: logAnomalyDetection
```
Example pakModules excerpt for an extended deployment:
```
pakModules:
 - enabled: true
   name: aiManager
 - enabled: true
   name: aiopsFoundation
 - enabled: true
   name: applicationManager
 - enabled: false
   name: connection
 - enabled: true
   name: logAnomalyDetection
```
Warning: The pakModules aiManager, aiopsFoundation, and applicationManager must be enabled as in the preceding YAML. Do not change these values to false.

Switching deployment type with the Red Hat OpenShift CLI

Ensure that you are logged in to your Red Hat OpenShift cluster with oc login.

Set environment variables.

export AIOPS_NAMESPACE=<project>
export AIOPS_INSTANCE=$(oc get installation -o jsonpath='{.items[0].metadata.name}' -n ${AIOPS_NAMESPACE})

Where <project> is the namespace (project) that your IBM Cloud Pak for AIOps installation is deployed in.

Edit your IBM Cloud Pak for AIOps installation instance by running the following command:
```
oc edit installation ${AIOPS_INSTANCE} -n ${AIOPS_NAMESPACE}
```
If the section spec > pakModules > logAnomalyDetection does not exist, then add it. Otherwise, find and edit the logAnomalyDetection section under spec > pakModules.

Set the value of enabled to one of the following options and then click Save:
- false for a base deployment without log anomaly detection and ticket analysis capabilities.
- true for an extended deployment with log anomaly detection and ticket analysis capabilities.
Example pakModules excerpt for a base deployment:
```
pakModules:
 - enabled: true
   name: aiManager
 - enabled: true
   name: aiopsFoundation
 - enabled: true
   name: applicationManager
 - enabled: false
   name: connection
 - enabled: false
   name: logAnomalyDetection
```
Example pakModules excerpt for an extended deployment:
```
pakModules:
 - enabled: true
   name: aiManager
 - enabled: true
   name: aiopsFoundation
 - enabled: true
   name: applicationManager
 - enabled: false
   name: connection
 - enabled: true
   name: logAnomalyDetection
```
Warning: The pakModules aiManager, aiopsFoundation, and applicationManager must be enabled as in the preceding YAML. Do not change these values to false.