Use Case Realization Call: September 25, 2019
Date
Sep 25, 2019
Attendees
@Benjamin Cheung
@Chandra Cinthala
@Rebecca Lantz (Ericsson)
@Tracy Van Brakle
@Giulio Graziani
@James Forsyth
@Joanne Liu Rudel
@Zu Qiang
@Albino Pinho
@Gerard Hynes
@Chris Rapposelli-Manzo
DISCUSSION ITEMS LOG
Ctgry | Item | Who | Notes |
Pltfm
| PLATFORM TOPICS: Controller to NF Association | @Benjamin Cheung | 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 | @N.K. Shankaranarayanan @Joanne Liu Rudel @Benjamin Cheung | 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 | @Oskar Malm | 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 | @marge.hillis @Vimal Begwani @fred feisullin |
Use Case WIKI: MOBILITY STANDARDS HARMONIZATION WITH ONAP |
Use Cases | USE CASE/5G: Licensing Management | @Timo Perala @Samuli Kuusela | New U/C added to the 5G Use Cases for Licensing Management Use case Wiki: LICENSING MANAGEMENT |
Use Cases | USE CASE/5G: OOF / SON | @N.K. Shankaranarayanan | 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 | @David Perez Caparros @Tim Carey @Chaker Al-Hakim | 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 | @marge.hillis | |
Use Cases | USE CASES/5G: PNF S/W Upgrade | @Zu Qiang @wangyaoguang | |
Use Cases | USE CASES/5G: Preonboarding/Onboarding | @Benjamin Cheung @Zu Qiang @Michela Bevilacqua [Ericsson] | |
Use Cases | USE CASES: IoT Service Creation | @Atul Purohit | IoT Create Services on 5G June 19, 2019 |
Use Cases | USE CASES: Modeling gNB/5G RAN | @Thinh Nguyenphu (Unlicensed) @Benjamin Cheung Melanie Sater @Tracy Van Brakle @Martin Skorupski | 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 | @wangyaoguang | 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 | @Benjamin Cheung | Arch S/C Information Flows: New Information flow for Preonboarding/Onboarding xNF packages/resources. |
Pltfm | A&AI | @James Forsyth | A&AI updates |
TSC | TSC: PoC Definition | @Benjamin Cheung @Alla.Goldner | |
TSC | TSC/USE CASES: Test Automation Progress | @Benjamin Cheung @Alla.Goldner | 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 | @James Forsyth @Former user (Deleted) | 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 https://lf-onap.atlassian.net/browse/AAI-2594 |
|
|
|
|
A&AI USE CASE IMPACTS FOR R6
USE CASE | IMPACTS |
|---|---|
PNF / Preonboarding Onboarding | No Impact |
PNF / Plug and Play | Wiki Page: PNF PLUG and PLAY in R6 Frankfurt Modeling Impact with A&AI for Geo-Location modeling with RFC6225 Lat/Long/Alt into Complex Object. Discussion: Complex object has been deprecated, migration. Relationship from Complex to other objects. A lot of things already use the Complex object - so this would be a lot of impact. If you take the location bits of the Complex and then add a relationship to the PLACE object. In R6 only modeling work will be done. If the place becomes an object. ETSI LOCATION INFO. If it was additions to the Complex Object it would be ok. SUMMARY: No S/W A&AI Impact in R6 |
PNF / Software Upgrade | No Impact |
PNF / Configuration with NetConf | No Impact |
5G / 5G Service Modeling | Modeling a 5G Service may require expansion of A&AI fields for PNF. @Benjamin Cheung looking at 3GPP TS28.540 and 3GPP TS28.541 model & network resource model (NRM) will analyze the model and present to Modeling Subcommittee & 5G U/C subcommittee ... possibly A&AI schema impacting? SUMMARY: No S/W A&AI impact in R6 only Modeling work in R6. |
5G / Bulk PM | Wiki Page: 5G Bulk PM in Frankfurt/R6 Ensure A&AI can generate necessary events related to xNF instantiation and removal SUMMARY: Needs investigation. @Mark Scott |
5G / PM Dictionary | No Impact |
5G / 5G Meta Data | No Impact |
5G / OOF SON (PCI) | Wiki Page: OOF (SON) in R5 El Alto, OOF (SON) in R6 Frankfurt OOF/SON/PCI Enhancements. Models & relationship between Config, Operational DB & AAI (Spreadsheet/Use Case Team): Cell Addition Management. (Oct 10 2019 discussion): Cross dependency with RunTime DB Use Case. Add info into PNFName & PNFID in A&AI. Will this just be "usage" of A&AI or will there be additional schema changes or A&AI code changes or is this just Test Only? Reuse of Existing Objects. New objects related automatically flow to A&AI event topic on DMaaP. Where is the topic & Payload. CONTACTS: @N.K. Shankaranarayanan , @Swaminathan Seetharaman SUMMARY: (Oct 10, 2019) No A&AI schema change or A&AI code change for R6. CLOSED |
5G / E2E Network Slicing | Wiki Page: NETWORK SLICING PoC in R6 Frankfurt (Obsolete) Update A&AI schema with Network Slicing model. Merged proposal presentation (CMCC & AmDocs) have been given at Architecture S/C ( Oct 29, 2019 ) and at Alla's call Oct 28, 2019 UPDATE: Oct 30, 2019 : For the E2E Network Slicing use case for Frankfurt Release, we intend to leverage the nested service model work that has been going on since Dublin release. From A&AI perspective, we foresee that the schemas would have to be enhanced to cover network slicing models. We have considered A&AI to be a stretch goal for Frankfurt, though we are committing resources. So, we would like to start the discussion in the coming weeks, and subsequently implementation work to try our best to complete the implementation for Frankfurt. AAI-2600 has been created just to indicate the SDC impacts, we will update it with more details, and also join the A&AI weekly call during the next 1-2 weeks to discuss further. It is also noted in the release requirements page as A&AI: Code Change. Frankfurt Release Requirements SUMMARY: Tracked by A&AI 2600. Presentation: Use Case Realization Call: November 20, 2019 |
5G / RAN ORAN 3GPP Standards Harmonization | No Impact |
5G / Runtime Config DB | Wiki Page: CONFIGURATION PERSISTENCE SERVICE R6 Epic #1 Run Time DB introduction E1: INITIAL SETUP - A&AI Provides initial physical inventory info to RunTimeDB. Initial setup of physical inventory (PNFs) and initial configuration of RunTime DB should sync with A&AI. GetAllPNFs function from A&AI on startup. This function allows you to query for all of the elements currently in A&AI. This Get (all PNFs) API (Direct API call to A&AI). If there is a very large network, paging support (to get a set at a time). Produce an export of database (as a 1-time process). Epic #2 Run Time DB Sync E2: xNF OBJECT UPDATES - When a new xNF appears in the system, the RunTime DB needs to update its records to reflect the newly appearing or disappearing xNF. In theory A&AI posts a DMaaP notification that there is a change in xNF status and RunTime DB S/W subscribes to this topic and can update its records / database. Need to verify discuss with A&AI. Discussion: No A&AI Jira ticket needed. To use the system properly: get credentials for AAF. Maybe onboarding from SDC. When you onboard the config changes to allow for a certain MAC id. This is all in AAF. on AAI side include them in AAI roles / traversal & resources. Bootstrap data in AAF to be updated. necessary to interact with any component; getting credentials into AAF is for general use across the systems. SUMMARY: No A&AI S/W Impact. @James Forsyth Oct 9, 2019 (CLOSED) Find some documentation on A&AI usage. Oct 30, 2019 Jimmy preparing the document. Met with the team: RunTime Config DB Meeting notes Nov 1, 2019 @Joanne Liu Rudel Oct 9, 2019 ACTION: will call a meeting to discussion with A&AI team. Ben has setup regular "team" meetings for this U/C. Fridays at 9 AM https://zoom.us/j/230322363 |
5G / NRM CM w/ RESTful HTTPS | No Impact |
5G / Licensing Management | No Impact. Modeling & architecture work for R6. |
SERVICE RESOLVER | Frankfurt Release Requirements: Listed as A&AI TEST ONLY SUMMARY: A&AI Test only |
SCALING | No Impact?? (Wiki lists nothing) SUMMARY: A&AI Test only |
Mobile Service Chaining & Service Selection | No Impact?? (Wiki lists nothing) |
BBS | PNF State Transition management for BBS, description: https://lf-onap.atlassian.net/wiki/download/attachments/16362101/BBS_R5_v1.pptx?version=1&modificationDate=1554180715000&api=v2 State Transition Diagram (Working Draft) (Spreadsheet/Use Case Team): Indicates impact Update Oct 30, 2019 Did not foresee requirement, but needs to review first. We are currently reviewing the list of items we found in the BBWF BBS testing and once we sort through them we will communicate the results back to ONAP community. Regarding AAI specifically, we do not foresee any new requirements for Frankfurt, but we would like to conclude the review first before jumping to final conclusions. @Stavros Kanarakis SUMMARY: Needs investigation (See update) |
CCVPN | A&AI Schema changes
CCVPN Use Case in Frankfurt Release SUMMARY: Needs Investigate (Huawei) |
Control Loop | No Impact |
Multi Domain Optical Service L0/L1 Orchestration | Have done some prototyping in to ingest topology from external controllers and show them in A&AI. Will need more work to act on notifications from controllers and keep the topology in sync. Wiki: Multi-domain Optical Network Services
(Spreadsheet/Use Case Team): Indicates impact SUMMARY: Needs investigation of AAI-2623 (Epic). Resource models changing. It will be A&AI schema changes only, no A&AI S/W impact. https://lf-onap.atlassian.net/browse/AAI-2683(Epic); https://lf-onap.atlassian.net/browse/AAI-2623 (Modeling change) ; According to @Srinivasan Ramanathan he will be contributing a new custom query and schema changes |
CHANGE MANAGEMENT | No Impact (Confirmed) Wiki: Change Management Frankfurt Extensions (Spreadsheet/Use Case Team): Indicates impact; CHANGED to No Impact @Chris Rapposelli-Manzo SUMMARY: No A&AI Impact |
HPA | Extending HPA for K8S, Wiki Page: Continuation of HPA Base line: NFD (Node feature discovery) from K8S CNCF project. Discovery of hardware features, creation of profiles and populating in A&AI of compute flavors. From the Frankfurt Release Requirements page it lists as Test-Only and supported (tested) by Intel. |