Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Meeting time: 13:00 UTC

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

2020 Modeling Subcommittee Recordings



Duration 60 minutes


DurationAgenda ItemRequested byNotes / Links

START RECORDING:

 15

Co-chair

ONAPMODEL-3 - Getting issue details... STATUS

1) Email Polls



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

      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: 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)  Joint SDC & Modeling subcommittee DM review:

  • 2 Potential topics: ETSI Package Management  & VNF SW Version (SDC & Modeling Subcommittee) (by M1)

5)  ONAP R7 Modeling High Level Requirements

Category 1 : R1/R2:

  Fred: Whether ETSI NFV 2.7.1 review next week will be decided by next Monday.

Category 1 : R3 will contact about how to proceed.

Category 1:  R4 Chuyi will detail the requirement

Category 2: Ben will handle them firstly , will contact with chairs once he need the help

Category 5: Container model documented, encourage the contribution.


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

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

Add Modeling Subcommittee meeting to the agenda. Andy Mayer


 5

ONAPMODEL-1 - Getting issue details... STATUS

Resource IM

ONAP R6 Resource IM Call 2020-5-25

Fred: ETSI Update (IFA 011 version 2.7.1) Virtual IP Support

 5

ONAPMODEL-2 - Getting issue details... STATUS

Service IM: Meeting Next Week to review requirements proposals.

Policy Model Editor Question. guochuyiwill take this on.

 0

ONAPMODEL-12 - Getting issue details... STATUS

AAI Reverse Engineering status


15VNF software version introductionLukasz Rajewski


5API Documentation

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

Reviewed and Endorsed by the Requirements Subcommittee on May 25th. 

see: May 25th, 2020

0 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 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

0Modeling and Use Cases

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




ACTION ITEMS:






Zoom Chat Log




  • No labels