| Table of Contents |
|---|
...
This page discusses the process to install SDNR/SDNC into the ONAP installation at OWL (ONAP Wireless Laboratory) in WINLAB at Rutgers University. The ONAP installation itself is described in the wiki page ONAP Open Wireless Laboratory (OWL) at Wireless Information Network Laboratory (WINLAB). This page describes how to install a development Docker image of SDNC into ONAP rather than the default image taken from the nexus3.onap.org:10001 repository.
...
To install the development image rather than the nexus3 image, open a terminal session with the VM containing the Rancher controller (sb4-rancher). There are instructions on how to create a ssh tunnel to sb4-rancher at this wiki page. Once logged in, we must update parameters in the values.yaml file in the Helm chart for SDNC in the OOM repository, shown here.
...
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
...
| aaf | false |
| aai | true |
| appc | false |
| clamp | false |
| cli | false |
| consul | false |
| contrib | false |
| dcaegen2 | false |
| dmaap | true |
| esr | false |
| log | true |
| sniro-emulator | true |
| oof | true |
| msb | false |
| multicloud | false |
| nbi | false |
| policy | true |
| pomba | false |
| portal | true |
| robot | true |
| sdc | false |
| sdnc | true |
| so | true |
| uui | false |
| vfc | false |
| vid | false |
| vnfsdk | false |
...
The first command deletes SDNC but, despite the "--purge" option, some residual resources remain. The subsequent commands discovers discover and delete those resources and generates commands that can be copied and pasted into your terminal session to be executed. If you know how to pipe a string into bash so it can be executed directly, kindly update this wiki page. The "helm del..." command takes some time, so please be patient. Once SDNC has been deleted, you can install the new version using the commands in the previous section.
...
SDNC is presenting a service at a NodePort that is accessible from outside the ONAP installation. PORT 8282:30202 means that port 30202 is accessible externally and maps to internal port 8282 (I'm not sure why 8282 rather than 8181; a port mapping from 8282 to 8181 may be set in a Dockerfile). Therefore, SDNC is listening at sb4-k8s-4:30202, or 10.31.1.79:30202. By creating a ssh tunnel to sb4-k8s-4 (described here), one can open a browser to localhost:30202/apidoc/explorer/index.html and see this.
...