/
2022-01-19 Policy Weekly Meeting
2022-01-19 Policy Weekly Meeting
- Liam Fallon
Owned by Liam Fallon
| Agenda Item | Requested by | Notes / Links | |
|---|---|---|---|
| START RECORDING | |||
| Review of minutes from last meeting and matters arising | Liam Fallon | ||
| Policy update, Status for M2 | 2022 TSC MEETING MINUTES (No TSC meeting yet in 2022) | ||
| TCA Implementation using TOSCA approach | Gervais-Martial Ngueko | Martial will contact DCAE to find the parameters/config that is needed. He will contact the TOSCA Control Loop developers if required. Martial will give us an update at the next meeting. | |
| Document Store for TOSCA entities: Progress | Ajith and Francesco both presented the results of their investigations. They will chat during the week and we will discuss this item further next week. | ||
| Statistics and Prometheus, way forward | Discussion on Prometheus work and where it leaves the current statistics code/Monitoring GUI. Se the Decisions section below. | ||
| 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
- Move from Wind River to the UNH lab
- Liam Fallon to check that when we move to the UNH lab we will still have two tenants and that we will have administrative access to those tenants for operations such as create TODO
Decisions
- The current Persistence Layer implementation will not be changed in Istanbul. While POCs or prototypes may be built in the Jakarta time frame, a full change to another persistence implementation will not be executed until at least the Kohn release.
- Monitoring in the Policy Framework:
- The medium to long term strategy is to move to use a Prometheus/Grafana approach, as was started in Istanbul and continues in Jakarta
- The existing statistics collection and transport in messages will be kept in place but will not be further developed
- The existing statistics database will be kept at least for the Jakarta release, even if it is not used and is even disabled in some deployments
- The current Monitoring GUI is not used by anyone so it will be removed in Jakarta because it's code coverage is low and it's not worth the effort to improve its code coverage.
Attendees
