Modeling 2020-02-18

START RECORDING:

 15

Co-chair

ONAPMODEL-3: General issues of Modeling subcommitteeOpen

@Hui Deng

@Andy MayerAndy Mayer

1) Email Polls

     None

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

• Action Item: Thinh help to remind Andrey get the registration done in ETSI.

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

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)  Thinh raised: ETSI start Release 3 to do enhancement for VNFD/NSD based on feature, question for ONAP how would you like to handle this information, such as: VNF software/VNF package notification.

     Action Item: present in Resource IM weekly call to discuss procedure: use case/requirement/Architecture/modeling

 5

ONAPMODEL-1: Resource IM of Modeling SubcommitteeOpen

@Xu Yang

@Kevin Scaggs

Resource IM

ONAP R6 Resource IM Call 2020-2-17

Discuss "As Built" License Model Comments: License Model Review Comments

Please review an provide comments by next Monday's Resource IM Call. Plan to reach closure before 28 Feb 2020.

 5

ONAPMODEL-2: Service IM of Modeling SubcommitteeOpen

@guochuyi

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

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

 5

ONAPMODEL-12: A&AI Reverse EngineeringOpen

@James Forsyth

@Jacqueline Beaulac [Ericsson]

AAI Reverse Engineering status

Addressed in Resource IM

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

30

Model Enabled ONAP effort

@Bob Papa

Invite the introduction about Model enabled ONAP

Action item: Andy could present service orchestration: Model_Enabled_ONAP.pptx

invite SO to present model driven POC next week .

0

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

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)