2022-01-26 Policy Weekly Meeting
Agenda Item | Requested by | Notes / Links | |
---|---|---|---|
START RECORDING | |||
Review of minutes from last meeting and matters arising | Liam Fallon | ||
Policy update, Status for M2 | |||
IBN user-triggered Intent update and CCVPN closed-loop changes in Jakarta | This item is regarding the IBN [1] and CCVPN [2] code impact on Policy in Jakarta release. They have just updated the code impact wiki [3] to indicate this impact, and apologise for doing it so late. The attached PPT is their design document. To provide a complete picture, they describe DCAE changes as well, but page 11 and 12 explains their idea on Policy changes. They are new to Policy, and our proposed design may not be accurate. So, they would like to a review of their design. [1] https://jira.onap.org/browse/REQ-1074 [2] https://jira.onap.org/browse/REQ-1076 [3] https://lf-onap.atlassian.net/wiki/display/DW/Jakarta+Impact+View+per+Component | ||
Metadata Set Handling | Discussion on this work and the commit comments | ||
TCA Implementation using TOSCA approach | Gervais-Martial Ngueko | Update from Martial. | |
Document Store for TOSCA entities: Progress | Continuation of discussion, carried over. | ||
High Availability Discussion | Saul Gill All | Carried over | |
Automation Composition Management | Carried over | ||
Support for native Kafka as an option for message passing to comply with Strimzi requirements | Carried over | ||
AOB | All |
Actions
- IBN/CCVPN to check if their use cases and microservices are affected by the switch from Cloudify to K8S based microservices in DCAE: Henry Yu
- Continue to work on the Metadata Set review, taking comments into account especially those form Jorge Hernandez: Ramesh Murugan Iyer
Decisions
The IBN use case will use policy in the same manner as they have implemented the CC-VPN use case.