Date
Attendees
- Benjamin Cheung
- Junfeng Wang
- Lin Meng
- Lukasz Rajewski
- Sofia Wallin
- Timo Perala
- Marge Hillis
- Swaminathan Seetharaman
- Zu Qiang
- David McBride
- Albino Pinho
- Joanne Liu Rudel
- Rebecca Lantz
- Jessica Gonzalez
- Vimal Begwani
- Raghavan Subramanian
- Chuanyu Chen
- Marci Haas
- Maleni
- -
Discussion items
TIME FOR THIS MEETING WILL BE 2PM UTC = 10AM EST (USA); 7 AM PST (USA)
| Item | Who | Notes | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Discussion this week
| All in 5G U/C |
|
| Meeting notes from the Use Case Realization call for March 4. (from Marge Hillis) Agenda David McBride---M4 Requirements discussion Sylvia ---introduction to the ReadtheDocs and its evolution. M4 Requirements https://lf-onap.atlassian.net/wiki/display/DW/Frankfurt+Release+Requirements David reviewed the requirements and what he needs for the M4. Several folks had follow on questions: How do I mark my requirement if I am moving part of it out? Requirements can be scaled back even later in the release if we need to extend some of the work into subsequent releases. We need to be as accurate as possible in filling out the score card. Need to be clear when a requirement is being descoped and need to be clear on the existing status of the requirement as it is documented and include notes if some things will be de-scoped e.g. if you are moving some things out but haven’t done it yet you are probably yellow not green and you should put in notes saying the parts you can’t do and that you intend to move them to the Guilin release. If a requirement is moved do we have to get approval or can we assume its ok for the next release e.g. if move from Frankfurt is approval for Guilin automatic? The answer was no you have to communicate to the architectural subcommittee and let them know that Frankfurt scope was reduced and you want to be able to add it to Guilin. They will probably accept this but you have to review We were not sure what the Use Case Action item was that you wanted David to discuss. He suggested we re-schedule that. READ THE DOCS Sylvia provided an over view of the plans for the evolution of material from the WIKI to the read the docs site. The reason for making this evolution in documentation is to provide an easier more organized way to find official information. Much information will remain on the WIKI but critical Use Case information as it matures and stabilizes needs to move to the ReadTheDocs. A task force is being started to evaluate what material should move from the WIKI. One of the members of the audience (I didn’t’ catch the name) showed some examples of issues they were facing and with the difficulty in getting items to the Read the Docs. Sylvia acknowledged that the documentation is a little sparse and that they are working on improving the documentation guidelines. I asked if they might prepare a tutorial that they could film and post with the guidelines showing folks how to do some of the basic things and then providing resources for questions. Sylvia seemed very willing to do that. She said that they plan to have a Hackathon to improve the documentation and info on the hackathon is below. If anyone from the use case realization team is interested in participating or perhaps in being a beta contributor to move a use case using their new documentation and tools she would very much welcome that. Ben, I know you are sometimes willing to be an early adopter so please let her know if you want to get involved. She is also willing to come back to your project utilization call and provide updates on their progress with the idea that perhaps we can partner to start to move use cases. https://lf-onap.atlassian.net/wiki/display/DW/March+11th+Documentation+Hackathon A gentleman from Orange told us that the scale out use case is an excellent example of the sort of documentation we are looking for. Below is a link to that Use Case. He went through a bit of it and it seemed very impressive. Good example of use cases is https://docs.onap.org/en/latest/submodules/integration.git/docs/docs_scaleout.html | ||||||||||||||||||||||||||
| Release 7 GuiLin Release | All in 5G U/C team | R7 GuiLin Requirements & Proposals - Requirements S/C page: Requirements subcommittee R7 new requirements, currently proposals in R7: Guilin release - functional requirements proposed list Use Case Template: Use Case Tracking Template Take a R7 - example page. | ||||||||||||||||||||||||||||
| M4 Deadline Deliverables | All in 5G U/C | M4 for R6 Deliverables DEADLINE: R6 Frankfurt Release: Frankfurt Milestone Status Release Planning Page: Release Planning M1 Deliverables Checklist: Deliverables for Planning Milestone Checklist Template Deliverables by Milestone: Frankfurt Deliverables by Milestone (1) FUNCTIONALITY FREEZE - M2 MILESTONE: Functionality freeze No new visible functionality is to be added to the current ONAP release. A stable document describing the API is documented and available in wiki. Base set of impacts to VNF Requirements identified by use case/ project. (2) API & DATA MODEL FREEZE - M3 MILESTONE: API & data model freeze. Mark the end of API and Data Model change. API and Data Model are now Frozen. Any changes to the API must be brought to the knowledge of the TSC for review and approval. 50% of Functional Test Case are automated. (3) FUNCTIONAL TEST CASES - Functional Test Cases are defined & documented M2/M3 CHECKLIST: Release Planning (legacy)
M4 Deliverables:
(CONTINUOUS) - DOCUMENTATION - Documentation (Read the Docs) - M1 - M4
"Are you referring to MS1 and the preliminary documentation? https://wikilf-onap.onapatlassian.orgnet/wiki/display/DW/Frankfurt+Documentation This is mainly relevant to new projects. The link that you provided below covers that, since the 5G use case team is not a new project, your documentation is already published on RTD." - Gerrit Files, Gerrit Review, Main Branch, Update file, create Gerrit Review, RC0 RC1 RC2 Project Team focused its effort on:
| ||||||||||||||||||||||||||||
| CONFERENCES & DEMOS | All in 5G U/C | ORAN/ONAP Plugfest held Thurs Dec 5, 2019 (AM EDT UTC-4 USA) at Rutgers WIN Lab (Brunswick NJ). Official WIKI Site: https://wiki.o-ran-sc.org/x/egBv RECORDING OF DEMOS PLUGFEST CONFERENCE PLUGFEST
CONFERENCES April 22-24 Open Network & Edge Summit (ONES) - Los Angeles - GuiLin R7 (Planning).
Early June DDF - (GuiLin R7) ACTION: Will remote presentations be possible, links to remotely attend? When is final schedule up. | ||||||||||||||||||||||||||||
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. Sync with Sandeep - will meet with Sandeep Fri 7 2020. Ted Johnson. Existing interface. For R6, will be part of CC-SDK. Met with Yuriy Malakov & Dan Timoney . 5G CONFIGURATION (RunTime DB) CONFIGURATION PERSISTENCE SERVICE R6 not a separate component in R6. CMNotify - The DCAE, CMNotify VES event (proper) are pushed to R7
Feb 3-7 Nokia has confirmed that Step 2/3/4 is in R7 due to VES review. Meeting setup with Sandeep - R7 planning. Need to make a presentation for Alla's call: ONAP Use Case / Requirements Teams Process Way of Working (WoW) R7 - Decide if we can to be a separate component. need to find a PTL lead. Automation tool integration. Schema details.
| |||||||||||||||||||||||||||||
| 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) - Development is proceeding. Start R7 release in next couple of weeks. Next week there will be presentation on requirements for R7. R4 in 3GPP 28.541 - implemented as part properties of a service. didn't create separate TOSCA type for sliceprofile. Plan to introduce new serivce for serivce & slice profile properties in 3GPP those are recent doc updated in january. introduced many new properties from GSP. You've modeling team presentations were made, platform updated w/ network slicing.
| |||||||||||||||||||||||||||||
| 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. DongHo Kim leading the Integration Sandeep code was merged w/ SDN-C branch. Current container has the latest code. Continuing to test. In AT&T lab now being tested
| |||||||||||||||||||||||||||||
| OOF SON PCI | N.K. Shankaranarayanan | From SDN-R when we send config change align to NetConf Yang model avail. whatever yang model used, want config DB schema to be aligned w/ yang model to keep model driven. wanted Yang Models from ORAN if possible. In license catch-22. Some yang models for RAN on ORAN website due to licensing issues from Martin Skorupski took 3GPP model converted to files to compile. Issue w/ ORAN getting ok from 3GPP that it is a valid rep of 3GPP model. Option (1) use previous yang model, or (2) switch to ORAN model if available immediately. yang to SQL schema. Only need some parts of the model for SON project. Currently MariaDB continue to use. Piotr, Marek, et al. If there are useful file wo/ IPR issues, should be a way to use interim files. | ||||||||||||||||||||||||||||
| WoW w/ Model & Arch | Way of Working between Architecture , Modeling Subcommittee & Use Case Teams and what happens and touch-points at M0/M1/M2/M3. Modeling Way of Working / Process: Proposed ONAP Release Process Updates for Information and Data Modeling Use Case Way of Working / Process Use Case WoW Process: ONAP Use Case / Requirements Teams Process Way of Working (WoW) | |||||||||||||||||||||||||||||
| Use Case Template | 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. Proposed Functional Template for Use Cases (driven from MEF/TM Forum) - showing interactions & information flows. Filling out, describing and creating the Wiki for a Use Case Use Case Tracking Template and Use Case Template 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. REQUIREMENTS SUBCOMMITTEE - requirements sub-group / not bring use cases any more, refer to them as requirements. / proposed change talk less about architecture in requirements mtgs & reviews. more clear split between req & arch discussion. / Alla Goldberg changed U/C S/C to Requirements S/C. Security and ctl loop req will be discussed in those S/C; other things should go to Req S/C. Monday - - what input for Req review; should not go into realization aspects should be moved out of req review. What type of info & how much info at M0. when just reviewing proposed req. Andy has said Proposed Functional Template for Use Cases this is ready to go live.
| |||||||||||||||||||||||||||||
| 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 U/C teams | |||||||||||||||||||||||||||||
PNF / SW Upgrade | Zu Qiang | Reviewed with SO team. Preparing for DDF. will discuss with Change Management team, might be presenting. R6 in progress. Should be able to update/merge all Jiras by M4. No big risk. Integration RC0-RC2 | ||||||||||||||||||||||||||||
5G/ Bulk PM | Preparing presentations at DDF in Prague in DDF for R6 BulkPM functionality in Jan 2020. Demo in Dec 5, 2019 - R4 functionality. PM control part is green; the other bulk PM for certificate handling has dependency with
| |||||||||||||||||||||||||||||
| PNF / NetConf | Oskar Malm | Basic U/C unchanged, support for NetConf over TLS. What is being worked on in R6 is to have a improved functionality around certificate handling. When you have a TLS 1.x for authentication for ONAP so the NF when it connects to ONAP it is a valid xNF. Authenticate user cert ONAP needs to get the certs from somewhere - a centralized solution w/ AAF. and connect to ext. PKI via CMPv2. ONAP component minimum version TLS 1.2. Dependency to REQ-140 | ||||||||||||||||||||||||||||
| PNF / Plug and Play | Benjamin Cheung | held meeting for discussing Civic Address elements & Geolocation information w/ the modeling S/C PnP - PNFD/SDC AID/AAI Schema Modeling - Discussion Jan 2, 2020 Eventually will the PNFregistration VES event for PnP (R7). SO presentations related to Building block definitions. Dependency to REQ-140. Option #2 new arch. is agreed. Option #1 continue w/ old. Use Case Realization Call: February 19, 2020
| ||||||||||||||||||||||||||||
| R6 Use Case VS 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. | ||||||||||||||||||||||||||||
| 5G Service Modeling U/C | Benjamin Cheung | WIKI: 5G RAN SERVICE MODELING & DEFINITION in R6 Frankfurt CDS Data dictionary - Define attribute, in that entry tells you how to get that value. Yuriy Malakov If you needed the IP@ you can go that entry → points to the REST call. Used for instantiation and configuration management. Model driven ONAP. Modeling Concepts 3GPP TS28.541/TS28.540 - 5G NRM Network Resource Model analysis (spreadsheet). Looking parameters introduce Classify parameters - CDS Data Dictionary, A&AI, RunTime Cfg DB. Presentations - Modeling S/C, U/C S/C, U/C Realization, 5G U/C. Modeling S/C - Experimental info model introduced (standards driven) A&AI - classification of A&AI parameters. Commission (might need at installation & commissioning) → A&AI. Onboarding - Onboarding, PNF PNFregistration, CMNotify (VES events), Pre-defined "load 3GPP model" Information Flows - Where these might be used. ORAN Standards - Usage of the 3GPP TS28.541 in ORAN Standards. Might want to consider which 3GPP parameters ORAN cares about & when. They might an opinion of when to incorporate parameters. Presentation at Use Case Realization call Use Case Realization Call: January 29, 2020 - next step to present to Modeling S/C. | ||||||||||||||||||||||||||||
| CMPv2 Security (AAF enhancements) | Hampus Tjader | M2/M3 CMPv2 & AAF status - CMPv2 GREEN at M2/M3 right now.
| ||||||||||||||||||||||||||||
or not??) some things should move to the VNF-requirements project (many people made comments to that end). Requirements there are there need to follow conventional req language. Reach to TrevorSUPPORTING SLIDES
| Document | File |
|---|---|
| Presentation | |
RECORDING
| Recording | File | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| MP4 (Video + Audio) |
| ||||||||||||||||||
| Audio Only |
| ||||||||||||||||||
| M3U, Chat |
|
...