Modeling 2021-01-05

START RECORDING:

 15

Co-chair

ONAPMODEL-3: General issues of Modeling subcommitteeOpen

@Hui Deng

@Andy Mayer

1) Email Polls: 2020 Modeling Subcommittee Decisions

A) Initiate Email Poll on the "as-built" CPS model. See:  Support for CPS Model Driven PoC R7

Rough consensus will be addressed on 15 December 2020

Yes: Nokia, AT&T, Ericsson  No: zero; Rough consensus met. Model may be moved to clean state.

2)  Modeling current activity status.

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

See: Modeling Current Activity Status

Please keep updated

Please add ONAPMODEL JIRAs for the ONAP R8 Modeling High Level Requirements items

3) Request initiation of co-chair election process 

See: Annual Community Elections - Process

and: Voting Best Practices

and: Voting Results History

On TSC Agenda; Kenny initiated email poll to TSC on 15 December 2020

@Hui Deng and @Andy Mayer approved by TSC email poll and announced at 17 December 2020 TSC meeting.

4） Future DM discussion （where and when to discuss it）(Dec 8)

the minimal changes that would need to be made to the SOL004 v 3.3.1 and SOL001 v3.3.1 specifications in order to support the onboarding and deployment of container based Network Functions. proposed by @Fernando Oliveira @Byung-Woo Jun

Initial proposal available  VNF/CNF Data Model Based on ETSI v3.3.1 SOL001 plus CNF Enhancements#VDUOsContainerDataModel

PLEASE COMMENT on the proposed model.

VNFD , CNF CSAR, YAML, reference to vFW , Helm charts.  initial discussion yesterday in orchestration 

Purpose: don't want to stop the implementation, for the purpose of experiemental, will be aligned with ETSI NFV standard spec.

5） 2021 February LFN Developer & Testing Forum

1-4 Feb 2021

Proposals Due 15 Jan 2021, see: https://wiki.lfnetworking.org/display/LN/2021+February+Developer+Topic+Proposals

15 Minutes @Benjamin Cheung @Andy Mayer New Train process impacts on modeling and use cases.

45 Minutes Container modeling workshop (joint with ETSI NFV SOL001 update @Hui Deng ) @Fernando Oliveira @Byung-Woo Jun

6) Questions from HOLMES-389

HOLMES-389: Data models shared with Modeling subcommitteeClosed

1. What if the model, such as VES and the closed control loop events, we use is defined by other projects? Do we have to provide them to the modeling subcommittee again? If the model is already documented, there is no need to provide it again to the modeling subcommittee. If new, a modeling requirement needs to be added and assigned. For VES, the model is defined here: VES 7.2

2. As for the models that are for internal use only, do we have to share them, as well? No need to model internal information that is not exposed externally by the system to other components.

 5

ONAPMODEL-1: Resource IM of Modeling SubcommitteeOpen

@Xu Yang

Resource IM

ONAP R8 Resource IM Call 2021-1-4

Will discuss comments on container updates next week's Resource IM call. Will share with ETSI NFV on 14 JAN to get feedback.

 5

ONAPMODEL-2: Service IM of Modeling SubcommitteeOpen

@guochuyi

Service IM

Next call 13 JAN

 0

ONAPMODEL-12: A&AI Reverse EngineeringOpen

@Jacqueline Beaulac [Ericsson]

@William Reehil

AAI Reverse Engineering status

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

Plans for Honolulu

@Benjamin Cheung @Kamel Idir

Discussion on Papyrus and Eclipse version compatibility .  Guidance page is updated to use latest version.