Page History

START RECORDING:

Co-chair

Hui Deng

Andy MayerAndy Mayer

1) Email Polls

     None

2) PNF Software Version  (Fei Zhang )

• ONAP Non-MANO Artifacts Set Identifiers
• Michela Bevilacqua proposed long life wiki page to maintain, but publish in xNF Requirements in readthedocs for each release. Will share proposal with stakeholders.

      Slides describing the proposal available for comments: ONAP Non-MANO Artifacts Set Identifiers_PA3.pptx (Michela Bevilacqua)

Action item: Michela Bevilacqua will connect with VNFRQS PTL to build lifetime readthedoc.

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

4)  20200422-23 ONS -NA

https://wiki.lfnetworking.org/display/LN/LFN+Technical+Meetings+at+ONES%3ANA+2020

Candidate topics: Apr. 22nd. 3 hours before lunch.

1) ETSI Alignment；1.5 hours

1.1)SO implementation

1.2) RM introduction

1.3) ETSI Thinh

2）Containers model: 2 hours

2.1 invite Multivim

2.2 Cloudnative PoC  from ONAP

2.3 CNCF TUG

2.4 CNTT Container subteam

3 Modeling planning for Guilin (not weekly call)

Xu Yang

Resource IM

ONAP R6 Resource IM Call 2020-2-24

Chuyi Guo

Service IM

No additional topics to discuss this week.

Possible to discuss 5G RAN modeling, 5G Use Case Call (10:00am EST on Thursday)  https://zoom.us/j/478423919

Chuyi Guo will be  5G RAN Info Modeling co-lead (along with Benjamin Cheung)

James Forsyth

Jacqueline Beaulac

AAI Reverse Engineering status

Addressed in Resource IM

New uml from AAi has errors that need to be fixed.

Bob Papa

Invite the introduction about Model enabled ONAP

Historical presentation：

1 Bob present latest progress on model enable ONAP

2 Andy present service orchestration: Model_Enabled_ONAP.pptx

Action item:

Bob Papa invite SO to present model driven POC next week .

Andy Mayer

• Review: The glossary Glossary of modeling subcommitteeModeling Subcommittee

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

• doc team expect doc generated from modeling.  but lack of resource to do it, current proposal to let doc team to take modeling gendoc to generate doc. at the end of release, revise template and create RST. Michela Bevilacqua  check whether there is the resource to support gendoc work.

  Jira
  server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key DOC-154

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

Benjamin Cheung

Andy Mayer

Proposed ONAP Release Process Updates for Information and Data Modeling

Discuss M3 process

Proposed Functional Template for Use Cases

Need to begin using these Functional Templates for each Use Case. Possibly merge into a single template. Benjamin Cheungis working with the Architecture Subcommittee (Use Case realization effort) to introduce.

See: ONAP Use Case / Requirements Teams Process Way of Working (WoW)