Modeling 2020-07-07

START RECORDING:

 15

Co-chair

ONAPMODEL-3: General issues of Modeling subcommitteeOpen

@Hui Deng

@Andy 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 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: Initiated ETSI review. Received 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

Please update for Guilin

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 

• See: REQ-334: ETSI-Alignment for GuilinDone

• For ETSI current SOL015 model please see: https://docbox.etsi.org/ISG/NFV/Open/Drafts/IFA015ed341_Info_Model_Report/NFV-IFA015ed341v336.zip

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.

Are JIRA's in place? @guochuyito add Policy Story. 

Please add JIRAs for Experimental items: @Fernando Oliveira @Byung-Woo Jun @Seshu Kumar Mudiganti @Benjamin Cheung @Andy Mayer

6) updated Modeling Subcommittee List 

Modeling Subcommittee Members

 5

ONAPMODEL-1: Resource IM of Modeling SubcommitteeOpen

@Xu Yang

Resource IM

ONAP R7 Resource IM Call 2020-7-6

 5

ONAPMODEL-2: Service IM of Modeling SubcommitteeOpen

@guochuyi

Service IM: 

ONAP Service IM Minutes 20200701

 0

ONAPMODEL-12: A&AI Reverse EngineeringOpen

@James Forsyth

@Jacqueline Beaulac [Ericsson]

AAI Reverse Engineering status

0

CNF Orchestration Modeling

@Seshu Kumar Mudiganti @Andy Mayer

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

10

Modeling and Use Cases

@Benjamin Cheung

@Andy Mayer

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

Proposed ONAP Release Process Updates for Information and Data Modeling

See: ONAP Use Case / Requirements Teams Process Way of Working (WoW)