Architecture Face to Face Planning Meeting Data Modeling

Architecture Face to Face Planning Meeting Data Modeling Breakout Session

Quick and Dirty Path for Dublin • There is a request for support of these selected typed from SOL 001 v 2. 5. 1 Type Comment tosca. nfv. nodes. PNF New; To be discussed tosca. nfv. nodes. NS, tosca. nodes. NS. Virtual. Link. SAP New; To be discussed; ETSI community wants to better understand the ONAP Service node type VNF, Vnf. Ext. Cp, Vdu. Compute, Virtual. Block. Storage, Virtual. Object. Storage, Virtual. File. Storage, Cp, Vdu. Cp, Vnf. Virtualink Already supported; Need an update to align with the latest version of SOL 001 Communicate to the PTLs: SDC, SO, AI&I, VID(? ), etc. Policy: Instantiation. Levels, Vdu. Instantiation. Levels, Virtual. Link. Instantiation. Levels New; To be discussed Policy: scaling New; To be discussed Policy: affirnity. Rule, anti. Affirnty. Rule New; To be discussed Data types to support all of the above Some new, some to be updated 2

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 F 2 F 3

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

Relationships with other Committees Mod. Com & the rest of the ONAP community From ARC: ONAP components: API operation Message name Id create. Service. Instance Producer or Input consumer parameters producer Version ns. Service. Name ns. Service. Description ns. Parameters: vnf. Profile. Id additional. Param. For. Ns Output parameters ONAP components SO Expect results 5