There will be joint meeting between architecture and modeling subcommittee at Montreal in the morning of Oct. 31st, 2018
Modeling subcommittee has several topics which need architecture’s guidance, for example
1) How information model will be designed, will it also differentiate internal and onboarding model?
2) Will Network Service (NS) be supported in design and runtime?
3) How model translation be supported?
And also modeling subcommittee has some expectation to future architecture design like model driven
Under such two considerations, shall we apply for a time slot during architecture f2f meeting and also arrange the joint meeting like below agenda:
1) Operator’s input on modeling aspect related to architecture
2) Modeling’s expectation and requirement to architecture
3) Architecture guidance to modeling subcommittee
4) Conclusion.
Modeling subcommittee will call for those contributions during our regular modeling subcommittee call.
Monday 29th Oct
| Start | Duration | Topic | Desription | Presenter | Slides |
|---|---|---|---|---|---|
| 10:05 | 30' | SP Survey input on ETSI alignment | Service Provider Survey input on ETSI-ONAP alignment | ||
| 10:35 | Break | ||||
| 11:00 | 45' | Modelling interactions with Architecture | Modelling sub-comittee input on how architecture and modelling interact 1) role of modeling (10m) Andy Mayer 2) Resource IM (10m) Xu Yang 3) DM (10m) Anatoly Katzman 4) Service IM (10m) Lingli Deng | Role of Modeling: service IM: resource IM: DM: |
Tuesday 30th Oct
| Start | Duration | Topic | Desription | Presenter | Slides |
|---|---|---|---|---|---|
| 09:40 | 45´ | NSD modelling | Clarify and align on the architectural and modeling assumptions for handling of the network service descriptor (including internally to ONAP) | ||
| 10:45 | 45' | Recursive and model driven use of allocated resource | Resursive service design and model driven use of the allotted resource. What needs to be focused on in Dublin. | ||
| 11:30 | 30' | Tosca Task Force Update | Tosca Task Force Update. A dublin focus | ||
| 16:30 | 90' | Modelling | b.1) Resource IM conclusion related to Arch. (YANG Xu) 10m b.2) Data Model conclusion related to Arch (Anatoly) 10m b.3) Service IM conclusion related to Arch (MENG Lin) 10m b.4) Internal model related summary (Anatoly) 10m b.5) 5G related (Gil) 10m |
Offline modeling discussion: (breakout room table)
Please contact with leaders to join their discussion
1) Data Modeling
Leader: Anatoly Katzman
2) Resource IM
Leader: Xu Yang
Slides: VNF instance model.pptx
3) Service IM
Leader: LIN MENG
Modeling of network slice by network service
Recommended Schedule, up to leader
Monday Afternoon: 1pm-6pm
Tuesday Afternoon: 1pm-4:30pm
2 Comments
Anatoly Katzman
Proposed agenda to discuss:
1. Translation between the onboarding model and the internal model:
2. Identify and document ONAP components' requirements for the design-time and run-time data (Thinh volunteered to do this)
3. Preservation of the onboarding model and making it available across the platform:
4. Transition from the current internal model to the target internal model.
Gil Bullard
The current understanding of modeling 5G "slices" is as Allotted Resources (a.k.a., Allotted Network Functions). I thing it is good in each ONAP release to make progress towards support for 5G, and as such I have been proposing in the Orchestration space to make progress towards model-driven Allotted Resource orchestration. Should we therefore add to our discussion topics the modeling of Allotted Resources?