Installing Netcool Operations Insight on Red Hat OpenShift with the oc ibm-pak plug-in, Operator Lifecycle Manager (OLM) UI, and Container Application Software for Enterprises (CASE)

Use these instructions to install IBM Netcool Operations Insight®, with the Container Application Software for Enterprises (CASE) and the Red Hat® OpenShift® Operator Lifecycle Manager (OLM) UI. This installation method is similar to installing with the OLM UI, but CASE creates the Netcool® Operations Insight catalog source and installs the Netcool Operations Insight Operator for you.

Before you begin

Ensure that you complete all the steps in Preparing.

Online installations of Netcool Operations Insight on Red Hat OpenShift can be run entirely as a nonroot user and do not require users to have sudo access.

The operator images for Netcool Operations Insight on Red Hat OpenShift are in the freely accessible operator repository (icr.io/cpopen), and the operand images are in the IBM® Entitled Registry (cp.icr.io), for which you require an entitlement key. The CASE bundle is available from IBM cloudPaks.

For more information about the OLM, see https://access.redhat.com/documentation/en-us/openshift_container_platform/4.10/html/operators/understanding-operators#operator-lifecycle-manager-olm external link.

Procedure

Get the Netcool Operations Insight CASE.

  1. Download and install the most recent version of IBM Catalog Management Plug-in for IBM Cloud Paks from the IBM/ibm-pak-plugin external icon. Extract the binary file by entering the following command:
    tar -xf oc-ibm_pak-linux-amd64.tar.gz
  2. Run the following command to move the file to the /usr/local/bin directory:
    mv oc-ibm_pak-linux-amd64 /usr/local/bin/oc-ibm_pak
    Note: If you are installing as a nonroot user, you must use sudo.
  3. Confirm that oc ibm-pak is installed by running the following command:
    oc ibm-pak --help

    Expected result: The plug-in usage is displayed.

  4. Note: If you want to install the previous 1.6.5 version, specify --version 1.5.0 in the oc ibm-pak get command.
    Download the Netcool Operations Insight CASE bundle (ibm-netcool-prod) to your Red Hat OpenShift cluster.
  5. Check that the CASE repository URL is pointing to the default https://github.com/IBM/cloud-pak/raw/master/repo/case/ location by running the oc ibm-pak config command.

    Example output:

    Repository Config
    
    Name                        CASE Repo URL
    ----                        -------------
    IBM Cloud-Pak Github Repo * https://github.com/IBM/cloud-pak/raw/master/repo/case/
    
    If the repository is not pointing to the default location (asterisk indicates default URL), then run the following command:
    oc ibm-pak config repo 'IBM Cloud-Pak Github Repo' --enable
    If the URL is not displayed, then add the repository by running the following command:
    oc ibm-pak config repo 'IBM Cloud-Pak Github Repo' --url https://github.com/IBM/cloud-pak/raw/master/repo/case/
  6. Run the following commands:
    export CASE_NAME=ibm-netcool-prod
    export CASE_VERSION=1.6.0
    Download the Netcool Operations Insight CASE bundle (ibm-netcool-prod) to your Red Hat OpenShift cluster.
    oc ibm-pak get $CASE_NAME --version $CASE_VERSION

Install the Netcool Operations Insight Catalog and Operator.

  1. Generate the catalog source.
    oc ibm-pak generate mirror-manifests ${CASE_NAME} icr.io --version ${CASE_VERSION}
  2. View the catalog source.
    cat ~/.ibm-pak/data/mirror/$CASE_NAME/$CASE_VERSION/catalog-sources-linux-amd64.yaml
  3. Apply the catalog source.
    oc apply -f ~/.ibm-pak/data/mirror/$CASE_NAME/$CASE_VERSION/catalog-sources-linux-amd64.yaml
  4. Install the operator.
    oc ibm-pak launch \
    $CASE_NAME \
    --version $CASE_VERSION \
    --namespace $NAMESPACE \
    --inventory noiOperatorSetup \
    --action install-operator

    Where $NAMESPACE is the custom namespace to be used for your deployment.

  5. Verify the status of IBM Cloud Pak for Watson AIOps Event Manager.
    From the Red Hat OpenShift OLM UI, go to Operators > Installed Operators, and verify that the status of IBM Cloud Pak for Watson AIOps Event Manager is Succeeded.

Create a Netcool Operations Insight instance.

  1. From the Red Hat OpenShift OLM UI, go to Operators > Installed Operators, and select IBM Cloud Pak for Watson AIOps Event Manager. Under Provided APIs > NOI, select Create Instance.
  2. From the Red Hat OpenShift OLM UI, use the YAML view or the Form view to configure the properties for the Netcool Operations Insight deployment. For more information about configurable properties for a cloud only deployment, see Cloud operator properties.
    CAUTION:
    Ensure that the name of the Netcool Operations Insight instance does not exceed 10 characters.
  3. Select Create.
  4. Under the All Instances tab, a Netcool Operations Insight instance appears.
    Navigate to Operators > Installed Operators and check that the status of your Netcool Operations Insight instance is Phase: OK. Click on Netcool Operations Insight > All Instances to check it. This means that IBM Cloud Pak for Watson AIOps Event Manager has started and is now in the process of starting up the various pods.
    To monitor the status of the installation, see Monitoring cloud installation progress.
    Note:
    • Changing an existing deployment from a Trial deployment type to a Production deployment type is not supported.
    • Changing an instance's deployment parameters in the Form view is not supported post deployment.
    • If you update custom secrets in the OLM console, the crypto key is corrupted and the command to encrypt passwords does not work. Update custom secrets only with the CLI. For more information about storing a certificate as a secret, see https://www.ibm.com/docs/en/SS9LQB_1.1.15/LoadingData/t_asm_obs_configuringsecurity.html external link

What to do next

  • To enable or disable a feature or observer after installation edit the Netcool Operations Insight instance by running the command:
    oc edit noi <noi-instance-name>
    Where <noi-instance-name> is the name of the deployment that you want to change.

    You can then select to enable or disable the feature or observer. When you disable features postinstallation , the resource is not automatically deleted. To find out whether the feature is deleted, you must check the asm-operator log.