Meeting time: 13:00 UTC, 21:00 Beijing Time, 08:00 US Eastern
...
| Time | Agenda Item | Requested by | Notes / Links | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
START RECORDING: | |||||||||||||||||||||
| 5 | Agenda Bashing | ASD model 0 mins Co-Chair: - ONAP Model Governance Update 15mins - Have no time to discuss - Second Workshop with ETSI, suggest to happen at CET 2:00-3:00 PM on 3.15 or 3.22 , agenda: 1)deep-dive on ASD information elements 2)Q&A Time: Suggest to 3.22. Next Step:Details of external cp and etc., don't need to prepare much materials. Ericsson: What should be talked to them? Catherine: it is good to share the work to SDO. We try to move forward to cloud native and we can let the ETSI to learn the fruit of ONAP. Thinh: Suggest ETSI to prepare questions first. Agree with Catherine to share. Can ETSI change their architecture?If so, we can do and discuss something. Answer Bruno's questions. Marian: how to consider this workshop? Byung:ASD doesn't use MANO, does the discussion include the MANO architecture. Xu: IM is not related with implementation, we should separate them, it is necessary to share the info in the workshop to know the differences of current work in ETSI. Currently not go for the architecture. Thinh and Byung: IM DM should align with DMIM, so it is related with implementationDM and implementation are derived from IM. Xu: It shoud be "Information model is independent with any specific implementation " Catherine: ETSI can do what they want, we just share. Suggest to move the current page to clean "version 1" and as the starting point. Fred: Grab and supplementthe the missing attributes comparing the ETSI model, suggest not move to "clean" now Ericsson: Answer to fred, the information is in helm chart , it is another expression. Catherine: For the workshop, we should have the time for them and clean up the concerns before moving to "clean". Xu: We have one IM for container, now there is another proposal, prefer to have one IM,don't have a separated one. Thinh: How to avoid the abstract layer,such as ETSI MANO to cloud native K8S, avoid the mapping input and ouput attributes of cloud native ways ?That is the background of ASD. Conclusion and AP: Ask the ETSI to prepare the questions and bring to ONAP before 3.15 and try to clean up the concerns, we can use their bridge(recordings) and use CNF task force wiki page to carry the questions. ETSI CNF support mins Reverse engineering mins Topology model mins Modeling Documentation mins | |||||||||||||||||||
| 30 | Co-chair
| - Modeling current activity status Provide the dash board of current status and how to involve: See: Modeling Current Activity Status Please keep updated Please capture modeling requirements for R10 here: ONAP R10 Modeling High Level Requirements Proposed Jakarta Release Schedule: Release Planning: Jakarta Note: In JIRA, ONAPMODEL is the "project" we are using to capture Modeling Subcommittee release requirements. - AAI model review request Review AAI’s REST Spec/Schema AAI REST API Documentation - Jakarta on CNF and CCVPN Intent-based Cloud Leased Line and Closed-loop efforts. Do we need to invite AAI team for an update of the status? Xu will contact AAI team later. - ONAP Model Governance Update | |||||||||||||||||||
| 0 | ETSI CNF support
| R9 DM proposal: https://wikilf-onap.onapatlassian.orgnet/wiki/pages/viewpage.action?pageId=9301177216463007 ongoing work on alignment IFA011 v4.3.1 | |||||||||||||||||||
| 5+ | ASD model
| 1）Plan for the PoC: Application Package Onboarding to SDC 2）IM: Application Service Descriptor (ASD) onboarding IM 3）DM: Application Service Descriptor (ASD) Resource Data Model 4）ASD in NSD: NSD requirements for ASD deployment 5）Packaging proposal: Application Service Descriptor (ASD) Onboarding Packaging Format Comments: | |||||||||||||||||||
| ? | Reverse engineering
| Jacqueline Beaulac [Ericsson] | AAI Reverse-engineering -- K8S resource | ||||||||||||||||||
| ? | Topology model
| https://wiki.onap.org/display/DW/Proposed+Topology+IM+Sketch | |||||||||||||||||||
| 0 | Modeling Documentation | ||||||||||||||||||||
...