...

http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/index.html

TLab specific

...

Upgrade of Portal

Below are the notes specific for the TLab environment. If a change is made in OOM charts then the following needs to be completed to upgrade the running charts in

1. 1. Find Rancher IP in R_Control-Plane tenant - we use “onap_dev” key and “Ubuntu” user to SSH. For example: “ssh -i onap_dev ubuntu@192.168.31xx.245xxx”.
   2. Login as ubuntu, then run "sudo -i" to login as root. The “oom” git repo is in the rancher vm's root directory, under “/root/oom”.
   3. Edit portal files at /root/oom/kubernetes
      

      “make portal”

      “make onap”
      Run below command from "/root” folder to do helm upgrade

      "helm upgrade -i dev local/onap -f ../../integration-override.yaml"/portal....

   4. When complete run the following form /root/oom/kubernetes  dir

      
      

      Code Block
      language bash theme Midnight
      > make portal .... > make onap .... # This will do the upgrade: helm upgrade dev local/onap --namespace onap -f onap/resources/environments/disable-allcharts.yaml --set portal.enabled=true # When complete run the following to ensure its in the process of coming up or complete. kubectl get pods -n onap -o wide | grep portal

   5. Rancher gui is at 192.168.31xx.245xxx:8080
      There is an interactive cli as well in the rancher gui where you can run kubectl commands.

   6. Below command will show the list of portal services.

...

1. 1. Code Block
      language bash theme Midnight
      kubectl get services --namespace=onap | grep

...

1. 1. portal

Accessing the ONAP Portal using OOM and a Kubernetes Cluster

...

Overview of the running system

> kubectl get services --namespace=onap | grep portal
portal-app               LoadBalancer   10.43.141.57    10.0.0.8      8989:30215/TCP,8006:30213/TCP,8010:30214/TCP   5d
portal-cassandra         ClusterIP      10.43.158.145   <none>        9160/TCP,7000/TCP,7001/TCP,7199/TCP,9042/TCP   5d
portal-db                ClusterIP      10.43.192.65    <none>        3306/TCP                                       5d
portal-sdk               ClusterIP      10.43.24.82     <none>        8990/TCP                                       5d
portal-widget            ClusterIP      10.43.101.233   <none>        8082/TCP                                       5d
portal-zookeeper         ClusterIP      10.43.0.82      <none>        2181/TCP                                       5d

> kubectl get pods --all-namespaces | grep portal
onap          dev-portal-app-b8c6668d8-56bjb                2/2       Running       0          2m
onap          dev-portal-app-b8c6668d8-g6whb                2/2       Running       0          2m
onap          dev-portal-app-b8c6668d8-xshwg                2/2       Running       0          2m
onap          dev-portal-cassandra-5ddbc59ffd-qc6rp         1/1       Running       0          2m
onap          dev-portal-db-6d7fc58648-sp9sf                0/1       Running       0          2m
onap          dev-portal-sdk-868f696cd7-mnjxk               0/2       Init:0/1      0          2m
onap          dev-portal-widget-694c45b75f-nqdtt            0/1       Init:0/1      0          2m
onap          dev-portal-zookeeper-db466fc-kggsw            1/1       Running       0          2m

...

portal:
  portal-app:
    replicaCount: 3

Then perform the helm upgrade.Run below command from "/root” folder to do helm upgrade

helm upgrade -i dev local/onap -f integration-override.yaml

portal-app Resiliency

A portal-app container failure can be simulated by stopping the portal-app container.    The kubernetes liveness operation will detect that the ports are down, inferring there's a problem with the service, and in turn, will restart the container. 

...