Versions Compared

Old Version 1

changes.mady.by.user Hui Deng

Saved on

compared with

New Version Current

changes.mady.by.user Xu Yang

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

2020 Modeling Subcommittee Recordings

zoom_0.mp4


Duration 60 minutes


DurationAgenda ItemRequested byNotes / Links

START RECORDING:

 15

Co-chair

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyONAPMODEL-3

Hui Deng

Andy Mayer

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

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyONAPMODEL-1

Xu Yang


Resource IM

ONAP R6 Resource IM Call 2020-56-251

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


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

  • JIRA Tickets Opened. See: 
    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyONAPMODEL-28
     and 
    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyONAPMODEL-29
     (gendoc jira)
  • Created working wiki page:Introducing Relationship Documentation and GenDocs generation modeling documentation
  • Guideline or principles for papyrus modeling (objects, classes, and relationship only) are needed.
  • recommend to close Jira 29 and keep 28 open.
 5

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyONAPMODEL-2

guochuyi


Service IM: Meeting Next Week to review requirements proposals.

Policy Model Editor Question. guochuyiwill take this on.

 0

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyONAPMODEL-12

James Forsyth

Jacqueline Beaulac [Ericsson]

AAI Reverse Engineering status


15VNF software version introductionLukasz Rajewski5API Documentation

Andy 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:

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/
  • Apply ReDoc to Swagger and place HTML in Readthedocs for the release


    • Apply Minimum (Phase 1+) swagger guidelines

    See: Proposed Phase 1+ OpenAPI 2.0 / Swagger Style Guide
  • 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 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

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

    ...

    ACTION ITEMS:





    ...

    Zoom Chat Log

    View file
    namemeeting_saved_chat.txt
    height250