Versions Compared

Key

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

...

2020 Modeling Subcommittee Recordings


Duration 60 minutes


serverId

 (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.
  • 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

    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

    ACTION: Email back to ETSI, assuming no issues and we are proceeding. ONAP identifier should be part of ETSI registry.

    Thinh: ETSI NFV endorsed the registration for Non-MANO artificats last week, and posted on the wiki page 

    https://nfvwiki.etsi.org/index.php?title=Non_MANO_artifact_sets

    thanks to Thinh for the coordination. Michela will help to update ONAP wiki page.


    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:

       Left issue: how to document DM spec, what about update AID model? approve AID officially?

    •  Potential topics: ETSI Package Management 


    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.

    ACTION:  Do we need requirements for: O-RAN A1 Adapter; CMPS; and License Management

    Decision: we will start our own ONAP policy model firstly. Chuyi and MIchela will discuss offline, will join resource model call later.


    6) Wrapup: June virtual LFN Developer and Testing Forum event: 

    https://wiki.lfnetworking.org/pages/viewpage.action?pageId=34606297#id-2020JuneVirtualLFNDeveloper&TestingForumTopicProposals-ONAP-ModelingSubcommitteeMeeting

    Topics:

    1) Current Status and R7 Requirements (10 minutes) Hui DengAndy Mayer

    2) Modeling process (5 minutes) Benjamin Cheung

    == > Mostly highlevel overview, not in detail.

    3)Policy Model (guochuyi ) (policy implementation) (7 minutes)

    4)slicing Model (guochuyi ) (R7 Slicing requirements and design model) (7 minutes)

    == > one requirement for SDC, will discuss with them, their own weekly meeting.

    5) CNF Orchestration Task Force (CNF Inventory)  (5 minutes) Andy Mayer

    6) ETSI CNF Modeling Overview (7 minutes) Byung-Woo JunFernando Oliveira

    7) ETSI Alignment (VNFD) (7 minutes)Byung-Woo JunFernando Oliveira

     == >  CNF model (IFA011), and current status early draft, and early proposal. like SDC importal and A&AI influence.

    8)  Geolocation (7 minutes) Benjamin Cheung

    == > need a seperate meeting for geolocation, if want to attend, please contact with Benjamin. 


    7) updated Modeling Subcommittee List 

    Modeling Subcommittee Members

     5

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

    Resource IM

    ONAP R6 Resource IM Call 2020-6-829

    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
    4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyONAPMODEL-29
     5

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

    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

    AAI Reverse Engineering status


    15CNF Orchestration Modeling

    See: CNF Modeling Activity

    Release requirement: 

    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

    10Modeling and Use Cases

    Please review and provide comments by next week to help finalize:

    Proposed ONAP Release Process Updates for Information and Data Modeling

    ...

    ACTION ITEMS:





    ...

    Zoom Chat Log


    View file
    namechat.txt
    height250