...
- Release Managment tasks to be completed
- What tasks and who will do it ?
- Service mesh:
- Need a global requirement for Kohn (https://jira.onap.org/projects/REQ) → discussed with David (old REQ
)Jira server ONAP Jira serverId 425b2b0a-557c-3c0c-b515-579789cceedb key REQ-368 - Existing epic JIRAs:
- Need a global requirement for Kohn (https://jira.onap.org/projects/REQ) → discussed with David (old REQ
- Istio Setup Update Andreas Geissler
- Show current findings and solutions
- MariaDB-Galera patch
- Open patches:
- https://gerrit.onap.org/r/c/oom/+/128335 [STRIMZI] Make Strimzi ServiceMesh compatible
- 128989 [AAF] Make AAF ServiceMesh compatible
- required as workarround for DMaaP issue
- https://gerrit.onap.org/r/c/oom/+/128715 [DMAAP] DMaaP ServiceMesh compatibility
- Issues with Message-router (dependency to AAF when configuring the SASL connection to Kafka)
- Workarround (deploy AAF with special options and enable AAF for DMaaP)
- https://gerrit.onap.org/r/c/oom/+/128994 [SO] Service mesh compatibility
- includes now https://gerrit.onap.org/r/c/oom/+/124231 → can be "abbandond"
- not yet tested:
- https://gerrit.onap.org/r/c/oom/+/128992 [CDS] Service mesh compatibility
- https://gerrit.onap.org/r/c/oom/+/128543 [POLICY] Service Mesh Compliance for Policy
- needed CR:
- [NBI] Service mesh compatibility
- Fiachra Corcoran is proposing that components move to Kafka native
- Kafka native clients would not use service mesh for Kafka, but other traffic would go through the sidecar, using the mesh
...