...

The first command deletes SDNC but, despite the "--purge" option, some residual resources remain.  The subsequent commands discovers 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.

Accessing SDNC/SDNR

SDNC/SDNR Browser Interfaces

Now that SDNC/SDNR is deployed, how can you access it?  To access the browser interfaces of SDNC/SDNR, I use this sequence of commands.  First:

...

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.

SDNC/SDNR Terminal Session

There are (at least) two ways to open a terminal session with SDNC/SDNR.  One way is through the command line.  To learn the names of the SDNC/SDNR pods:

% kubectl get pods -n onap | grep demo-sdnc-sdnc
demo-sdnc-sdnc-0                                       2/2       Running                 0          20m
demo-sdnc-sdnc-1                                       2/2       Running                 0          3m
demo-sdnc-sdnc-2                                       2/2       Running                 0          3m
demo-sdnc-sdnc-ansible-server-7ddf4c54dd-7t5l5         1/1       Running                 0          20m
demo-sdnc-sdnc-db-0                                    2/2       Running                 0          20m
demo-sdnc-sdnc-db-1                                    2/2       Running                 0          3m
demo-sdnc-sdnc-dgbuilder-647d9bddb8-t8lsh              1/1       Running                 0          20m
demo-sdnc-sdnc-dmaap-listener-f9c9fd74c-vblr7          0/1       Init:0/1                0          20m
demo-sdnc-sdnc-portal-6fcd6b8445-dkxfq                 1/1       Running                 0          20m
demo-sdnc-sdnc-ueb-listener-849d6498b5-q2jhf           0/1       Init:0/1                0          20m

Then, to open a session with demo-sdnc-sdnc-0, for example, enter:

% kubectl exec -it demo-sdnc-sdnc-0 -n onap -- /bin/bash
Defaulting container name to sdnc.
Use 'kubectl describe pod/demo-sdnc-sdnc-0' to see all of the containers in this pod.
root@demo-sdnc-sdnc-0:/#

Another approach is to use the Kubernetes GUI.  Browse to the GUI, enter "sdnc" in the "Search" window and then scroll down to "Pods."

Image Added

Click on "demo-sdnc-sdnc-0," for example, and then on "EXEC" in the new window with details about that pod.

Image Added

This will open a new window with a terminal session to the SDNC container in that pod.

Image Added

Conclusion

Please feel free to edit this page to make corrections or improvements.  Your assistance will be greatly appreciated.