Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

...

Working with the ONAP oom and integration repositories in the "ubuntu" home directory in sb4-rancher

The VM sb4-rancher is VM is the Rancher controller for the ONAP installation at OWL, and we keep clones of the ONAP oom and integration repositories in the ubuntu home directory.  Below are commands to execute as user ubuntu in a terminal session with sb4-rancher.  Please edit these commands if something is wrong or missing.

sudo -i -u ubuntuChange to user ubuntu

cd ~/git/oom && git status && git checkout . && git pull

Discard any changes. I assume that we keep all of our changes in override files.git pullPull changes in the oom repository and pull down the latest. I assume that we will keep all of our changes in override files and other locations.
cd ~/git/integration

This repository maintains version numbers of the latest code for the ONAP components. There is information about the repository at https://gerrit.onap.org/r/gitweb?p=integration.git;a=summary.

git pull

Get the latest; currently working in the master branch. There is no Casablanca branch.

cd ~/git/integration/version-manifest/src/main/scripts

Scripts This folder contains scripts that update the OOM repository with the correct version numbers

./update-oom-image-versions.sh \

~/git/integration/version-manifest/src/main/resources/docker-manifest-staging.csv \

~/git/oom

Execute a script to update version numbers in the Helm charts in the oom/kubernetes directory. This will make changes to the values.yaml files, so “git status” in ~/git/oom will return a lot of many changes. I emphasize “staging” because there is also a “release” script. We want to use the staging version numbers.

cd ~/git/oom/kubernetes

Start following instructions at https://wiki.onap.org/display/DW/OOM+Helm+%28un%29Deploy+plugins

sudo cp -r ~/oom/kubernetes/helm/plugins/ ~/.helm

Get the Helm deploy plugin developed by the OOM group

make repo

This updates the Helm repo served by a local Helm process listening on port localhost:8879

make && make onap

I think this updates the local Helm repo with the latest versions in ~/git/oom/kubernetes. These commands take a while.

After these commands, the repositories and Helm resources have been updated to the latest versions, and we can use the commands described in the next section to deploy our code into ONAP.

Preparing to install the SDNC Docker image

...

The simplest way to override the values is to copy the entire values.yaml file into a separate file (I use ~/oof-pci/override-sndc.yaml) and modify the relevant parameters in that new file.  The new values are shown below.  We identify the repository with the source image name and tag, create a cluster of three ODL members, and create a redundant MySQL deployment of two instances.

...

#################################################################
# Application configuration defaults.
#################################################################
# application images
repository: nexus3.onap.org:10001
repositoryOverride: registry.hub.docker.com
pullPolicy: Always
#image: onap/sdnc-image:1.4.1
image: ft3e0tab7p92qsoceonq/oof-pci-sdnr:1.4.2-SNAPSHOT

...

mysql:
  nameOverride: sdnc-db
  service:
    name: sdnc-dbhost
    internalPort: 3306
  nfsprovisionerPrefix: sdnc
  sdnctlPrefix: sdnc
  persistence:
    mountSubPath: sdnc/mysql
    enabled: true
  disableNfsProvisioner: true
  replicaCount: 2
  geoEnabled: false

...

# default number of instances
replicaCount: 3

...

aaffalse
aaitrue
appcfalse
clampfalse
clifalse
consulfalse
contribfalse
dcaegen2false
dmaaptrue
esrfalse
logtrue
sniro-emulatortrue
ooftrue
msbfalse
multicloudfalse
nbifalse
policytrue
pombafalse
portaltrue
robottrue
sdcfalse
sdnctrue
sotrue
uuifalse
vfcfalse
vidfalse
vnfsdkfalse

...