Date
Attendees
Discussion items
TIME FOR THIS MEETING WILL BE 2PM UTC = 10AM EST (USA); 7 AM PST (USA)
| Item | Who | Notes | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| M1 Deadline Deliverables | All in 5G U/C | M1 Deliverables, DEADLINE: Nov 14, 2019 PTLs need to close 33 open Jiras tickets to proceed (these tickets Clarify R6 req & scope by project): Frankfurt Milestone Status Release Planning Page: Release Planning M1 Deliverables Checklist: Deliverables for Planning Milestone Checklist Template (1) TESTING - Integration Testing End-to-end use cases. Creation of Test case (high level). Identification of Integration lead and environment and testing resources needed. NOV 07: Still to be done. OPEN POINT. (2) PTLs - Commitments from the Platform component PTLs DONE (3) RELEASE MANAGEMENT - Frankfurt Release Requirements has been updated. This release requirement page tracks REQ jiras, PTL & Company commitments, Project component impacts & Size. DONE. Only PNF PnP & E2E Network Slicing are Yellow. (4) MODEL - Modeling Requirements Page for R6 (Planning). See this wiki: ONAP R6 Modeling High Level Requirements . DONE (5) CHECKLIST - Deliverables for planning milestone checklist template: Deliverables for Planning Milestone Checklist Template . (See other points in this list) (6) DOCUMENTATION - Documentation (Read the Docs) - READ THE DOCS: https://onap.readthedocs.io/en/latest/index.html
(7) Security Vulnerabilities - The security vulnerabilities and nexus IQ scans are done by PTLs. The 5G U/C teams do not need to do anything there. N/A (8) Product Management - Creating your Jira (Epics & Stories) Backlog for your 5G Use Cases. DONE. (9) Development Teams - Identify and list your key development contacts on the Wiki. INVESTIGATE & CHECK ACTIONS per 5G U/C: 1. RunTime Config DB Integration Lead
3. TESTING & INTEGRATION PER USE CASE (Open) Many of the 5G and PNF U/C need to specify at a high-level the integration & testing info. Integration Testing End-to-end use cases. Creation of Test case (high level). Identification of Integration lead and environment and testing resources needed. See the PNF PNP as an example: 5G - PNF Plug and Play#5G-PNFPlugandPlay-TESTING-PNFPLUGANDPLAYINTEGRATION&TESTING TSC call discussion of M1 milestone for R6. OOF, Pomba, Logging, UUI, Holmes = No resources; if what's in R5 is ok you are ok; if in R6 you need enhancements to these you may be at Risk. many Logging tickets jira. So Logging team said we don't have resources. M1 - 5G / OOF SON YELLOW CCSDK stretch goal. PNF / Plug and Play YELLOW SO lack of commitment, resources - SO weekly meeting on scope of R6. comes down to commitment; if resources exist, may need confirmation. Nokia has identified the developers for SO work. Agreed to close the loop with Seshu. Ben met with Nokia dev. team to confirm. PNF BPMN W/F > BB. 5G / E2E Network Slicing YELLOW SO & Ext-API lack of resources - OOF , UUI is resource constrained and OOF, UUI can't make enhancements. OOF/UUI is dependent on these. OOF is needed. selection and enhancements needed. SO was listed as approved, why is this still an issue? At TSC call Swami discussed, Seshu Kumar Mudiganti said committed. UUI probably not needed. Discussion deadline was Sept 2019 didn't have commitment. OOF has pythos 2 dependency. December 5, 2019: NEW M2/M3 Date: New M2/M3 date is January 21, 2020. Team should work PTL to ensure needed APIs are defined and frozen by that date. | ||||||||
| ORAN ONAP Plugfest Demos | All in 5G U/C | Next week Nov 13, 2019 will be a ORAN/ONAP Plugfest discussion with Tracy Van Brakle Demos will be on Thurs Dec 5, 2019 (AM EDT UTC-4 USA) at Rutgers Lab (Brunswick NJ). Use Case Realization call for Nov 13, 2019 will be another discussion: Use Case Realization Call: November 13, 2019 Dec 5 Plugfest Nokia identified issues w/ the Rutgers lab. The lab was setup to demo 5G OOF/SON/PCI U/C and there isn't sufficient components to run PNF PnP. For example A&AI isn't deployed. It isn't on the latest R5 El Alto load. Health check fails. Rutgers needs to be brought up to the latest R5 load. Oskar Malm - Ericsson plan is run from their lab. | ||||||||
| R6 Use Case Proposals / Requirements | All in 5G U/C | TSC Release Page. Frankfurt Release Requirements WHAT IS A USE CASE VS A REQUIREMENT? In the REQUIREMENTS Table of the R6 Release Requirements Wiki (above) the Use Case requirements as discussed on the TSC call for Sept 12, and David McBride has asked that we have requirements (jiras) on separate rows. Further follow-up discussions will be had for "what is a use case" and if some of the 5G use cases should be moved up to the first table. | ||||||||
RunTime Config DB | Architecture S/C presentation for Run Time DB.
Team is working to define the Proposal (see wiki). Then it will be presented at the Arch S/C and then TSC. Will be part of CC-SDK. CONFIGURATION PERSISTENCE SERVICE R6 not a separate component in R6. | |||||||||
| Network Slicing R6 Proposal | Update on slicing proposal. SO/Seshu presented. Multiple functional requirements/Use Cases. Recursive orchestration of nested services. Didn't want independent W/F for flows but try to leverage/reuse work. Presented the End to End U/C with macro-view for E2E slice. and components impacted. Right now impact will be on SO, OOF, Policy, SDC and AAI. What controller will be used for managing slices? Focusing on design aspects and instantiation and activation. Put up logical E2E slice. Target simple VNFs. Focus to create VNF vs reconfiguring a VNF? Slice segments are going to be both dedicated/shared. Started with discovering existing resources; assume segments created with VNF/PNFs in inventory & discoverable. Spinup new slice instances. Presentation/slides at: NETWORK SLICING PoC in R6 Frankfurt (Obsolete) Convergence Plan Presented Oct 17, 2019.
Setting up Regular meetings Presentation planned for the U/C realization call Discussion: Milind Jalwadi
Presentation given on Use Case Realization Call Use Case Realization Call: November 20, 2019 for Network Slicing discussion | |||||||||
| ORAN/3GPP ONAP Harmonization U/C | Trying to settle on scope of the Use Case. List of many possible contributions that will take more than one release to complete. Impacts for items to be added to wiki (analysis). Prioritize the work items what we could propose to accomplish. CM Notify as a new domain has been accepted on the DCAE S/C today Oct 24 2019. Dongho Kim will be creating the test/integration page. - A1 & O1 test integration pages have been added & links. | |||||||||
| WoW w/ Model & Arch | Way of Working between Architecture , Modeling Subcommittee & Use Case Teams and what happens and touchpoints at M0/M1/M2/M3. | |||||||||
| Use Case Template | 5G U/C Team | Use Case Template - discuss updating the Use Case template & pages with some of these fields. Modeling team has said it would be useful for them to have the pre-condition & post-conditions, and information being passed (info-flows) documented. Filling out, describing and creating the Wiki for a Use Case Use Case Tracking Template and Use Case Template Proposed Functional Template for Use Cases Ben talked w/ Andy Mayer U/CR call Oct 23. He said he is preparing the page, and would present here at the 5G U/C S/C call. | ||||||||
| 5G Service Modeling, Bulk PM, PM Dictionary, 5G NRM | 5G U/C teams | Chaker Al-Hakim - History Inventory resources associated w/ xNF. Assumptions: what are the resources that I need to inventory about a xNF so that I have a complete view of the VNF. parms added due to nature of VNF. resource inventory didn't have to do with provisioning data that the xNF can have. Should be evolved to reflect what we know today. | ||||||||
PNF Pre-onboarding/ onboarding PNF / Plug and Play, PNF / NetConf PNF / SW Upgrade | PNF U/C teams | |||||||||
SUPPORTING SLIDES
| Document | File |
|---|---|
| Presentation | |
RECORDING
| Recording | File |
|---|---|
| MP4 (Video + Audio) | |
| Audio Only | |
| M3U, Chat |
