...

1. Papyrus Service domain project issue
   1. Current papyrus has one space for ONAP Service model, one space for NSD, but in common RootEntity hierarchy or anywhere, there is no description for the relationship between Service model and NSD: 1)ONAP service has ServiceDescrptor and NSD, 2)ServiceDescriptor and NSD can be composite or atomic, and ServcieDescriptor can nest NSD.
      Proposed solution is to add NSD to the common root diagram.
   2. In the Sevice.di, there are multiple diagrams that are under progress, making it not clear which part really works, what has been accepted, what is not pursuing anymore. guochuyi  wil do the clean-up to delete the obsolete diagrams.
   3. In information model, we don't differ onboarding model and internal model, VNFD/PNFD in the diagram can represent onboarding model or SDC internal model, but how to map this to data model?No conclusion.
2. ETSI NSD/VNFD/PNFD Model alignment issues in ONAP
   
   1. SDC VF module is not 1 to 1 mapping to VNF(also impact CNF), SDC internal models have much differences between ETSI models, this cause confusion in run time. This confusion is expected to be solved at modeling team. We may need resources from more companies or operators to solve this problem together. Fernando Oliveirawill prepare a material to present more details about this problem for further discussion.
   2. NSD papyrus model is a very old version and need to update to align with v2.7.1, since there has a lot of content to update, Chuyi suggested to star with the requirements of R7.
3. Time changes. It seems today's time slot (UTC 12:00) is preferred, so we consider to shift meeting time 1 hour earlier.

Recordings

zoom_0.mp4