Page History

...

helm deploy dev-so local/onap -f /root/oom/kubernetes/onap/resources/environments/public-cloud.yaml -f /root/integration-override.yaml --namespace onap  --verbose

If you are using the SNAPSHOT image override file:

helm deploy dev-sdnc local/onap -f /root/oom/kubernetes/onap/resources/environments/public-cloud.yaml -f /root/integration-override.yaml -f /root/integration/deployment/heat/onap-rke/staging-image-override.yaml --namespace onap --verbose

1. After editing a chart 
   1. cd /root/oom/kubernetes
   2. make project
      
      1. note that for cds/sdnc you need to do make cds; make sdnc
   3. make onap
2. helm del project --purge
   1. helm list -a to confirm its gone
   2. also check pvc's for applications like sdnc/appc and kubectl -n onap delete pvc any remaining ones
      1. kubectl -n onap get pv  | grep project
      2. kubectl -n onap get pvc | grep  project
      3. ...
      4. "delete /dockerdata-nfs/dev-project"
   3. Cleanup shared cassandra (aai, sdc) and shared maiadb (sdnc, so)
   4. /root/integration/deployment/heat/onap-rke/cleanup.sh  project(without dev-)
      1. example: ./cleanup.sh sdc
      2. this script cleans up the shared cassandra and mariadb as well as pvc, pv, jobs etc.
      3. if you get an error when doing aai or sdc check to make sure cassandra cleaned up correctly. We have known problem where the cluster does not let schema's to be replicated and you get a Timeout back to cleanup.sh
3. Rebuild helm charts as necessary
   1. cd /root/oom/kubernetes
   2. make project
   3. make onap
4. helm deploy dev local/onap -f /root/oom/kubernetes/onap/resources/environments/public-cloud.yaml -f /root/integration-override.yaml --namespace onap  --verbose
5. list pods and ports (with k8 host)
   1. kubectl -n onap get pods -o=wide 
   2. kubectl -n onap get services
6. Find out why pod is stuck in initializing or crash loopback
   1. kubectl -n onap describe pod dev-blah-blah-blah
   2. kubectl -n onap logs dev-blah-blah-blah
      
      

...