Discussion items
| Duration | Agenda Item | Requested by | Notes / Links |
|---|---|---|---|
| START RECORDING | |||
| Model driven Control Loop Design - Review of the Dublin work and discussion on goals for El Alto to complete Self-Serve Control Loops. | |||
Control Loop Sub Committee Frankfurt Release Planning - Proposals for El Alto Functional Requirements | |||
ATTENDEES
Please put name here if I forgot you - some names I did not recognize. Sorry!
NOTES
- The CSAR packaging of the Monitoring policy types is split amongst 2 files - discuss with SDC PTL Ofir Sonsinocan we simplify the policy specific DataType into one file?
- Hard to know if everything is TOSCA compliant
- TOSCA Policy validation against the Policy Types
- Need to understand TOSCA specification with OASIS regarding the definition/use of Trigger policy types. Very ambiguous and not implementable.
- Targets may be doable in El Alto
- #7 Stretch Goal
STRETCH GOAL: Additionally, with the use of the new Policy Lifecycle API CLAMP will also be able to call the Policy Lifecycle API to query for available Operational Policy Types, Guard Policy Types, Control Loop Coordination Types, etc. for the Designer to choose from as desired.
Issue for Operational policy that the designer will need to specify target to take an action on. So how will CLAMP know that via the Policy Type specification to parse the CSAR looking for VNFs/VFModules as well as know to use vserver.
Create method for automating tests of generic control loops
Difficult to build generic tests - will have to defer
- Need API's for CLAMP/SDC because GUI testing is difficult
- Self Serve
- Should 17) Simplifying the onboarding steps for MS not specifically binded to SDC service be there for this functional requirement?
- Must prioritize the SDC engagement
