...
Ctgry | Item | Who | Notes | ||||||||||
Pltfm | PLATFORM TOPICS: Controller to NF Association | R5/R6 Topic 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 | STATUS: Work for RunTime DB completed, not merged in R4 Dan Timoney moved to R5, one Jira for RunTime DB. One issue about merging. ONAP code added can take a test ONAP deployment to have the ConfigDB work. USE CASE REALIZATION MEETING (Notes 2019-01-30) U/C Cross-Interaction, Persistency | |||||||||||
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 for Licensing Management Use case Wiki: LICENSING MANAGEMENT | |||||||||||
Use Cases | USE CASE/5G: OOF / SON | PoC U/C will happen in WinLab. To meet time lines do those parts in Windriver focusing on DCAE, Policy and OOF. Jira SDN-C (Dan Timoney) pushed El Alto (the Maintenance Release). | |||||||||||
Use Cases | USE CASES: BBS U/C Evolution | BBS Evolution - Slide set linked in R6 proposed U/C. List of proposals & functional requirements.
| |||||||||||
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, reconcile various information models to ONAP model: Expand & verify model and harmonize with the 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 that need transport models need some model consistency. - Try a Use Case with extended ONAP model & real equipment. | |||||||||||
Use Cases | 5G NRM (Network Resource Model) Configuration | yaoguang wang | Presented at the 2019 June LFN DDF, titled as '5G Provisioning management service to NRM' Presentation scheduled for Aug 8, 2019 | ||||||||||
Arch | Architecture S/C PNF POB/OB Flow | Arch S/C Information Flows: New Information flow for Preonboarding/Onboarding xNF packages/resources. | |||||||||||
Pltfm | A&AI | A&AI updates | |||||||||||
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 / M0 | Need the U/C teams to fill out the Dev. Impacts. More Generalized Use Case Template (discussed w/ Model team): | ||||||||||||
VID: Service Models Browser Orchestration | VID: Service Models browser - display orchestration type (macro / a`la carte) use-case. This use-case requires us to extend the AAI data-model, with an additional field, related to Service Model. This field will be used later on to indicate in VID the Service Model orchestration type. A&AI Epic 2594
|
DCAE USE CASE IMPACTS FOR R6
Frankfurt Release Requirements
...
Wiki Page: PNF PLUG and PLAY in R6 Frankfurt
Epic #4: Secure PnP (see next row in this table)
- CMPv2 for operator certificate enrollment for VES Collector to correctly handle pnfRegistration event.
Epic #5: Refactor Tests for DCAE-SDK DMaaP-Client
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
SUMMARY: DCAE Commits
...
CMPv2 being developed in REQ-140 which is the common work in AAF
There are then 3 other release requirements covering Use Cases that will use it: (1) Netconf U/C to enhancement w/ Certificate management; (2) enhnace Bulk PM, (3) Enhancing PnP & VES Collector
Also DCAE platform CMPv2 cert can be requested correctly and delivered to the micro-services.
Was discussed last week with Pawel (Nokia).
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
SUMMARY: Commit by DCAE
...
will use CMPv2 (see the CMPv2 Development row)
No additional DCAE impact.
...
No Impact. Modeling impact.
SUMMARY: No Impact
...
Wiki Page: 5G Bulk PM in Frankfurt/R6
Epic #1 PM control -
- DCAE impacts to addition of new PM Subscription Handler micro-service
- Any needed updates to PM Mapper mS to enable dynamic mapping of measurements that are part of active subscriptions (stretch goal)
Epic #2 Secure 5G Bulk PM
- CMPv2 for operator certificate enrollment for secure 5G Bulk PM.
OPEN QUESTIONS: Is there further discussion for flow/paths for the Use Case itself? update from AAI triggering updates to SO, SH. change to have new mS and rigger policy update to reconfigure the mS follow policy path flow. Talk, but need follow-ups. AAI I/F vs direct I/F adding new OTI component for R6. Still nee dto close on some open points.
(Spreadsheet/Use Case Team): Indicates impact
SUMMARY: Will nee some further discussion, need some updated flows and better understanding on the flows. Discussion with Oskar & Michela.
...
Wiki Page: FM META DATA & PM DICTIONARY in R6 Frankfurt
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
DCAEGEN2-1767 Epic
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
DCAEGEN2-1768 Story
Epic: Update PM Dictionary Schema to have one YAML document per measurement. All measurement YAML documents will be in the same PM Dictionary YAML file.
Story: VES Event Registration Spec updates to section 3.3 for PM Dictionary schema change.
No DCAE Impact. Marge Agrees. New Artifact & definition.
SUMMARY: Needs more discussion with Marge. May need to be update, Marge will sync Vijay & Damian.
...
Wiki Page: OOF (SON) in R5 El Alto, OOF (SON) in R6 Frankfurt
Epic#1 - OOF/SON Enhancements
Functionality enhancement to SON Handler MS
Will also USE the CM Notify (being introduced in VES update)
(Spreadsheet/Use Case Team): Indicates impact
SUMMARY: Needs Clarification
...
...
5G / RAN ORAN 3GPP Standards Harmonization
...
Wiki Page: MOBILITY STANDARDS HARMONIZATION WITH ONAP
Might have to delay. Enhancements expected from DCAE
(1) CM NOTIFICATION: Listen to CM notification (config change notification).
(2) 3GPP FAULT EVENT: how to support 3GPP fault. 3GPP fault as a separate domain; alignment with 3GPP.
(3) FILE READY - VES event, add a field for the type of file. Sub: data field collector. Can use existing fields to support this. Applicable to other types of file beyond the PM file (e.g. trace, log files) want it to be generic.
(Spreadsheet/Use Case Team): Indicates impact
Timeline - meeting held Oct 2 to align 3GPP fault event, converging on an approach; another meeting next week Oct 7+. Maybe difficult to achieve by M2/M3 (Nov 7 2019)
SUMMARY: (see CM Notify VES event)
...
CM notications are new impacting VES event registration & listener.
VES publications happen before components use it. VES updates need to happen before development. VES event reg & listener, FM dictionary. Modeling updates by M2. A finalized VES document might be difficult by Nov 7
IMPACTS: ORAN/ONAP Harmonization U/C, OOF/SON/PCI Use Case, and RunTime DB Use Case.
SUMMARY: DCAE commits, but wants to follow-through on the definition of the VES definitions. WARNING: M2/M3 deadline for M2/M3 Nov 7 2019. Collector change to accommodate VES
...
Wiki Page: 5G CONFIGURATION (RunTime DB)
Epic #1: Base RunTime DB Development
E1a. VES/DCAE pathway to provide configuration notification RunTime DB (see also the ORAN/ONAP harmonization U/C ROW ABOVE - CM O1 Notification). DCAE collectors needs a new domain for CM Notify. No additional impact expected to USE the CM Notify. RunTime DB SUBSCRIBES to the CM Notify Event.
E1b. VES Event Listener Document to be updated.
E1c. New VES Event domain (CM Notify) to be introduced (DCAE VES Listener)
(Direct invoke API).
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
SUMMARY: (impact captured in the CM notify VES impact)
...
Wiki Page: Scaling Use Case (Frankfurt)
Goal: Manual and Automatic Scale In
Scale In Trigger (Priority: 2)
Support creating a Threshold Alert (TA) when capacity needs to be reduced
Send the TA to Policy
No new functionality for scaling expected.
SUMMARY: Needs Investigation.
...
Wiki Page: MOBILE SERVICE CHAINING
We want close loop mechanism for service chaining operation
Policy Framework, DCAE, and Service Orchestration Project may be upgraded
SUMMARY: Need Investigation.
...
Wiki / PPT slide indicates no impact
(Spreadsheet/Use Case Team): Indicates impact
SUMMARY: No impact
...
Wiki Page: CCVPN Use Case in Frankfurt Release
(Spreadsheet/Use Case Team): Indicates impact
SUMMARY: Needs Investigation
...
Self Serve Control Loops - continuation from Dublin
PNF support in Control Loops - non-service Control Loops
Adding Policy Update and PEP (Policy Enforcement Point) registration with Policy for updates on Decision Policies
CLAMP would provide arbitrary blueprints to DCAE instead of SDC.
CL Event format standardization to VES
(Spreadsheet/Use Case Team): Indicates impact
SUMMARY: DCAE some things are committed. Separate requirements created.
...
Wiki Page: Multi-domain Optical Network Services
(Spreadsheet/Use Case Team): Indicates impact
SUMMARY: Needs Impact assessment.
...
Wiki Page: Change Management Frankfurt Extensions
(Spreadsheet/Use Case Team): No impact listed
SUMMARY: No impact.
...
SUMMARY: Needs investigation
...
Wiki Page: K8S based Cloud region support (Continue from R4)
(Spreadsheet/Use Case Team):
SUMMARY: Needs investigation
...
Wiki Page: Third-party Operational Domain Manager
...
KEY PRESENTATIONS & OVERVIEWS & RECORDINGS
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 S/C , Use Case Project Teams, Architecture S/C Way of Working | Model S/C (Sub committee) contributions page: | |
Jun 5, 2019 | Use Case slides for Dev. Forum | Use Case Realization Call: June 5, 2019 | |
July 10, 2019 | R6: PNF Software Upgrade Overview & Discussion | 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, Overview & Discussion | OOF / PCI / SON Use Case Demo | |
Aug 7, 2019 | 5G NRM (Network Resource Model) Configuration U/C Overview | yaoguang wang | 5G NRM (Network Resource Model) Configuration U/C Overview & Presentation |
Aug 14, 2019 | ORAN Standards Harmonization U/C Overview | ORAN Standards Harmonization U/C Overview & Presentation | |
Aug 21, 2019 | Modeling Sub-Committee guidelines & Use Case Interactions | Modeling S/C Process Wiki: Proposed ONAP Release Process Updates for Information and Data Modeling Use Case Tracking Template and Use Case Template R6 Modeling High Level Requirements Planning Page: ONAP R6 Modeling High Level Requirements | |
Sept 4, 2019 | Licensing Management Overview | Introduction of Licensing Management in R6 | |
Sept 11, 2019 | 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. |
Sept 18, 2019 | VID & R6 U/C Discuss Preparation for Technical Conference Antwerp | 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) |
Sept 25, 2019 | 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. | |
Oct 2, 2019 | DCAE & R6 Use Case Impacts Discussion | Vijay Venkatesh Kumar | Discussion with DCAE PTL (Vijay Kumar) for R6 Use Case Impacts discussion and commitments for DCAE impacting Use Cases |
Oct 9, 2019 | M1 U/C discussion | Use Case Teams | M1 Deadline (Oct 10 |
2019) | |||
Oct 16, 2019 | 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. |
x, 2019 | SO & R6 Use Case Impacts Discussion | Discussion with SO PTL (Seshu Kumar) for R6 Use Case Impacts discussion and commitments. | |
x, 2019 | 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? |
x, 2019 | RunTime DB Discussion | 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. | |||
x, 2019 | Discussion of Use Case Template for R7 | Filling out, describing and creating the Wiki for a Use Case | |
x, 2019 | 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 |
SUPPORTING DOCUMENTATION
Document | File | ||||||
---|---|---|---|---|---|---|---|
Use Case Impacts Spreadsheet |
| ||||||
...