Meeting Minutes:

5G Use Cases:
https://wiki.onap.org/display/DW/5G+Use+Cases+in+R6+Frankfurt

• REST Based Interface --> AI Interface.
• A1 to support Rest based protocol with content ---
• CDS with AI Interface using Python/Kotlin [more efficent--reactive/non-blocking]
  • https://github.com/onap/ccsdk-cds/blob/master/components/model-catalog/blueprint-model/uat-blueprints/pnf_config/Scripts/python/RestconfConfigDeploy.py#L35
  • https://wiki.onap.org/display/DW/Modeling+Concepts#Concepts-2026349199
• Does CDS need to support External Systems allocation for 5G use cases? Interaction with external systems is made dynamic, removing development cycle to support new endpoint.
• In order to define the external system information, TOSCA provides dsl_definitions. Link to TOSCA spec info 1, info 2.

SO and CDS Integration comment---:

• SO to CDS need to make sure we pass the namespace/endpoint.
• Extend Marco Building block flows to existing flow architecture with the hooks of scope and action. 
• Discuss Strategy towards SO Tosca Driven orchestration and integration with CDS (long strategy --Frankfurt)
  • Benjamin M, Steve S, Seshu S, Alexis , Dan T , Damian, Henry, Mac, Munir, Eric M , Yuriy , Shawn

Policy and CDS Integration: 

• # 1. Alignment betweenon the AAI notation used inpolicy (node.attribute) and CDS (attribute) - AAI properties can be extracted outof config-deploy-properties into its own aai-properties as a workflow input under config-deploy-request 
• # 2. CLAMP rendering possible actions supported by CDS + rendering of the input fields from CBA - Open API generatedfrom the protobuff - Ingest the TOSCA yaml from CDS
• # 3. SO response back to CDS for selected params inorderto store them: e.g. in cases where VNF management IP isnot a static IP. - Use heatbridge information
• # 4. Distributed CDS orfor multi-tenancy: placeholder for the nameof CDS or an identifier to resolve a specific CDS instance (namespace) # 5. Spec for SLA for an end-to-end closeloop automation, existing data??