Versions Compared

Key

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

...

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

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


6) Questions from HOLMES-389

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyHOLMES-389

  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?
  2. As for the models that are for internal use only, do we have to share them, as well?


 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

No meeting until Jan


 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

Call tomorrow. 

 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

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

Plans for Honolulu



Benjamin Cheung Kamel IdirDiscussion on Papyrus and Eclipse version compatibility 

...