General Information:
- Date and Time: 2020, Oct 12th, 9pm~10pm Beijing Time, 9am~10am US Eastern
- Meeting Room: https://zoom.us/j/97595070639 password: 244130
- Meeting Recording:
- Meeting Chat Log:
Agenda:
- Agenda bashing - 5 minutes
- Model Proposals
- allotted resource - 0 minutes
- 5G service - 0 minutes
- ETSI CNF support - 0 5 minutes
- PNF instance model - 0 minutes
- VES model update - 20 0 minutes
- CPS model driven PoC - 0 minutes
- R8 use case requirements and relationship with modeling - 20 minutes
- Modeling Documentation - 0 minutes
...
- Agenda bashing
- Model Proposals
- allotted resource
- the plan is to finish the network slicing discussion in service model first, then discuss allotted resource
- VES model update
- no one shows up, postpone to next call
- CPS model
- postpone to next call
- ETSI support for CNF model
- ETSI has finished the modeling, a team has formed to investigate how to introduce them to ONAP
- Fred has begun to study on the papyrus model
- question: whether to submit 2 set of changes for v3.x.1 / 4.1.1 of ETSI specs, or 1 set of changes
- plan to work on both design time and run time model
- move the old page under R8/Honolulu, create a simplified version for R7
- will discuss the detailed changes next week
- R8 use case requirements and relationship with modeling
- R8 Honolulu Use Cases & Requirements
- use case overviews and demos are shown on the page
- NOTE: Ben has presented the arc team working process to the TSC, ONAP Architecture Team Process, request people to review
- use cases:
- Plug & Play: R8 plan is to further study how to use the "place" model
- VES: there are existing updates (VES 7.2), no plan for R8 now
- 1.2.44 is requested to be reviewed, the question is where to use this data type
- Ben will help invite VES team to present next Monday
- allotted resource
- Modeling Documentation
- R6 readthedocs review:
- gendoc template improvement: ONAP Information Model - Gendoc Examples
- AP: simplify the sterotypes for the associations, Xu will help summarize the status and trigger the discussion
- add relationship documentation to the UML guideline:
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key ONAPMODEL-28 - UML principle wiki page:
- Principle and Guideline for Information Model Proposal Using Papyrus (Draft)
- https://wiki.onap.org/pages/viewpage.action?pageId=84669384
- reviewed, no comments for now
- will continue working on the pages
- UML principle wiki page:
- R6 readthedocs review: