Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device.
Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Common Helm Chart
How best to police helm chart changes performed by owning teams?
more test automation - integration team trying to drive this effort
OOM meeting in new year to co-ordinate helm chart completion for identified projects taking ownership in Frankfurt
.tpl driving towards completion by M2/M3
secrets
ingress
storage class (pv/pvc)
globals: ingress, repository, global.security.aaf.enabled
some level of service mesh enablement
Service Mesh
A&AI (patch by EOW)
DMaaP (patch by EOW)
SDC + Cassandra (starting now)
ONAP Integration Test Environment
http://testresults.opnfv.org/onap-integration/index.html
Integration Project
Review Patch
https://gerrit.onap.org/r/#/c/oom/+/99326/ (last required to enable storage classes)
https://gerrit.onap.org/r/#/c/oom/+/98403/ (Cassandra 3) - waiting on SDC patch to be merged
https://gerrit.onap.org/r/#/c/oom/+/99628/ (secrets)
https://gerrit.onap.org/r/#/c/oom/+/99627/ (secrets)
https://gerrit.onap.org/r/#/c/oom/+/99679/ (secrets - example) - not to be merged
https://gerrit.onap.org/r/#/c/oom/+/99010/ (ingress) - need to review patches for all applications