Modeling 2018-10-09

Meeting Info:

Zoom Meeting Link:  https://zoom.us/j/137904496
International numbers available: https://zoom.us/zoomconference?m=mi-ad1sMLWlXByAKLio5vDnd9JYqUR_a

2018 Modeling Subcommittee Recordings

Duration 60 minutes

DurationAgenda ItemRequested byNotes / Links
START RECORDING
 5Co-chair

Logistics: Is there a joint Modeling Subcommittee meeting at the ARC face to face?

Dublin IM and DM Requirements wiki page needs to be started. (also connect to work by component teams)

Need to discuss Modeling impacts on release checklists.

 5 Resource IM report Xu Yang

Discussed Allotted Resource Model, more examples are expected next week.

VES, wiki page will be created for discussion based on Papyrus. Discuss datatype to classes.

IM for events, need to describe artifacts inside packages.

Models are available via Read the Docs for Casablanca.

https://onap.readthedocs.io/en/latest/submodules/modeling/modelspec.git/docs/ONAP%20Model%20Spec/im/VnfdAndVnfInstance.html
this is the document for vnfd and vnf instance
please note that the UML diagrams are planned to be added afterwards
the NSD document has just been submitted, I think you will find it in a few days after the source code is merged
This is the link for all the documents for modeling spec: https://onap.readthedocs.io/en/latest/submodules/modeling/modelspec.git/docs/index.html
In the end, all the documents for R3 should be presented here.


 5 Service IM report Lingli Deng

Resuming calls this week.

Finalizing Papyrus model.

Service RST is uploaded in Read the Docs for Casablanca

Call for contributions for R4

 5 DM report

Walked through SOL001 constructs and TOSCA types, Example in A.5.

SOL001 wasn't intended to mandate TOSCA orchestration. Most important is the information represented in NFV Types. Will feed into Architecture TOSCA taskforce. Mapping SOL001 Sample into more standard TOSCA Semantics.

See: TOSCA Task Force

Taskforce should identify impact of model on ONAP components.

How does ETSI VNFD flow though ONAP Components?

 20How to identify ONAP components that are impacted by any DM/IM changes

Need to understand different model domains (e.g., on-boarding, design time, component specific, instantiation time, run time)

Modeling should focus on shared information.

Need to describe how information is produces, passed, and consumed.

Map into actionable work items for ONAP components. (e.g., mapping of on-boarding data model to internal ONAP model)

25ONAP architecture F2F joint modeling meeting

Joint meeting between architecture and modeling subcommittee 201810

Morning of Oct 31st, half day

Also, intermingle Modeling topics within Arch topics.

Work with Arch on ONAP Target, identify key capabilities for Dublin and identify priority modeling items.

Ask for Service Provider input on incremental Dublin priorities (use cases, architecture, modeling), obtain implementation feasibility from PTLs

Dublin Architecture Planning Meeting
Please provide contributions to the half day agenda by 23 Oct 2018.

15

Proposed ONAP Modeling Process




Kevin Scaggs

First topic next week.

On the topic of model governance, the deck can be found in the modeling contributions area of the wiki.
Modeling sub-committee Contributions


Action items

  •  

Agreement on ??



Zoom Chat Log