OOM Meeting Notes - 2019-10-09
Agenda
Helm Chart Generation status from @Venkata Harish Kajur
Helm Chart Transfers
dependent on Helm Chart generation + schema validation
Policy Team indicated they have resources that can help with this for the Policy Chart transfer
DCAE Team also indicated we can work together to verify that generation and schema validation works for DCAE charts
Ingress Controller status
PoC work provided learns that can be leveraged in Frankfurt
Discussion at F2F around moving to Istio for Ingress in Frankfurt
Intel can provide learnings on successfully deploying Istio as Ingress
Comments
Oct 9, 2019
What are S, M and L deployments and which components should be included?
The question of "what are the core components" may be a topic for Architecture subcommittee meeting
@Fiachra Corcoran - topic being tracked under OOM-1946. Comment has been added to this Jira ticket.
Need to ensure all projects understand that it must be possible to disable AAF integration.
This was a checklist item in past milestones.
The purpose is to ensure that operators can choose to optionally disabled TLS for dev environments and in order to use Service Mesh
@Mike Elliott needs to align with Architecture Subcommittee to ensure enforcement as we move towards SM integration
Concern was raised by @Fiachra Corcoran that DMaaP (and potentially other projects) have integrated with AAF/CADI to provide RBAC and if AAF is not required to be deployed, what would that mean for RBAC?
@Fiachra Corcoran perhaps you can raise your concerns re; RBAC as comments to OOM-1986?
Edge Automation Status to be discussed in up coming Architecture subcommittee meeting
DMaaP to join Edge Automation WG as they are greatly impacted and have huge value in being part of the discussion/solution