OOM Meeting Notes - 2019-03-13

Agenda



Reviews must have healthcheck and a get pods output to get reviews - ideally with testing results on the review or Jira

# deploy robot pod in addition to your pod tree ubuntu@a-ons0-master:~/oom/kubernetes/robot$ sudo ./ete-k8s.sh onap health ...your pods only need to pass Basic DMAAP Message Router Health Check | PASS | ubuntu@a-ons0-master:~$ kubectl get pods --all-namespaces NAMESPACE NAME READY STATUS RESTARTS AGE kube-system heapster-7b48b696fc-cs22c 1/1 Running 0 1d kube-system kube-dns-6655f78c68-dfjsf 3/3 Running 0 1d kube-system kubernetes-dashboard-6f54f7c4b-2rzlx 1/1 Running 0 1d kube-system monitoring-grafana-7877679464-cxbns 1/1 Running 0 1d kube-system monitoring-influxdb-64664c6cf5-trggz 1/1 Running 0 1d kube-system tiller-deploy-78db58d887-v8nbd 1/1 Running 0 1d # your components pods - and any dependencies - like dmaap,aaf - we will account for known issues unrelated to your merge onap onap-aai-aai-babel-86bd78c6b4-dgdrn 2/2 Running 0 21h onap onap-aai-aai-bf7cdb594-6vcjq 0/1 Init:0/1 96 17h onap onap-aai-aai-cassandra-0 1/1 Running 2 21h



Reviews should verify nodeport collision - either deploy all of onap - or verify OOM NodePort List

Reviews need to have all committers to get reviewed faster (@Alexis de Talhouët , @Borislav Glozman , @James MacNider, @Mike Elliott ) and contributors like myself (@Michael O'Brien), @Prudence Au and integration team members affected @Gary Wu @Brian Freeman @Yang Xu