...
| Duration | Agenda Item | Requested by | Notes / Links | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
START RECORDING: | |||||||||||||
| 15 | Co-chair
| 1) Email Polls 2) Non-MANO Artifacts (Fei Zhang (Ericsson) ) Come back until end of Frankfurt release)
Slides describing the proposal available for comments: ONAP Non-MANO Artifacts Set Identifiers_PA3.pptx (Michela Bevilacqua) Action item: Michela Bevilacqua will connect with VNFRQS PTL to build lifetime readthedoc. Jira is created for VNFRQS. UPDATE: Updated Wiki Page, JIRA to update requirements. Ready for ETSI to review. For all non-MANO artifacts. Action: Initiated ETSI review. Received response from ETSI ACTION: Email back to ETSI, assuming no issues and we are proceeding. ONAP identifier should be part of ETSI registry. Thinh： ETSI NFV endorsed the registration for Non-MANO artificats last week, and posted on the wiki page https://nfvwiki.etsi.org/index.php?title=Non_MANO_artifact_sets thanks to Thinh for the coordination. Michela will help to update ONAP wiki page. 3) Modeling current activity status. Provide the dash board of current status and how to involve: See: Modeling Current Activity Status 4) Joint SDC & Modeling subcommittee DM review: Left issue: how to document DM spec, what about update AID model? approve AID officially?
5) ONAP R7 Modeling High Level Requirements Category 1 : R1/R2: Fred: Whether ETSI NFV 2.7.1 review next week will be decided by next Monday. Category 1 : R3 will contact about how to proceed. Category 1: R4 Chuyi will detail the requirement Category 2: Ben will handle them firstly , will contact with chairs once he need the help Category 5: Container model documented, encourage the contribution. ACTION: Do we need requirements for: O-RAN A1 Adapter; CMPS; and License Management Decision: we will start our own ONAP policy model firstly. Chuyi and MIchela will discuss offline, will join resource model call later. 6) updated Modeling Subcommittee List | |||||||||||
| 5 |
| Resource IM | |||||||||||
| 5 |
| ||||||||||||
| 0 |
| AAI Reverse Engineering status | |||||||||||
| 0 | CNF Orchestration Modeling | Release requirement: | |||||||||||
| 0 | Container model | 0310： Introduction of K8S module in MultiVIM project 0324： Invite K8S PoC CNF Taskforce takes place after Thursday's TSC: CNF-Taskforce Recordings 0421: Container Modeling at April Technical Event | |||||||||||
| 10 | Modeling and Use Cases | Please review and provide comments by next week to help finalize: Proposed ONAP Release Process Updates for Information and Data Modeling | |||||||||||
...