4 Upgrading OCNADD

This section provides information on how to upgrade an existing OCNADD deployment.

Note:

The OCNADD can be upgraded from a source release to a target release using CLI procedures as outlined in the following sections. These steps can also be followed for any hotfix upgrade.

4.1 Preupgrade Tasks

Before starting the procedure to upgrade OCNADD, perform the following tasks:

Note:

  • While performing an upgrade, you must align the ocnadd-custom-values.yaml file of the target release as per the ocnadd/values.yaml file of the source release or the older release.
  • Do not enable any new feature during the upgrade.
  • The parent or sub-charts values.yaml parameter must not be changed while performing the upgrade, unless it is explicitly specified in this document.

For information about enabling any new feature through Helm parameters, see Oracle Communications Network Analytics Data Director User Guide.

  1. Fetch the images and charts of the target release as described in Installing OCNADD.
  2. Keep a backup of the current ocnadd/values.yaml file of the source release as a backup while upgrading to target release.
  3. Update the following helm chart files of the target release with the parameter values of the source release files:
    • ocnadd-custom-values.yaml
    • ocnadd/ocdd-db-resource.sql
    • ocnadd/templates/ocnadd-secret-hook.yaml
    • Update the pvcClaimSize parameter of all the Kafka brokers ocnadd-custom-values.yaml.

4.2 OCNADD Upgrade

This section includes information about upgrading an existing OCNADD deployment.

When you attempt to upgrade an existing OCNADD deployment, the running set of containers and pods are replaced with the new set of containers and pods. However, If there is no change in the pod configuration, the running set of containers and pods are not replaced.

Important:

  • (Optional) A timeout interval of 15 minutes can be set while performing an upgrade as only one POD of the Data Director services is upgraded at a time.

  • Ensure that no OCNADD pod is in the failed state
  • Ensure that the defined in the Preupgrade Tasks are complete
  • There can be a downtime of Kafka brokers for about a minute while performing an upgrade that affects all of the brokers. You can avoid this downtime by upgrading the brokers one at a time, if applicable. Kafka upgrade along with PVC storage changes are not supported.
  • The Consumer Adapter pods/services are created when Data feed is created from OCNADD GUI. By default, the upgrade of these pods is set to false. To upgrade them, follow the procedure described in "Upgrade Consumer Adapter" section in the Oracle Communications Network Analytics Data Director User Guide .
Execute the following command to upgrade an existing OCNADD deployment:
  1. Upgrade the OCNADD microservices:
    • When using the local Helm chart:
       helm upgrade <release_name> <helm_chart> --namespace <namespace-name> --timeout=15m

      where,

      <release_name> is the release name used by the Helm command

      <helm_chart> is the location of the Helm chart extracted from the target ocnadd-<releaseNumber>.tgz file

      <namespace-name> is the OCNADD namespace in which the release is deployed

    • When using the chart from Helm repo:
       helm upgrade <release_name> <helm_repo/helm_chart> --version <chart_version> --namespace <namespace-name> --timeout=15m

      where,

      <helm_repo> is the OCNADD Helm repo.

      <chart_version> is the version of the Helm chart extracted from the ocnadd-<releaseNumber>.tgz file

      <namespace-name> is the OCNADD namespace in which the release is deployed

  2. Check the status of the upgrade:
    helm history <release_name> --namespace <namespace-name>
  3. Verify if the upgrade is successful using the following steps:
    1. All the pods that have been respawned after upgrade, have the latest age ( in secs )
    2. The Adapter pods also gets respawned for any upgrade. The status can also be verified from GUI for respective Data Feeds.

      In case of any failure, follow the steps mentioned in the Oracle Communications Network Analytics Data Director Troubleshooting Guide.

4.2.1 Hotfix Upgrade

For a HotFix patch upgrade, follow the steps mentioned in the OCNADD Upgrade section.