START RECORDING:
TSC priorities:
Jira space of modeling subcommittee discussion
3 EPICs: Resource IM, Service IM, General
Under each EPIC, there are many tasks.
Please provide task owners
Under Resource IM EPIC: owner (yangxu)
Task 1.1 Common IM / License
Task 1.2 Common IM / VES update
Task 1.3 Resource IM / Allotted Resource
Task 1.4 Resource IM / PNF instance
Under Service IM: owner (chuyi )
Task 2.1 Service IM / Network Slicing Model
Task 2.2 Service IM / Slice Service KPI Monitor
Under General: owner (Andy)
Task 3.1: Modeling Process Update
Task 3.2 Glossary of modeling subcommittee
Task 3.3 Reverse engineering
Changed from MODELSPEC into ONAPMODEL similar to ONAPARCH
PNF Software Version (Fei Zhang )
- ONAP TSC approve it last week TSC meeting.
- Future proposal to send to the TSC list before TSC meeting between Tuesday and Thursday.
- Michela Bevilacqua has updated ONAP Non-MANO artifact registry
- Will ask Andrei Kojukhovto draft email to ETSI to inform them of the new item for PNF Software Version
Use the established wiki page for capturing modeling current activity status.
Provide the dash board of current status and how to involve:
See: Modeling Current Activity Status
Thanks Xu Yang update
Next step: ask Model lead to check status, wait for Jira assignment.
Also refer to Approved ONAP Model Governance
Integrate Glossary Provided by Modeling Subcommittee
- Review: The Glossary of Modeling Subcommittee
- Explore using the approved information model as a basis for the Glossary. Can GenDoc be used to create a Glossary based on IM Class Descriptions?Next step: Kevin is looking at GenDoc template and will review and feedback next week. Class, datatypes, enumeration definitions first (note: attribute definitions need to be explored).
JIRA for Modeling Subcommittee Work (however publishing of spec Gerritt will be in the Modeling Project)
Discussion on approval of "Documentation - As Built" models
Possible use of stereotypes (may add a new one, or use "Reference Stereotype" to reflect "as built". Kevin Scaggsto make a proposal next week.
ONAP R6 Resource IM Call 2019-11-11
Request Licence Management Use Case team to involve ONAP End User Advisory Group
No call last week
Call tomorrow, new proposal for Parameter Group.
Papyrus
nothing to report
New Papyrus does not like spaces in GenDoc
Descriptions extract is still work to be done.
Which repo should RE Papyrus IM for A&AI reside? (possible use of sub-models) Can the model be imported and pulled from a separate repo? Kevin Scaggs Jacqueline Beaulac
For the descriptions on the AAI UML files need to get volunteers from the community to take this on but no help so far. Will continue to work on finding someone to own it.
Developing ONAP API Documentation
No meeting last week, will resume this week
Proposed OpenAPI 2.0 / Swagger Style Guide
Ask for review and comments, and feedback
Meeting minutes for ONAP API Documentation call:
2019-10-25 API Docs Meeting Notes
Agenda for this week: 2019-12-06 API Docs Meeting Notes
Proposed ONAP Release Process Updates for Information and Data Modeling
After M2, will come back to modeling subcommittee.
Will discuss M3 process next week.