5 Upgrading OSO

This chapter provides information about upgrading Oracle Communications Cloud Native Core, Operations Services Overlay (OSO) deployment to the latest release. It is recommended to perform OSO upgrade in a specific order. For more information about the upgrade order, see Oracle Communications Cloud Native Core, Solution Upgrade Guide.

Note:

While performing OSO upgrade from 25.1.1xx or 25.1.2xx to 25.2.100, a small service interruption is expected.

5.1 Supported Upgrade Paths

The following table lists the supported upgrade path for OSO:

Table 5-1 Supported Upgrade Path

Source Release Target Release
25.1.2xx 25.2.100
25.1.1xx 25.2.100

5.2 Prerequisites

Following are the prerequisites for upgrading OSO:
  • Ensure that the system has OSO 25.1.2xx or 25.1.1xx installed and the OSO is working properly.
  • Verify if all the pods and services are up and running.
  • Ensure that the NFs are upgraded after the OSO upgrade.

5.3 Upgrading OSO using CSAR

This section describes the procedure to upgrade an existing OSO using CSAR.

  1. Prepare the ocoso_csar_25_2_100_0_0_0_custom_values.yaml file by performing the following steps. This yaml file is used as the input during the upgrade process.
    1. Download OSO CSAR zip file from My Oracle Support (MOS).
    2. Unzip the CSAR zip file:
      $ unzip <OSO CSAR package>
    3. Upload all the artifacts present in the Artifacts/Images folder to the configured repository. For more information on the artifacts, see the Installation Prerequisite section.
    4. Update the Prometheus and Alertmanager ocoso_csar_25_2_100_0_0_0_prom_custom_values.yaml and ocoso_csar_25_2_100_0_0_0_alm_custom_values.yaml files present in the Artifacts/Scripts directory with the required values as mentioned in OSO Configuration Parameters.
    5. Untar the Helm charts tgz file available in the Artifacts/Scripts directory.
      
cd Artifacts/Scripts
$ tar -xvzf <helm charts.tgz file>
  2. Run the following command to upgrade the existing OSO release:
    
$ helm upgrade <OSO release-name for prometheus> <path to the new prom-OSO helm chart> -n <oso-namespace> -f <path to ocoso_csar_25_2_100_0_0_0_prom_custom_values.yaml file>
$ helm upgrade <OSO release-name for alertmanager> <path to the new alm-OSO helm chart> -n <oso-namespace> -f <path to ocoso_csar_25_2_100_0_0_0_alm_custom_values.yaml file>

    Note:

    To install the alert config feature, see Automated Configuration of NF Alerts.
  3. Post the Helm upgrade a new Prometheus pod spuns up, which is in container creating state. To make it into running state, detach the PVC from old pod in K8s and let it attach to this new upgraded pod.

    Note:

    Find Prometheus deployment name and replace it in the following commands, Both the commands given below should be run at the same time. 
    
$ kubectl get deployment -n <oso-namespace>
# Find Prometheus deployment name and replace it in below commands, Both the commands below needs to be run at the same time
$ kubectl -n <oso-namespace> scale deploy <oso-deployment-name> --replicas=0
$ kubectl -n <oso-namespace> scale deploy <oso-deployment-name> --replicas=1
  4. Verify if all the pods are up and running with the latest versions and changes.
  5. Verify if the upgraded OSO is working as expected by performing the Verifying Installation procedure.