2019-10-09 Control Loop Sub Committee
- Pamela Dragosh
Discussion items
Duration | Agenda Item | Requested by | Notes / Links |
|---|---|---|---|
START RECORDING | |||
Community Elections | @Pamela Dragosh | ||
Frankfurt Requirement Status REQ-9: Self Serve Control LoopsDone - @Scott Blandford REQ-21: TOSCA Compliant PoliciesDone - @Gervais-Martial Ngueko REQ-25: Policy Update NotificationsDone - @Pamela Dragosh REQ-29: CLAMP Deployment of Policies to PDP GroupsDone - @Ram Krishna Verma REQ-33: Integration of CDS as an Actor in Control LoopsDone - @Rushmep REQ-150: Control Loop Tutorial DocumentationDone - @Eric Debeau | Subcommittee | ||
ATTENDEES
NOTES
Election Decisions
Chair only
Control Loop Subcommittee - send email for ONAP community to ensure membership list is correct by Oct 15, 2019
Ask ONAP community to ensure they have a single voter delegate per 4.4.1.4 section decided by Oct 22, 2019
Start the election on Oct 23, 2019 - for LF to run.
@Pamela Dragosh schedule a meeting with Policy, DCAE and wipro team to discuss Update Notification requirement. Next week possibly if time available.
Need to cleanup each FR wiki page with impacts, workflows and add commitment sections per project.
Also need to add how each FR will be tested.
Self Serve Issue - where is the Flow persisted?
Is it a push to CLAMP or does CLAMP query DCAE for all available flows for CL design? @Scott Blandford will setup a meeting for discussion.
Flow contains the blueprint ID - get the blueprint information from the DCAE inventory.
DCAE inventory is in the DCAE platform - existing api to pull this that CLAMP will use (instead of relying on SDC distribution). Work in Frankfurt is to associate the flow with the blueprint.