Modeling 2020-05-12

Modeling 2020-05-12

Meeting time: 13:00 UTC

Zoom Meeting Link:  https://zoom.us/j/137904496 International numbers available: https://zoom.us/zoomconference?m=mi-ad1sMLWlXByAKLio5vDnd9JYqUR_a

May 12, 2020

2020 Modeling Subcommittee Recordings

May 12, 2020

2020 Modeling Subcommittee Recordings

 

Duration 60 minutes

 

Duration

Agenda Item

Requested by

Notes / Links

Duration

Agenda Item

Requested by

Notes / Links

START RECORDING:

 15

Co-chair

https://lf-onap.atlassian.net/browse/ONAPMODEL-3

@Hui Deng

@Andrew Mayer

1) Email Polls

 

 

2) Non-MANO Artifacts  (@Fei Zhang (Ericsson) ) Come back until end of Frankfurt release)

  • ONAP Non-MANO Artifacts Set Identifiers

  • @Michela Bevilacqua [Ericsson] 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: (Michela Bevilacqua)

Action item: @Michela Bevilacqua [Ericsson] 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: Initiated ETSI review. Awaiting response from ETSI

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 @Ben Cheung (Nokia)

    • 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

Added information flow elements to the Arch Template

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 [Ericsson]

8) June virtual LFN Developer and Testing Forum event, deadline June 3rd: https://wiki.lfnetworking.org/pages/viewpage.action?pageId=34606297

June 22-25

Deadline for topics June 3

 

A5

CNF Modeling

@Fernando Oliveira

@Byung-Woo Jun

@Andrew 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.

 10

 Review use case process update

@Hui Deng

Use case guidance from Modeling subcommittee

 Proposed ONAP Release Process Updates for Information and Data Modeling

 5

https://lf-onap.atlassian.net/browse/ONAPMODEL-1

@Xu Yang

 

Resource IM

ONAP R6 Resource IM Call 2020-5-11

 5

https://lf-onap.atlassian.net/browse/ONAPMODEL-2

@guochuyi

 

Service IM

 

 5

https://lf-onap.atlassian.net/browse/ONAPMODEL-12

@James Forsyth

@Jacqueline Beaulac [Ericsson]

AAI Reverse Engineering status

 

15

 

@Ben Cheung (Nokia)

GeoLocation Model Update

PNFD/SDC AID/AAI Schema Modeling/5G Svc Model - R7 Discussion

5

API Documentation

@Andrew Mayer

Developing ONAP API Documentation

Discussed 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: Created 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:

Added Non-functional requirements in wiki

Created JIRAs within documentation project:

Epic: https://jira.onap.org/browse/DOC-608

User Story: https://jira.onap.org/browse/DOC-609

User Story: https://jira.onap.org/browse/DOC-610

User Story: https://jira.onap.org/browse/DOC-611

Scheduled to review with Requirements Subcommittee on May 25th.

 5

 Container model

 

0310: Introduction of K8S module in MultiVIM project

cFW orchestration demo 

HowToOrchestrateCNF

0324: Invite K8S PoC

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

0421: Container Modeling at April Technical Event

 

Modeling and Use Cases

@Ben Cheung (Nokia)

@Andrew 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. @Ben Cheung (Nokia)is 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

 

 

 

ACTION ITEMS:

 

 

 

 


Zoom Chat Log