Non-Clustered Environment – Decommissioned

VM NameExternal IPappc-multicloud-integration IPMulMoam_onap_LH2Z IPNote
onap-aai-inst110.12.5.11410.10.5.1510.0.1.1mainly followed the setup:

https://wiki.onap.org/display/DW/How+to+Docker+setup+on+Single+VM+HEAT+Deployment

onap-aai-inst210.12.5.20110.10.5.2410.0.0.7
onap-dns-server10.12.5.5910.10.5.1610.0.100.1
onap-appc10.12.5.4310.10.5.1010.0.2.1
Stability-Test-VM310.12.6.13010.10.5.1810.0.0.18

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

  • cd csit; ./run-robot-appc.sh - check csit health check

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 https://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/


VM NameExternal IP
k8s-master10.12.5.171
k8s-appc110.12.7.48
k8s-appc210.12.7.47
k8s-appc310.12.5.194
k8s-appc410.12.6.73
k8s-appc510.12.6.100
k8s-master-elalto10.12.6.68
k8s-appc1-elalto10.12.6.113
k8s-appc2-elalto10.12.6.92
k8s-appc3-elalto10.12.6.117
k8s-appc4-elalto10.12.6.138
k8s-appc5-elalto10.12.6.251


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 /root/oom/kubernetes
  3. change value.yaml (etc)
  4. cd /root/oom/kubernetes
  5. override file is on /root/oom/kubernetes/onap/value.yaml
  6. make all;make onap
  7. "helm deploy dev local/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

NOTE: in order to sync up the version from the manifest file to value.yaml, those commands below should be executed

  1. cd /root/integration
  2. git pull then git reset --hard origin/master (master in this case)
  3. cd /root/oom
  4. git pull then git reset --hard origin/master (master in this case)
  5. cd /root/integration/version-manifest/src/main/scripts/

  6. ./update-oom-image-versions.sh ../resources/docker-manifest-staging.csv /root/oom/

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: (note: use "kubectl get pods --all-namespaces -o wide" to get the VM name where pod is running)

CDT: 

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


APIDOC: 

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

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

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

k8s-master-elalto APIDOC/CDT Access: (note: use "kubectl get pods --all-namespaces -o wide" to get the VM name where pod is running)

CDT:

k8s-appc1-elalto 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-elalto https://10.12.6.113:30230/apidoc/explorer/index.html

dev-appc-appc-1 k8s-appc5-elalto https://10.12.5.3:30230/apidoc/explorer/index.html

dev-appc-appc-2 k8s-appc3-elalto https://10.12.6.117:30230/apidoc/explorer/index.html




  • No labels

1 Comment

  1. If does not work correctly after update check that the /etc/hosts files contain the correct hostname mappings