...
Duration | Agenda Item | Requested by | Notes / Links | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
START RECORDING: | |||||||||||||||||||||
15 | Co-chair
| 1) Email Polls: 2020 Modeling Subcommittee Decisions 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 Topology Modeling Activity:
Could we add this to the Honolulu Modeling Requirements as Document Only (category 2)? 3) 2021 February LFN Developer & Testing Forum 1-4 Feb 2021 Should we cancel Modeling Subcommittee Call for Feb 2nd? AGENDA: https://teamup.com/ksgw6qzqcmg9zbzsfq?date=2021-2-1&view=MD4
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 == > Thinh will suggest the time slot from ETSI NFV side. ETSI NFV SOL weekly meeting on this thursday will discuss ONAP proposal of container DM. 4) Modeling review related in Honolulu release | |||||||||||||||||||
5 |
| Resource IM ONAP R8 Resource IM Call 2021-1-18 Container DM discussion: 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 |
| Service IM Next call 13 JAN, 1) network slicing, 2) NSD to support network service design. | |||||||||||||||||||
0 |
| 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. |
...