...
| Ctgry | Item | Who | Notes |
Pltfm | PLATFORM TOPICS: Controller to NF Association | See Slides Nov 6, 2018. Development of Controller to NF assignment association S/W. CDS, VF-C, APP-C, SDN-R, SDN-C; will the CCSDK "merging" of controllers happen in R6? | |
| Pltfm | PLATFORM TOPICS: Data Persistency, RunTime DB | RunTime Config DB is now a R6 use case : USE CASE REALIZATION MEETING (Notes 2019-01-30) U/C Cross-Interaction, Persistency 5G CONFIGURATION (RunTime DB)CONFIGURATION PERSISTENCE SERVICE R6 | |
| Pltfm | PLATFORM TOPICS: Controller LCM API Evolution | Goals (Architecture Evolution)
Present at the Arch S/C Apr 9 (Tue) second presentation. | |
| Use Cases | USE CASE/5G: RAN (ORAN-3GPP) Standards harmonization with ONAP |
Use Case WIKI: MOBILITY STANDARDS HARMONIZATION WITH ONAP | |
| Use Cases | USE CASE/5G: Licensing Management | New U/C added to the 5G Use Cases Wiki: LICENSING MANAGEMENT (Oct 8 2019) Arch Samuli presented on Licensing Management. Modeling work: ONAP R6 Modeling High Level Requirements | |
| Use Cases | USE CASE/5G: OOF / SON / PCI | PoC for December 2019? SDN-R south-bound NetConf I/F w/ model and also integration with Runtime DB work. | |
| Use Cases | USE CASES: BBS U/C Evolution | BBS Evolution - Slide set linked in R6 proposed U/C. List of proposals & functional requirements.
https://wikilf-onap.onapatlassian.orgnet/wiki/download/attachments/6088750416362101/BBS_R5_v1.pptx?version=1&modificationDate=1554180715000&api=v2 | |
| Use Cases | USE CASES/5G: PM Dictionary/FM MD GUI | FM META DATA & PM DICTIONARY in R5 | |
| Use Cases | USE CASES/5G: PNF S/W Upgrade | PNF software upgrade in R6 Frankfurt | |
| Use Cases | USE CASES/5G: Preonboarding/Onboarding | PNF PREONBOARDING / ONBOARDING in R5 | |
| Use Cases | USE CASES: IoT Service Creation | IoT Create Services on 5G June 19, 2019 | |
| Use Cases | USE CASES: Modeling gNB/5G RAN | Align & harmonize information models to ONAP model and ONAP internal information & data model: ETSI SOL001 ... 007 with ONAP internal Model, PNFD modeling (Model S/C), 5G Model (3GPP, RAN), ORAN (WGs, RAN), Open ROADM (reconfig optical add/drop multiplexer, Optical), ONF (Optical), ISOMII (Optical), OTCC (Optical transport config & control) | |
| Use Cases | USE CASES: 5G NRM (Network Resource Model) Configuration | wangyaoguang | June 2019 LFN DDF, titled as '5G Provisioning management service to NRM' Presentation: 5G Network Resource Model (NRM) Configuration in R6 Frankfurt |
| Arch | Architecture S/C PNF POB/OB Flow | Arch S/C Information Flows: Draft ONAP Information Flows New Information flow for Preonboarding/Onboarding xNF packages/resources. | |
| TSC | TSC: PoC Definition | POC definition | |
| TSC | TSC/USE CASES: Test Automation Progress | Use Case Test Automation Action Items: Use case subcommittee to reach the Dublin use case owner to provide the following information. what's the current percentage of testing automation regarding your use case and functional requirements; what will be the plan to be 100% and constraints (resources availability etc.) | |
| R6 Frankfurt / M1 | Need the U/C teams to fill out the Dev. Impacts. More Generalized Use Case Template (discussed w/ Model team): | ||
...
| DATE | TOPIC | PRESENTER | DESCRIPTION |
| Apr 10, 2019 | Controller LCM API Evolution |
| |
| May 1, 2019 | A&AI GraphGraph Visualizer | Visualizer for A&AI Model Layout | |
| May 8, 2019 | A&AI Model Browser, Sparky | A&AI developer Model Browser to navigate and viewing attributes, object types & edge view Recording & Slides: Use Case Realization Call: May 8, 2019 | |
| May 15, 2019 | A&AI Run Time Browser (Sparky) | A&AI Run-Time Browser | |
| May 22, 2019 | Edge Automation Overview & Discussion | Central & Distributed Edge ONAP configuration. Topics include: Onboarding, Instantiation, Edge Orchestration, A&AI, Architecture, Work-flows, Multi-Tenancy | |
| May 29, 2019 | Modeling, Use Case & Arch S/C Way of Working | Model S/C (Sub committee) contributions page: Modeling sub-committee Contributions https://wikilf-onap.onapatlassian.orgnet/wiki/display/DW/Proposed+ONAP+Release+Process+Updates+for+Information+and+Data+Modeling | |
| Jun 5, 2019 | Use Case slides for Dev. Forum | Use Case Realization Call: June 5, 2019 | |
| July 10, 2019 | R6: PNF Software Upgrade | ONAP Read the Docs/R4 Announcements WIKI: PNF software upgrade in R6 Frankfurt Overview & Presentation | |
| July 24, 2019 | R6: OOF/SON PCI Use Case Demo | NK Shankar | OOF / PCI / SON Use Case Discussion and Overview |
| 5G NRM Configuration U/C Overview | wangyaoguang | 5G NRM (Network Resource Model) Configuration U/C Overview & Presentation |
| ORAN Standards Harmonization | ORAN Standards Harmonization U/C Overview & Presentation | |
| Modeling S/C guidelines & Use Case Interactions | Modeling S/C Process Wiki: Proposed ONAP Release Process Updates for Information and Data Modeling with Use Case Tracking Template and Use Case Template R6 Modeling Req Plan wiki: ONAP R6 Modeling High Level Requirements | |
| Licensing Management Overview | Introduction of Licensing Management in R6 | |
| SDC & R6 Use Case Impacts Discussion | Ofir Sonsino | Discussion with SDC PTL Ofir w/ the Use Case Teams and SDC commitments. See the summary Table for SDC impacting Use Cases. |
| VID & R6 U/C Discuss | Use Case Teams | Discussion with VID PTL (Ittay Stern) for R6 Use Case Impacts discussion and commitments for VID impacting Use Cases Preparing slides for Use Cases at the Technical Conference Antwerp (for 5G/PNF use cases) |
| A&AI & R6 Use Case Impacts Discussion | Discussion with A&AI PTL (Jimmy Forsyth) and Chandra Cinthala for R6 A&AI Use Case Impacts discussion and commitments. | |
| DCAE & R6 Use Case Impacts Discussion | Vijay Kumar | Discussion with DCAE PTL (Vijay Kumar) for R6 Use Case Impacts discussion and commitments for DCAE impacting Use Cases |
| M1 U/C discussion | Use Case Teams | R6 M1 Deadline (Oct 10 2019) M1 Checklist: Deliverables for Planning Milestone Checklist Template READ THE DOCS: http://onap.readthedocs.io/en/latest/guides/onap-developer/developing/index.html > USER GUIDES > Verified Use Cases and discussion with A&AI (James Forsyth ) continuing discussion from Sept 25. Network Slicing has two proposals in R6 (LIN MENG CMCC and Swaminathan Seetharaman ). Need to align the two proposals and present at Use Case S/C meeting (Alla G.) and TSC and Architecture next week Oct 14. |
| PoC Planning & Discussion | Tracy Van Brakle | Combination Plugfest & PoC 1st week of December bringing together subset of ONAP modules as SMO (svc mgmt orchestration) layer w/ other artifacts from ORAN S/W (LF). LF will publicize. Planned June 2020. Co-Demo discussion Nokia & Ericsson: Plug Fest Planning Discussion Oct 28, 2019 |
| RunTime Config DB (Data Persistency) | Discussion of the RunTime DB Use Case in R6 Frankfurt which introduces a Common Service Data Layer for a data lake to store configuration and operational parameters. Component & Flows: ARC RunTime DB Component Description - R6 Frankfurt ARCHCOM: InfoFlow - RunTime Config DB Information Flow5G CONFIGURATION (RunTime DB) | |
| OOF & R6 Use Case Impacts Discussion | Shankar PN | Discussion with OOF PTL (Shankaranarayanan Puzhavakath Narayanan ) for R6 Use Case Impacts discussion and technical details for OOF impacting Use Cases |
| SO & R6 Use Case Impacts Discussion | Discussion with SO PTL (Seshu Kumar) for R6 Use Case Impacts discussion and commitments. | |
| PoC Planning & Discussion | Tracy Van Brakle | Sync up on the Dec 5, 2019 ORAN/ONAP PlugFest & Demo |
| Network Slicing | CMCC-Huawei-Tencent & Wipro-ATT-Amdocs joint Network Slicing proposal | |
| No Meeting | No Meeting | |
| MDONS | Xin Miao (Unlicensed) | Presentation and discussion of Multi-domain Optical Network Services |
| Ctlr & R6 U/C Impacts | Dan Timoney | Discussion with Controller (APP-C, SDN-C) PTL (Dan Timoney) for R6 Use Case Impacts to Controller project. A technical discussion, Q&A, and U/C analysis. Recap of ONAP/ORAN Plugfest (Dec 5) |
| No Meeting | No Meeting | No meeting end of December due to Holidays & Vacations |
| |||
| M2/M3 Discussion | |||
| x, 2020 | Discussion of Use Case Template for R7 | Filling out, describing and creating the Wiki for a Use Case | |
| x, 2020 | Release Manager Discussion | David McBride | Discussion with David McBride of the Linux Foundation, the R6 Release Manager regarding practices, wiki page updates, Jira dashboard and what is a use case? Release development process moving waterfall > agile/sprint |
| x, 2020 | CC-SDK and E2E Automation | Yuriy Malakov | |
| Way of Working Process | Process for Modeling WoW and development with Architecture & Modeling. | ||
...
SDN-C USE CASE IMPACTS FOR R6
Frankfurt Release Requirements
Overview:
SDN-C, SDN-R, APP-C, VF-C, CC-SDK ... CC-SDK is the platform to build controllers.
...
| PNF / Preonboarding Onboarding | Wiki Page: PNF/VNF PREONBOARDING / ONBOARDING in R6 Frankfurt SUMMARY: No impact | ||||||||||||||||||||
| PNF / Plug and Play | Wiki Page: PNF PLUG and PLAY in R6 Frankfurt Frankfurt Release Requirements : - Use Case Spreadsheet: Indicates Impact WIKI: (Ericsson) Epic#1: Controller to PNF exchange (Epic) STEP 37 Epic #1:
See the Netconf communiation main Use Case. PnP defines the step 37; the actual work is in the NetConf Use Case SUMMARY: Controller to PNF (NetConf) communication Question: Will NetConf adaptor in CDS? Answer: in R4 there is a solution uses CDS as part of the post-inst. for PNF. The change in R6, to convert from python to coclin still using opendaylight as the open client. Dan: CDS has N/C built in as well push back that's not architecturally correct. Dan Timoney Netconf going through SDN controller so architecture S/C doesn't push back. if we took that out, then that would raise the question if CDS is another controller, but CDS is not a controller. | ||||||||||||||||||||
PNF / PNF Software Upgrade using direct Netconf/Yang interface with PNF | Wiki Page: PNF software upgrade in R6 Frankfurt Use Case Spreadsheet: Indicates Impact Frankfurt Release Requirements : Indicates Impact WIKI: Epic #1: PNF Software Upgrade.
SUMMARY: TEST ONLY Most of the impact "core" part of PNF S/W Upgrade is in SO. New APIs being developed. SO API. | ||||||||||||||||||||
PNF / Enable Schema Update once PNF software is updated | Wiki Page: PNF software upgrade in R6 Frankfurt - SUMMARY: No impact | ||||||||||||||||||||
PNF / Enhancement on PNF Software Upgrade with EM with Ansible | Wiki Page: PNF software upgrade in R6 Frankfurt Frankfurt Release Requirements : - WIKI:
Added by Huawei team to add ansible playbook for controller. Before only upgrade S/W API. split that into separate download activate APIs. SDN-C uses LCM API from CC-SDK. to support ansible path, which huawei uses need to go to CC-SDK to add new RPCs in the API for active & download S/W SUMMARY: -
| ||||||||||||||||||||
PNF / PNF Software Upgrade with EM with Netconf | Wiki Page: PNF software upgrade in R6 Frankfurt Frankfurt Release Requirements : Test only Impact SUMMARY: Test only | ||||||||||||||||||||
PNF / Configuration with NETCONF/ Secure Communication between xNFs and ONAP | Wiki Page: Configuration with NETCONF in Frankfurt/R6 WIKI: Improve support for deploying NETCONF/TLS client certificates into ODL netconf-keystore
SUMMARY: Deploying NetConf TLS certificates. Looking at adding a second option for certificate handling used by Netconf TLS in SDN-C. Option from initi container of SDN-C request second certificate from AAF using existing API every ONAP component would request a certificate to protect internal communication Border components SDNC want a dedicated cert. e.g xNF over TLS option to request 2nd cert. from AAF use it in opendaylight. Installs the cert into the NetConf keystore in ODL.
In OOM honor global flag to disable/enable AAF. if AAF is disabled, how is this handled? A: The fall back is a manual method to provide cert. via in a persistent volume. A previous procedure. Could a self-signed certificate be used? Usually service providers will have their own procedure for certificates and not necessarily using AAF. Thus, the manual method is important for other reasons from actual service provider scenarios & procedures for cert. management. | ||||||||||||||||||||
| 5G / 5G Service Modeling | Wiki Page: 5G RAN SERVICE MODELING & DEFINITION in R6 Frankfurt WIKI: Modeling work only SUMMARY: No impact | ||||||||||||||||||||
5G / Bulk PM / PM Control | Wiki Page: 5G Bulk PM in Frankfurt/R6 Frankfurt Release Requirements : No impact WIKI: No Code impact. Operation will use the controller. The flow expecting for PM control U/C. Policy will use the CDS API. Will have a customized blue-print to support it. SUMMARY: Test Only | ||||||||||||||||||||
| 5G / PM Dictionary | Wiki Page: FM META DATA & PM DICTIONARY in R6 Frankfurt SUMMARY: No Impact | ||||||||||||||||||||
| 5G / 5G FM Meta Data | Wiki Page: FM META DATA & PM DICTIONARY in R6 Frankfurt SUMMARY: No Impact | ||||||||||||||||||||
| 5G / OOF SON (PCI) | Wiki Page: OOF (SON) in R5 El Alto, OOF (SON) in R6 Frankfurt Use Case Spreadsheet: Indicates Impact WIKI: Epic#1 - OOF/SON Enhancements Enhance Yang model to align with 3GPP and O-RAN Configuration/Operational Database, Config History (e.g. to revert changes) RAN Simulator – enhance and include in ONAP codebase* Related O-RAN Jira: https://jira.o-ran-sc.org/secure/RapidBoard.jspa?rapidView=7&projectKey=OAM&view=detail&selectedIssue=OAM-9
SUMMARY: Development From Swaminathan Seetharaman Sandeep Shah 2 cases I am involved with - OOF SON use case - we expect some SDN-C impacts due to ORAN alignment and ConfigDB, our team (most likely Sandeep Shah) will contact Dan. | ||||||||||||||||||||
| 5G / E2E Network Slicing | Wiki Page: NETWORK SLICING PoC in R6 Frankfurt (Obsolete) Frankfurt Release Requirements : Indicates Impact Use Case Spreadsheet: Indicates Impact WIKI:
SUMMARY: New Development CONFIG DB - A new schema for Config DB. Needs to be available by M3 Swaminathan Seetharaman Sandeep Shah For Network Slicing use case, SDN-C impacts are not clarified for Frankfurt (it is not part of the approved scope, so it will be a stretch goal), we will contact Dan once details are worked out, so it can be a PoC for Frankfurt if we implement it after agreement with Dan. | ||||||||||||||||||||
5G / RAN ORAN 3GPP Standards Harmonization | Wiki Page: MOBILITY STANDARDS HARMONIZATION WITH ONAP WIKI: Epic #1 ORAN/3GPP & ONAP Harmonization A1 Interface
SUMMARY: Sandeep is working on CCSDK-1796, talking to Dan about Docker container. Working on A1 adaptor. getting A1 policy through DMaaP, converting that to an A1 compliant I/F to talk to RIC side. The introduction of the A1 adaptor is S/W. Sandeep working on DMaaP agent, and DG work flow. | ||||||||||||||||||||
5G / Runtime Config DB , Data Persistency U/C | Wiki Page: 5G CONFIGURATION (RunTime DB) Use Case Spreadsheet: Indicates Impact WIKI: E1a. Provide RunTime DB yang model to RunTime DB. E1a. SO + Controller pathway BACK to the PNF through Netconf to update RunTime DB. Incorporation of RunTime DB into CCSDK SUMMARY: Development Impact | ||||||||||||||||||||
| 5G / NRM CM w/ RESTful HTTPS | Wiki Page: 5G Network Resource Model (NRM) Configuration in R6 Frankfurt Frankfurt Release Requirements : Indicates Impact WIKI: No impact SUMMARY: No impact | ||||||||||||||||||||
| 5G / Licensing Management | Wiki Page: LICENSING MANAGEMENT SUMMARY: No Impact, Modeling & architecture work only for R6. | ||||||||||||||||||||
| SERVICE RESOLVER | Wiki Page: Service Resolver WIKI: SUMMARY: No impact | ||||||||||||||||||||
| SCALING | Wiki Page: Scaling Use Case (Frankfurt) Frankfurt Release Requirements: Indicates Impact Use Case Spreadsheet: Indicates Impact WIKI: (Test only)
SUMMARY: Test only | ||||||||||||||||||||
| Mobile Service Chaining & Service Selection | Wiki Page: MOBILE SERVICE CHAINING Use Case Spreadsheet: Indicates Impact WIKI: (Only slideware) SUMMARY: - | ||||||||||||||||||||
| BBS | Wiki Page: BBS Broadband Service Use Case (Frankfurt) Use Case Spreadsheet: No Impact WIKI: - ? SUMMARY: | ||||||||||||||||||||
| CCVPN | Wiki Page: CCVPN Use Case in Frankfurt Release Use Case Spreadsheet: Indicates Impact WIKI: ?? Frankfurt Release Requirements: - SUMMARY: - | ||||||||||||||||||||
| Control Loop | Wiki Page: Control Loop Sub Committee Frankfurt Release Planning Use Case Spreadsheet: Indicates Impact WIKI: Event based Common API for Control Loop Operations SUMMARY: - | ||||||||||||||||||||
| Multi Domain Optical Service L0/L1 Orchestration | Wiki Page: Multi-domain Optical Network Services Use Case Spreadsheet: Indicates Impact WIKI: Raghavan Subramanian Have done some prototyping in Dublin for adding new DGs to extract topology from external domain controllers and map them to A&AI schema. Will need additional work to integrate this with proposed CDS workflow in Future release.
SUMMARY: SDNC Impact for MDONS: | ||||||||||||||||||||
| CHANGE MANAGEMENT | Wiki Page: Change Management Frankfurt Extensions Use Case Spreadsheet: Impact WIKI: Extensions to APP-C , VNF-C for Ansible Protocol. Delivery of "vFW K8s Use Case" Integrated with CDS - modification in CDS required for K8s workflow support. Dedicate package for CDS only uses existing functionality - Test only. Change on K8S plugin multi-cloud side. Ansible server (part of CCSDK), the integration of ansible server of APP-C. Modify how it is used by APP-C. (Test only, no S/W impact for SDN-C/CCSDK) SUMMARY: | ||||||||||||||||||||
| HPA | Wiki Page: Continuation of HPA Frankfurt Release Requirements: ? WIKI: ? SUMMARY: ?. | ||||||||||||||||||||
| RUN TIME SECURITY | |||||||||||||||||||||
| K8S Based Cloud Region Support | Wiki Page: K8S based Cloud region support (Continue from R4) Use Case Spreadsheet: Indicates Impact Frankfurt Release Requirements : Indicates Test Only WIKI: ? SUMMARY: - ? | ||||||||||||||||||||
| DAaaS | Wiki Page: Distributed Analytics as a Service (Continuation from R4) Use Case Spreadsheet: ? WIKI: ? SUMMARY: - | ||||||||||||||||||||
| 3rd Party Operational Domain Manager | Wiki Page: Third-party Operational Domain Manager Use Case Spreadsheet: ? Frankfurt Release Requirements: ? WIKI: SUMMARY: - |
SUPPORTING DOCUMENTATION
...
| Recording | FILE | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Zoom Video & Audio (MP4) |
| ||||||||||||
| Audio Only (M4A) |
| ||||||||||||
| Playback (M3U) |
| ||||||||||||
| Chat (Txt) |
|