APPC WindRiver Lab

Non-Clustered Environment

CDT: https://10.12.5.43:8080/index.html#/home (you need to add certificate exception on https://10.12.5.43:9090 first)

APIDOC: http://10.12.5.43:8282/apidoc/explorer/index.html

To perform an update on any of the VMs that are not under Kubernetes (based on docker compose), you may execute the following steps:

• Login to the VM in the table above as the Ubuntu user, using the External IP address after connecting to the WindRiver VPN. (which is 10.12.5.43)
• sudo su - root
• cd /opt

• ./dc.sh - remove all dockers resources etc.

• /opt/config/docker_version.txt , /opt/config/ansible_version.txt, /opt/config/dgbuilder_version.txt  - update/check the docker version

• cd /opt/deployment; git pull (make sure the head of appc/deployment Repo is here)
• docker ps -a

• ./appc_vm_init.sh - install dockers using docker compose

• ./health_check.sh - check appc health

• ./bundle_query.sh - check appc bundles

• ./db_query.sh - check database

Note for CDT development in your local environment:

For the CDT GUI development purpose, you can connect to 10.12.5.43 APPC runtime environment. follow the steps below:

1. bring up windriver lab VPN in your local environment
   
2. git clone CDT source code from appc/cdt repo
3. cd src/environments/
4. cp environment.ts environment.ts.org

5. change environment.ts to below:

       getDesigns: 'https://10.12.5.43:9090/cdtService/getDesigns',
       validateTemplate: 'https://10.12.5.43:9090/cdtService/validateTemplate',
       testVnf: 'https://10.12.5.43:9090/cdtService/testVnf',
       checkTestStatus: 'https://10.12.5.43:9090/cdtService/checkTestStatus'

   
   

6. cd ../..

7. npm start run → it will bring CDT up in your local. the URL is http://localhost:8080/index.html#/home

8. to tail APPC runtime karaf log :
   

   1. ssh to 10.12.5.43

   2. sudo -i

   3. docker exec -it appc_controller_container bash

   4. cd /opt/opendaylight/current/data/log

   5. tail -f karaf.log
      
      

Clustered Environment

To see the robot logs: http://10.12.5.171:30209/logs/

To perform an update on any of the VMs that are under Kubernetes, you may execute the following steps:

1. Login to the k8s-master VM as the Ubuntu user using the External IP address in the table above.
2. cd ~oom/kubernetes
3. change value.yaml (etc)
4. cd ~oom/kubernetes
5. override file is on ~oom/kubernetes/onap/value.yaml
6. make all;make onap
7. "helm deploy dev ./onap --namespace onap" or if you only changed APPC chart, then "helm deploy dev-appc ./onap --namespace onap"
8. kubectl get pods --all-namespaces -o wide -w => using this to check deployment status

To undeploy dev-appc release:

• helm undeploy dev-appc –purge
• kubectl get pods --all-namespaces -o wide -w => using this to check undeployment status
  
• helm del dev-appc --purge
• cd /home/ubuntu
• ./cleanup_appc.sh → that del pvc and pv
• sudo -i
• rm -rf /dockerdata-nfs/dev*
• exit

k8s-master APIDOC/CDT Access:

CDT: 

dev-appc-appc-cdt-xxx - k8s-appc1  http://10.12.5.174:30289/index.html#/home

APIDOC: 

dev-appc-appc-0 - k8s-appc5  http://10.12.6.100:30230/apidoc/explorer/index.html

dev-appc-appc-1 - k8s-appc2  http://10.12.5.193:30230/apidoc/explorer/index.html

dev-appc-appc-2 - k8s-appc4  http://10.12.6.73:30230/apidoc/explorer/index.html

k8s-master-dublin APIDOC/CDT Access:

CDT:

k8s-appc1-dublin https://10.12.6.113:30289/index.html#/home (you need to add certificate exception on https://10.12.6.113:30211/ first)

APIDOC:

dev-appc-appc-0 k8s-appc1-dublin http://10.12.6.113:30230/apidoc/explorer/index.html

dev-appc-appc-1 k8s-appc5-dublin http://10.12.5.3:30230/apidoc/explorer/index.html

dev-appc-appc-2 k8s-appc3-dublin http://10.12.6.117:30230/apidoc/explorer/index.html

Robot:

k8s-appc5-dublin http://10.12.5.3:30209/