General Information:
- Date and Time: 2020, March 2nd, 10pm~11pm Beijing Time, 9am~10am US Eastern
- Meeting Room: https://zoom.us/j/645982535
- Meeting Recording:
- Meeting Chat Log:
Agenda:
- Agenda bashing - 5 minutes
- PNF instance model
- ETSI NFV R3 feedback
- Modeling glossary
- Modeling Documentation - 10 minutes
- Model Proposals - 25 minutes
- license management
- 5G RAN service
- allotted resource
- Modeling Process discussion - 15 minutes
Material:
- Proposed ONAP Release Process Updates for Information and Data Modeling
- License Model Review Comments
- Allotted Resource Revised
- 5G RAN SERVICE MODELING & DEFINITION in R6 Frankfurt
- https://docs.onap.org/en/elalto/submodules/modeling/modelspec.git/docs/ONAP%20Model%20Spec/index.html
...
- Agenda bashing:
- PNF instance model
- UML generation:
- the problem is "&" is not escaped
- next week Jacqueline will present the outcome
- UML generation:
- ETSI NFV R3 feedback
- modeling team (co-chairs) will create release G requirement page, and take ETSI NFV R3 feedback as an input
- For information: Guilin release - functional requirements proposed list
- will collaborate with use case realization team (as well as requirement team) on this
- Thinh suggest to pick specific features ONAP (modeling team) are interested in, e.g., VNF software update/change feature as an enhancement for VNFD/VNF package and network slice for service IM
- Thinh could help present network slice on service IM call (though current time slot is hard for him to join)
- could discuss with ETSI alignment team for the modeling
- the current modeling is based on v2.5.1 of ETSI specs, the latest version is v2.7.1; whether need to update in release G
- modeling team (co-chairs) will create release G requirement page, and take ETSI NFV R3 feedback as an input
- Modeling glossary
- need volunteer to put the fragments together
- create a wiki page for comments
- start review afterwards
- need volunteer to put the fragments together
- PNF instance model
- Modeling Documentation
- To discuss:
- what additional items are needed besides readthedocs?
- have an "index" wiki page to link to the approved models (wiki pages)
- Jacqueline will help create a draft page for that
- question: the page attach to each release?
- propose to create a high level page, but will document progress for each release
- what additional items are needed besides readthedocs?
- AP:
- add diagrams to readthedocs
- To discuss:
- Model Proposals
- license management
- License Model Review Comments reviewed
- Andy has created Jiras for the update
- License Management (Moved to Clean) updated
- Ricci found some issues when editing the papyrus model, Jacqueline will help
- will wait for the update, and continue review (next week)
- License Model Review Comments reviewed
- 5G RAN service model
- the material is based on 3GPP spec 28.541, maybe not all of them are needed for ONAP
- scope of the model requirements:
- 2 use cases: network slicing, OOF PCI
- need to introduce something, and show people how to use the models
- potential dupliciation with 3GPP spec
- suggest to start with something simple
- have already discussed with A&AI team for that
- suggest Ben to present the A&AI progress next time as a starting point
- allotted resource
- updated proposal at Allotted Resource Revised, request for review
- question:
- there was a quesiton on the change of relation in the last revision; Michela will take a look at the proposal to see if the question is clarified
- Andy will create a wiki page for discussing comments
- license management
- Modeling Process Discussion
arc team involvement for M3- use case is discussing the M2 process
- arc team is also starting to discuss the process (start from M0)
- 3 teams need to align some time later
- modeling should finish M4