Modeling 2020-05-05

START RECORDING:

 15

Co-chair

ONAPMODEL-3: General issues of Modeling subcommitteeOpen

@Hui Deng

@Andy Mayer

1) Email Polls

2) PNF Software Version  (@Fei Zhang (Ericsson) ) (Come back until end of Frankfurt release)

• 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. Jira is created for VNFRQS.

UPDATE: Updated Wiki Page, JIRA to update requirements. Ready for ETSI to review. For all non-MANO artifacts.

Action: Initiate ETSI review.

3)  Modeling current activity status.

Provide the dash board of current status and how to involve:

See: Modeling Current Activity Status

4)  How to proceed future DM discussion?

• Conclusion: SDC and Modeling subcommittee review and approve it together, (perhaps use SDC features meeting or Modeling Subcommittee meeting, with additional modeling breakouts if needed).

  • Engage Use Case teams for Frankfurt updates and Guilin data model requirements @Benjamin Cheung

  • Any updates?

  • Need Use Case teams to update Modeling Requirements page

  • Reach out to @Ofir Sonsinoto identify any model updates. (existing modeling of SDC, any updates to the model) to attend May 13 call.

5) R7 Guilin Architecture Review (template) - functional requirements

6) Review procedure:

6.1:  ONAP R7 Modeling High Level Requirements

6.2:  Use case guidance from Modeling subcommittee

Ref：Guilin (R7) - Use Cases (and Requirements in Use Cases)

Action item: encourage to review and comment

  Benjam will help to arrange modeling present in use case group on May 13th.

7) Proposal on how to describe and document relationships in ONAP Info Model @Jacqueline Beaulac [Ericsson] @Michela Bevilacqua

• JIRA Tickets Opened. See: ONAPMODEL-28: Using the Documentation Property for RelationshipsOpen and ONAPMODEL-29: Relationships in GenDocs generation modeling documentationOpen

• Created working wiki page:Introducing Relationship Documentation and GenDocs generation modeling documentation

5

@Fernando Oliveira

@Byung-Woo Jun

@Andy Mayer

Action review:

ACTION: Discuss any potential new modeling requirements for Guilin release. Yes, create one.

ACTION: create modeling subcommittee requirement (Is there a specific requirement activity, perhaps related to on-boarding of SOL001 VNFs) Guilin (R7) - Use Cases (and Requirements in Use Cases).

ACTION: Fred will create R7 requirement.

Discussing under Arch Task Force 1 meeting. weekly Monday's at 8:00am eastern (12:00 UTC)

We could also use the Resource IM call at 9:00am eastern

Fred will update Modeling subcommittee on activity.

 30

 Review use case process

@Benjamin Cheung

Use case guidance from Modeling subcommittee

 Proposed ONAP Release Process Updates for Information and Data Modeling

 5

ONAPMODEL-1: Resource IM of Modeling SubcommitteeOpen

@Xu Yang

Resource IM

ONAP R6 Resource IM Call 2020-5-4

 5

ONAPMODEL-2: Service IM of Modeling SubcommitteeOpen

@guochuyi

Service IM

 5

ONAPMODEL-12: A&AI Reverse EngineeringOpen

@James Forsyth

@Jacqueline Beaulac [Ericsson]

AAI Reverse Engineering status

5

@Benjamin Cheung

GeoLocation Model Update

5

API Documentation

@Andy Mayer

Developing ONAP API Documentation

Discuss Proposed Phased activities: (e.g., Minimum 1, 2, & 3 Guilin; 4 & 5 Stretch goals)

1. All components should place externally facing API definitions (e.g. Swagger) in a common path within their Gerrit/Git 

a.Suggested Path: <Component>/docs/api/swagger/

2.Apply ReDoc to Swagger and place HTML in Readthedocs for the release.

3.Apply Minimum (Phase 1+) swagger guidelines

a.Use common insert for Info section template

4.Use embedded markdown for conceptual documentation

5.Apply full swagger guidelines.

Proposed ACTION: Create non-functional requirements for Guilin release:

1. All components should place externally facing (i.e. interfaces exposed by the ONAP component to either other ONAP components or components external to ONAP) API definitions (e.g. Swagger) in a common path within their Gerrit/Git 
   Suggested Path: <Component>/docs/api/swagger/

2. Apply ReDoc to Swagger and place HTML in Readthedocs for the release

3. Apply Minimum (Phase 1+) swagger guidelines

   1. See: Proposed Phase 1+ OpenAPI 2.0 / Swagger Style Guide

   2. Use the common insert for the info section (e.g., license info, contact info, etc): Swagger Insert Sample for Info Section

Progress:

 5

 Container model

0310： Introduction of K8S module in MultiVIM project

cFW orchestration demo　

HowToOrchestrateCNF

0324： Invite K8S PoC

Intel_ONAP_k8_work.pdf

CNF Taskforce takes place after Thursday's TSC:  CNF-Taskforce 2020 Recordings

0421: Container Modeling at April Technical Event

ETSI NFV Container Architecture for ONAP v1.pptx

CNTT RA2 for ONAPv2.pptx

CNCF TUG Progress_0421.pdf

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)

May 13th call with Use Case teams.

April 16th 5G call will also discuss. (11:00 eastern US) https://zoom.us/j/478423919