1. Architecture Face to Face Planning Meeting Data Modeling Breakout Session

2. Quick and Dirty Path for Dublin
There is a request for support of these selected typed from SOL001 v2.5.1
Type
Comment
tosca.nfv.nodes.PNF
New; To be discussed
tosca.nfv.nodes.NS, tosca.nodes.NS.VirtualLink.SAP
New; To be discussed; ETSI community wants to better understand the ONAP Service node type
VNF, VnfExtCp, Vdu.Compute, VirtualBlockStorage, VirtualObjectStorage, VirtualFileStorage, Cp, VduCp, VnfVirtualink
Already supported;
Need an update to align with the latest version of SOL001
Communicate to the PTLs: SDC, SO, AI&I, VID(?), etc.
Policy: InstantiationLevels, VduInstantiationLevels, VirtualLinkInstantiationLevels
Policy: scaling
Policy: affirnityRule, antiAffirntyRule
Data types to support all of the above
Some new, some to be updated

3. Long-Term Path – Translation from Onboarding into Internal DM
Try to translate VGW.csar to TIDM
Write down the challenges
We haven’t managed to get there 
AT&T has a draft of the translation logic, to be reviewed online after the F2F

4. Looking for a REAL SOL001 VNF for the Modeling community
NOT SunshineDB
LCM [partially] implemented
Artifacts: deployment images, implementation scripts
Configuration parameters for VNF,
Policies
Internal links, external links
Reasonable complexity: ~3 VFCs
Single deployment flavor

5. Relationships with other Committees
ModCom & the rest of the ONAP community From ARC:
ONAP components: API operation
Message name Id
Producer or consumer
Input parameters
Output parameters
ONAP components
Expect results
createServiceInstance
 producer
 Version
nsServiceName
nsServiceDescription
nsParameters: vnfProfileId
additionalParamForNs SO