Page Comparison

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

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