Modeling 2020-01-21

START RECORDING:

 15

Co-chair

ONAPMODEL-3: General issues of Modeling subcommitteeOpen

@Hui Deng

@Andy MayerAndy Mayer

Modeling Subcommittee Co-Chairs Self Nomination ended, two candidates for co-chairs

Ends 11 December at 3:30PM Pacific US time

https://wiki.lfnetworking.org/display/LN/Call+for+ONAP+DDF+Topics+-+Prague+2020

Prague meeting summary

1) Email Polls

Refinement to Dynamic Parameters

The polling period will be open until 22:00GMT on 17 December. 2019.

Conclusion： 4 Yes, 1 abstain. Reached rough consensus, stereotypes will be updated to preliminary

As-built License Management Info Model

Conclusion: 2 Yes and 2 No votes. @Michela Bevilacquawill post comments on the wiki. Comments will be reviewed and proposed resolution will be addressed before another poll. Discussion will be discussed during the Resource IM calls.

2) PNF Software Version  (@Fei Zhang (Ericsson) )

•  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 @andreikto draft email to ETSI to inform them of the new item for PNF Software Version

  • May discussed in an upcoming SOL meeting next week.

  • The SOL chair allocated this topic to the upcoming Remote SOL meeting.' CR is NFVSOL(19)000205r2.

• Shitao: Andrei presented in ETSI meeting, there are some comments like wiki page not official, let's replicate with readthedoc with official release.

3)  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

Next step: ask Model lead to LINK the Jira task

M2 is today, no new modeling activities for this release.

4)  ONAP M2/M3 deadline: 21th Jan. 2020

Modeling subcommittee will not accept any new modelspec

and will review each Project M3 model checklist (model spec and API)

See: Frankfurt Release Requirements

Use Case Realization will discuss 5G modeling activities during tomorrow's call.

 5

ONAPMODEL-1: Resource IM of Modeling SubcommitteeOpen

@Xu Yang

@Kevin Scaggs

ONAP R6 Resource IM Call 2020-1-20

• VES Spec

• PNF Instance Model (need to clean up duplicate classes)

• Model Glossary (further discussion with documentation subcommittee)

• Allotted Resources (will discuss in 2 weeks)

• Discussed overall structure of information model, perhaps update readthedocs structure

• Will discuss comments on License model

 5

ONAPMODEL-2: Service IM of Modeling SubcommitteeOpen

@guochuyi

No call last week.

Conclusion: Jan. 8th will reopen, if no service model item, then resource IM will borrow this time slot

Can TM Forum presentation from David be shared? @Andy Mayerwill ask David

No call Jan 22 and Jan 29th

 0

Papyrus

@Kevin Scaggs

nothing to report

New Papyrus does not like spaces in GenDoc

 5

ONAPMODEL-12: A&AI Reverse EngineeringOpen

@James Forsyth

@Jacqueline Beaulac [Ericsson]

0

Documenting ONAP APIs

@Andy Mayer

Call on Friday to review tools for validating Swagger and producing documentation.

Developing ONAP API Documentation

5

ONAP Glossary

@Andy Mayer

@Kevin Scaggs

• Review: The Glossary of Modeling Subcommittee

• Meet doc team on Thursday, add stereotype back again. report next week.

• 
  
  

  DOC-154: Integrate Glossary Provided by Modeling SubcommitteeClosed

• 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).

• Draft Glossary Posted in Contribution Area

  • Some cleanup is still needed. (do old artifacts need to be removed)

  • What filters need to be applied based on stereotype (preliminary, experimental, etc.)

    • Perhaps include stereotype on the glossary items

    • Further Discussion next week:

      • Agreed to remove Experimental from Glossary (or we can mark definition as Experimental, discussion?)

      • Need to explore removal of Examples from Glossary (any opinions?)

  • Add item to Documentation Project agenda for next week to share status

  • Includes Classes, Datatypes, and Enumerations

  • Link: Modeling sub-committee Contributions

  • Reviewing Glossary and Model definitions with Documentation Project

Call for volunteers who are familiar with GENDOC.

0

Modeling and Use Cases

@Benjamin Cheung

@Andy Mayer

Proposed ONAP Release Process Updates for Information and Data Modeling

After M2, will come back to modeling subcommittee.

Will discuss M3 process next week.

Proposed Functional Template for Use Cases