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

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

Before you begin

  • Ensure that you complete all the steps in Preparing your cluster. Most of these steps were completed as part of your previous Netcool Operations Insight deployment.
  • Ensure that you have an adequately sized cluster. For more information, see Sizing for a Netcool Operations Insight on Red Hat OpenShift deployment.
  • Configure persistent storage for your deployment. Only version 1.6.5 deployments with persistence enabled are supported for upgrade to version 1.6.6.
  • Before you upgrade to version 1.6.6, if present, remove the noi-root-ca secret by running the following command:
    oc delete secret noi-root-ca
  • Before you upgrade to version 1.6.6, if present, reverse any image overrides from the test fix of the previous release.
    1. Edit the custom resource (CR).
      oc edit noi <release-name>
      Where <release-name> is the release name, for example, evtmanager.
    2. Manually remove the tag, name, and digest entries of image overrides from the helmValuesNOI section of the YAML file.

All the required images for version 1.6.6 are either in the freely accessible operator repository (icr.io/cpopen), or in the IBM® Entitled Registry (cp.icr.io) for which you will require an entitlement key.

Procedure

Upgrade on-premises Operations Management

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

Prepare a host

  1. Complete the steps in 1. Set up your mirroring environment.

Download the CASE bundle

  1. Complete the steps in 2. Set environment variables and download CASE files.

Mirroring images

  1. Complete the steps in 3. Mirror images.

Upgrade the Netcool Operations Insight Catalog

  1. Install the catalog by using CASE, see 4.1 Create the catalog source.

Upgrade the Netcool Operations Insight Operator

  1. Upgrade the Netcool Operations Insight Operator.
    Run the following command:
    oc ibm-pak launch \
    $CASE_NAME \
    --version $CASE_VERSION \
    --namespace $NAMESPACE \
    --inventory $CASE_INVENTORY_SETUP \
    --args "--registry $TARGET_REGISTRY" \
    --action install-operator
    Where namespace is the custom namespace to be used for your deployment.
  2. 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

  1. 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=$TARGET_REGISTRY \
        --docker-username=$TARGET_REGISTRY_USER \
        --docker-password=$TARGET_REGISTRY_PASSWORD \
        --namespace=$TARGET_NAMESPACE
  2. 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.
  3. Go to the All instances tab and select your instance. Edit the Netcool Operations Insight instance YAML.
    Update spec.version: 1.6.5 to spec.version: 1.6.6.
  4. 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.
  5. Select the Save button.
  6. Delete the CEM deployment by running the following command:
    oc delete deployment <release-name>-ibm-cem-akora-app-cem
    Where <release-name> is the release name of the cluster.
    Note: If you are upgrading from version 1.6.4, you must also delete the Logstash and Spark deployments.
    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

Upgrade the Netcool Hybrid Deployment Option Integration Kit

  1. 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.
      Note: When you upgrade the Hybrid Integration Kit, Installation Manager displays that the OAuth configuration is complete. However, you must reenter the Client Secret.
    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.
  2. 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 <smadmin 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 location is usually /opt/IBM/JazzSM/profile.
    • <smadmin password> is the smadmin password.
    To obtain the smadmin password, run the following command:
    oc get secret <release_name>-was-secret -o json -n namespace | grep WAS_PASSWORD | cut -d : -f2 | cut -d '"' -f2 | base64 -d;echo
    Where:
    • <release_name> is the release name for the current cluster.
    • namespace is the namespace that Netcool Operations Insight is deployed into, which can be retrieved by using the oc project command.
    For more information, see Retrieving passwords from secrets.

What to do next

After upgrading, if the GitLab and SevOne observers are not listed in the YAML, run the oc edit noihybrid command and add the following lines:
observers:
  gitlab: true
  sevone: true