Upgrading cloud native Netcool Operations Insight components offline with a portable compute device

Learn about upgrading an existing hybrid deployment from version 1.6.4 to 1.6.5, on an offline Red Hat® OpenShift® cluster, by using a portable compute device.

Upgrade on-premises Operations Management

1. Use IBM Installation Manager to upgrade on-premises Operations Management to version 1.6.5. For more information, see Upgrading and rolling back on premises.

Prepare a host

2. Complete the steps for preparing your host, see Prepare a host.

Download the CASE bundle

3. Complete the steps for downloading the CASE bundle, see Download the case bundle.

Setting up the portable docker registry

4. Complete the steps for setting up the portable docker registry, see Setting up the portable docker registry.

Mirroring images to the portable docker registry

5. Complete the steps for mirroring images to the portable docker registry, see Mirroring images to the portable docker registry.

Copying the offline data to the portable compute device

6. Complete the steps for copying the offline data to the portable compute device, see Copying the offline data to the portable compute device.

Setting up the local docker registry

7. Complete the steps for setting up the local docker registry, see Setting up the local docker registry.

Configuring Red Hat OpenShift cluster for airgap

8. Complete the steps for configuring Red Hat OpenShift cluster for airgap, see Configure Red Hat OpenShift cluster for airgap..

Upgrade the Netcool Operations Insight Catalog

9. Install the catalog by using CASE:
   Set the project (namespace) to install the catalog:

   export CATALOG_NAMESPACE=openshift-marketplace

   Create the catalog source:

   cloudctl case launch \
     --case $CASE_LOCAL_PATH \
     --inventory noiOperatorSetup \
     --action install-catalog \
     --namespace $CATALOG_NAMESPACE \
     --args "--registry $LOCAL_DOCKER_REGISTRY/cpopen"

   Note: Verify that the image in the catalog source does not reference the $LOCAL_DOCKER_REGISTRY/noi-operator-catalog:latest image. If the image references noi-operator-catalog:latest, set export CLOUDCTL_CASE_USE_CATALOG_DIGEST=1 and re-run the cloudctl case command to re-create the catalog source.

Upgrade the Netcool Operations Insight Operator

10. Upgrade the Netcool Operations Insight Operator.
    Run the following command:

    cloudctl case launch \
    --case $CASE_LOCAL_PATH \
    --namespace $TARGET_NAMESPACE \
    --inventory noiOperatorSetup \
    --action install-operator \
    --args "--registry $LOCAL_DOCKER_REGISTRY"

    Where namespace is the custom namespace to be used for your deployment.
11. Verify the status of IBM Cloud Pak for Watson™ AIOps Event Manager.
    From the Red Hat OpenShift OLM UI, navigate to Operators > Installed Operators, and verify that the status of IBM Cloud Pak for Watson AIOps Event Manager is Succeeded.

Upgrade the NOI instance

12. Note: If you already set up access to the target registry, skip this step.
    If your offline registry is secure, create a secret for access to the target registry
    Run the following command on your Red Hat OpenShift cluster.

    oc create secret docker-registry target-registry-secret  \
        --docker-server=$LOCAL_DOCKER_REGISTRY \
        --docker-username=$LOCAL_DOCKER_REGISTRY_USER \
        --docker-password=$LOCAL_DOCKER_REGISTRY_PASSWORD \                      
        --namespace=$TARGET_NAMESPACE

    Where:

    • $LOCAL_DOCKER_REGISTRY is the target registry that you created.
    • target-registry-secret is the name of the secret that you are creating. Suggested value is target-registry-secret.
    • $LOCAL_DOCKER_REGISTRY_USER and $LOCAL_DOCKER_REGISTRY_PASSWORD are the credentials to access your target registry.
    • $TARGET_NAMESPACE is the namespace that you want to deploy Netcool Operations Insight in.
13. From the Red Hat OpenShift OLM UI, upgrade the Netcool Operations Insight instance. Go to Operators > Installed Operators and select your Project. Then select IBM Cloud Pak for Watson AIOps Event Manager.
14. Go to the All instances tab and select your instance. Edit the Netcool Operations Insight instance YAML.
    Upgrading to 1.6.5.1: Update spec.version: 1.6.5 to spec.version: 1.6.5.1.
    Upgrading to 1.6.5: Update spec.version: 1.6.4 to spec.version: 1.6.5.
15. Edit the Netcool Operations Insight properties to provide access to the target registry.
    1. Update spec.advanced.imagePullRepository so that it points to the target registry that you created.
    2. Set spec.entitlementSecret to the target registry secret.
16. Select the Save button.
17. The logstash pod is replaced with the common-datarouting pod in version 1.6.5. Delete the logstash and spark deployments by running the following commands:

    oc delete deployment <release-name>-logstash
    oc delete deployment <release-name>-spark-master
    oc delete deployment <release-name>-spark-slave

18. After you restart the noi-operator, confirm that the logstash and spark deployments are not recreated.

Upgrade the Netcool Hybrid Deployment Option Integration Kit

19. Use Installation Manager to upgrade the Netcool Hybrid Deployment Option Integration Kit.
    1. Start Installation Manager in GUI mode with the following commands:

       cd IM_dir/eclipse
       ./IBMIM

       where IM_dir is the Installation Manager Group installation directory, for example /home/netcool/IBM/InstallationManager/eclipse.
    2. From the main Installation Manager screen, select Update, and from the Update Packages window select Netcool Hybrid Deployment Option Integration Kit.
    3. Proceed through the windows, accept the license and the defaults, and enter the on-premises WebSphere® Application Server password.
    4. On the window OAuth 2.0 Configuration, set Redirect URL to the URL of your cloud native Netcool Operations Insight components deployment. This URL is https://netcool-release_name.apps.fqdn/users/api/authprovider/v1/was/return
       Where
       • release_name is the name of your deployment, as specified by the value used for name (OLM UI Form view), or name in the metadata section of the noi.ibm.com_noihybrids_cr.yaml or noi.ibm.com_nois_cr.yaml files (YAML view).
       • fqdn is the cluster FQDN.
    5. On the window OAuth 2.0 Configuration, set Client ID and Client Secret to the values that were set for them in secret release_name-was-oauth-cnea-secrets when you installed the cloud native Netcool Operations Insight components. Retrieve these values by running the following commands on your cloud native Netcool Operations Insight components deployment.

       oc get secret release_name-was-oauth-cnea-secrets -o json -n namespace| grep client-secret | cut -d : -f2 | cut -d '"' -f2 | base64 -d;echo
       oc get secret release_name-was-oauth-cnea-secrets -o json -n namespace | grep client-id | cut -d : -f2 | cut -d '"' -f2 | base64 -d;echo

       Where
       • release_name is the name of your deployment, as specified by the value used for name (OLM UI Form view), or name in the metadata section of the noi.ibm.com_noihybrids_cr.yaml or noi.ibm.com_nois_cr.yaml files (YAML view).
       • namespace is the name of the namespace in which the cloud native Netcool Operations Insight components are installed.
    6. Select Next and Update.
20. Restart Dashboard Application Services Hub on your Dashboard Application Services Hub on-premises installation by using the following commands.

    cd JazzSM_WAS_Profile/bin
    ./stopServer.sh server1 -username smadmin -password password
    ./startServer.sh server1

    where JazzSM_WAS_Profile is the location of the application server profile that is used for Jazz® for Service Management. This is usually /opt/IBM/JazzSM/profile.