1. Operations Services Overlay (OSO) Installation Guide
  2. Installing OSO

2 Installing OSO

The installation procedures in this document provision and configure the Oracle Communications Operations Services Overlay (OCOSO). OSO is packaged as a Cloud Service Archive (CSAR) file. The OSO CSAR is a ZIP file that contains the following components:
  • All required OSO images (including open source software) as a tar file.
  • All required OSO Helm charts
  • Custom values.yaml file named "prometheus-custom-values.yaml" under Artifacts -> Scripts in the CSAR.

    Note:

    The name of the prometheus-custom-values.yaml file will change as per the below format in each release:

    "oso-<release-version>-custom-values.yaml"

Installing OSO using CSAR

The CSAR format is intended to be used by an Open Network Automation Platform (ONAP) compliant Orchestrator to onboard, validate, and install OSO. However in the absence of orchestrator, manual installation is possible using the CSAR file contents.

Follow the procedure to install OSO using CSAR artifacts:
  1. Download OSO CSAR zip file from Oracle Software Download Center (OSDC).
  2. Unpack the CSAR zip file:

    Note:

    In case "unzip" is not available on the linux system where the CSAR zip is stored, download and installed the "unzip" using the command: "yum install unzip". 
    unzip csar_oso_1_6_0.zip
  3. Load Artifacts → Images in the repository.
  4. Go to Artifacts → Scripts directory and update the prometheus-custom-values.yaml file with the required values as mentioned in OSO Configuration Parameter.
  5. Go to Artifacts → Scripts directory where the helm charts tgz file is available and untar it.
    cd Artifacts/Scripts
tar -xvzf oso-1.6.0-charts.tgz
  6. Install OSO using helm charts provided and updated prometheus-custom-values.yaml file with below command:
    1. Installation using helm2:
      helm install -f <prometheus-custom-values.yaml> --namespace=<deployment-namespace-name> --name=<deployment-name> ./prometheus
    2. Installation using helm3 if custom labels are given. Skip the flag (--disable-openapi-validation) if custom labels are not provided:
      helm3 install -f <prometheus-custom-values.yaml> --namespace=<deployment-namespace-name> --name=<deployment-name> ./prometheus --disable-openapi-validation
    Example:
    helm install -f prometheus-custom-values.yaml --namespace=ocoso --name=ocoso ./prometheus