Page Comparison

Casablanca Notes with new Deploy/Undeploy plugin from OOM Team

...

helm deploy dev local/onap -f /root/integration-override.yaml--namespace onap

For slower cloud environment use this to use longer interval for readiness

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

...

1. After editing a chart 
   1. cd ~/oom/kubeneties
   2. make project
   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
      helm deploy dev local/onap
      1. 1. kubectl -n onap get pv  | grep project
         2. kubectl -n onap get pvc | grep  project
         3. ...
         4. "delete /dockerdata-nfs/dev-project"
   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/integrationintegration-override.yaml   --namespace  onaponap  --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
         
         

   ...

   Remember: Do the enabled=false BEFORE doing the make onap so that the kubectl processing will use the old chart to delete the POD

   # make robot; make onap

   # helm upgrade -i dev local/onap --namespace onap -f integration-override.yaml - this would just redeploy robot becuase its configMap only

   ...