...

1. Agenda Bashing
   1. IFA 015 UML work hasn't been discussed, we will wait Michela to discuss together.
2. NSD and AID SD mapping
   1. Fred and Byung showed an analysis of ETSI model and AID model mapping, the presented analysis can be found: ETSI Package Management (SDC Enhancements)- Guilin
   
   Orchestration Scenarios Meeting Information
   1. .  
   2. Current analysis for NSD includes attribute mapping between SOL001 and SDC org.openecomp.resource.vfc.NSD, based on the material shown by Thinh before.
      Image Added
      In the material, there has a suggestion to use tosa.nodes.nfv.NS directly in SDC.
   3.  The modeling work for NSD can be 1)align NSD IM to v2.7.1, 2) translate it into ONAP internal data model.
   4. The basic issue for NSD is no initial node type for NSD in SDC. VFC is using org.openecomp.resource.vfc.NSD, but the goal is to provide a general model mapping that can be used by all other run-time components, like DCAE, which highly depend on AID model. In R7, there will have contribution to support SOL 007 in SDC.
   5. PNFD has works for mapping with AID model by Ericsson in SDC, but no works for VNFD. VNFD suffers challenges. In AID model, there has VF module, while ETSI doesn't, VF module and ETSI SOL 001 is not 1 to 1 mapping. The ONAP components may need VF module, but vendors don't need. The mapping work is also expected to support CNF as well.
   6. VLs now are vendor specific, and is differnt from ETSI in current implementation. Suggested solution is to use tosca.nodes.nfv NsVirtualLink.
   7. Suggest to have a talk with VFC to seek for their perspective, Byung will summary this, and send email to VFC team. There has Orchestration Scenarios Meeting on Monday to talk about ETSI alignment issues, Meeting Information can be found: Orchestration Scenarios

Recordings

zoom_0.mp4