Modeling 2020-08-11

START RECORDING:

 15

Co-chair

ONAPMODEL-3: General issues of Modeling subcommitteeOpen

@Hui Deng

@Andy Mayer

1) Email Polls

2)  Modeling current activity status.

Provide the dash board of current status and how to involve:

See: Modeling Current Activity Status

Please keep updated

3)  Joint SDC & Modeling subcommittee DM review:

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

•  Potential topics: (Fred is defining IM and DM, Ericsson will make enhancement in SDC, reviewed in the future)

  • ETSI  Package Management , (SOL007 NS package,  after NSD/VLD), to support SDC to design firstly , other than onboarding.

  • Mapping between SOL001 VNFD/NSD DM and AID model， initial information model to meet REQ271 (difficulty: how to do nesting, composed /atomic model in ONAP)

  • Action:  SDC PTL.  invite @ChrisC

  • REQ-334: ETSI-Alignment for GuilinDone

  • step 1：info model: link:  ETSI IFA011 v2.7.1 Changes (review and collect feedback in resource model call and subcommittee poll later)

  • step 2:  approve changes, 

  • ETSI Package Management (SDC Enhancements)- Guilin#SOL001MappingtoSDCAIDDM

  • collect feedback in SDC and modeling subcommittee together and send an poll later.

  • 2.1: have a call to review the proposal (Friday, Internal Ericsson review(mapping and 2.7.1), next Monday review in SDC)

  • 2.2: email collect feedback (1 week) , will consult with A&AI PTL.

  • 2.3: poll on this. (2 weeks)

  • step 3: coding and documentation 

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

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

5) Request initiation of co-chair election process 

Modeling Subcommittee Members

@Hui Deng

@Andy Mayer

Data models shared with Modeling subcommittee

Guilin Release Data Model

Guilin Impact View per Component

ONAP R7 Modeling High Level Requirements

Action: review all

 5

ONAPMODEL-1: Resource IM of Modeling SubcommitteeOpen

@Xu Yang

Resource IM

ONAP R7 Resource IM Call 2020-8-10

 5

ONAPMODEL-2: Service IM of Modeling SubcommitteeOpen

@guochuyi

Service IM: NSD call at 8am eastern time IFA2.7.1 NS Descriptor changes

A&AI impact  will be discussed in A&AI weekly meeting 9am eastern time.

 0

ONAPMODEL-12: A&AI Reverse EngineeringOpen

@James Forsyth

@Jacqueline Beaulac [Ericsson]

@William Reehil

AAI Reverse Engineering status

open Jira ticket: get A&AI schema into papyrus. A&AI 2441 Guilin EPIC,

not necessarily done in Guilin （tomorrow A&AI call discussion）

10

Modeling and Use Cases

@Benjamin Cheung

@Andy Mayer

Please review and provide comments by next week to help finalize next week: Proposed ONAP Release Process Updates for Information and Data Modeling

Please attend Aug 10 Resource IM call if there are additional comments or questions.

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

Modeling process will be shared on the next Arch SC Call.

UC Information Element Templates are being filled in. 

See: Guilin (R7) - Use Cases (and Requirements in Use Cases)

Model review will be on Aug 12th: Use Case Realization Call: Aug 12 2020