...
| Agenda Item | Requested by | Notes / Links | |
|---|---|---|---|
START RECORDING Meeting Chair: Liam Fallon | |||
| Review of minutes from last meeting and matters arising | Liam Fallon | ||
| Policy update, Status for M2 | |||
Spring boot changes and backwards compatibility. There have been some comments in the reviews and feedback of potential inconsistencies in the clamp database (controlloop) regarding the tables being in lower case. The question is with all the churn if we are making sure DBs will remain backwards compatible to go from Istanbul to Jakarta. | |||
| Short Update: TCA Implementation using TOSCA approach | Gervais-Martial Ngueko | Work is progressing with support from Ramesh Murugan Iyer | |
| Short Update: Document Store for TOSCA entities: Proposal for PoC | All | Carried over | |
| Automation Composition Management | |||
| Support for native Kafka as an option for message passing to comply with Strimzi requirements | Sirisha Manchikanti | ||
Actions
- Create a Wiki page defining the scope of a PoC on the approach for moving to a document store approach. Liam Fallon
- Policy types/Policies/Node Types/Node Templates are first order items
- Data Types have a scope of a first order item, so a data type definition only applies in the scope of a policy type or node type definition
- We should keep our current APIs, all changes should be internal
- We must provide an upgrade pat to the new data structure and a rollback to the current structure
- The JIRAs on HA and on Database backup/restore will be reorganised Liam Fallon
- Create a story and subtasks for the rename of the CLAMP TOSCA Control Loop function to CLAMP Automation Composition Management (ACM) Liam Fallon
- See
Jira Legacy server System Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key POLICY-3938
- See
- Investigate developing a direct Kafka client implementation rather than an implementation that uses Springboot Kafka support as part of the Kafka investigation/PoC. Sirisha Manchikanti
Notes
- The issue of churn in the DB/persistence layer was raised and discussed
- For API/PAP there is no change in the DB structure so there should be no upgrade/rollback issues.
- For CLAMP, the table structure is unchanged, and table names are set to be case insensitive
- DB Migrator is to be modified for all DB changes as they arise
- The proposal to change the name of the TOSCA Control Loop function to "Automation Composition Management was accepted. See Automation Composition Management: Architecture and Design.
- The presentation on Kafka from Sirisha Manchikanti was well received, see Investigation of using Kafka for messaging for Springboot applications for the material presented. The PoC is proceeding well. In order to avoid sucking in a lot of Spring dependencies, the team felt it would be better to develop code in policy-common Endpoints that implements a Kafka client directly rather than using Springboot Kafka libraries and support. If Kafka endpoints are developed using Springboot support, it will force components to convert to Springboot if they want to use Kafka support.
Attendees
