...
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 | ||||||||||||||||||||
5G / PM Dictionary | No Impact | ||||||||||||||||||||
| |||||||||||||||||||||
5G / PM Dictionary | No Impact | ||||||||||||||||||||
5G / 5G 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 SUMMARY: Needs investigation | ||||||||||||||||||||
5G / E2E Network Slicing | Wiki Page: NETWORK SLICING in R6 Frankfurt Update A&AI schema with Network Slicing model
SUMMARY: Needs investigation | ||||||||||||||||||||
5G / RAN ORAN 3GPP Standards Harmonization | No Impact | ||||||||||||||||||||
5G / Runtime DB | Wiki Page: 5G CONFIGURATION (RunTime DB) 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. | ||||||||||||||||||||
5G / NRM CM w/ RESTful HTTPS | No Impact | ||||||||||||||||||||
5G / Licensing Management | No Impact. Modeling & architecture work for R6. | ||||||||||||||||||||
SERVICE RESOLVER | No Impact?? (Wiki lists nothing) | ||||||||||||||||||||
SCALING | No Impact?? (Wiki lists nothing) | ||||||||||||||||||||
Mobile Service Chaining & Service Selection | No Impact?? (Wiki lists nothing) | ||||||||||||||||||||
. (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 ( ) and at Alla's call UPDATE: : 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.
| ||||||||||||||||||||
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://wiki.onap.org/download/attachments/60887504/BBS_R5_v1.pptx?version=1&modificationDate=1554180715000&api=v2 State Transition Diagram (Working Draft) (Spreadsheet/Use Case Team): Indicates impact Update 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.
According to Srinivasan Ramanathan he will be contributing a new custom query and schema changes | ||||||||||||||||||||
CHANGE MANAGEMENT | BBS | No Impact (Confirmed) | (Spreadsheet/Use Case Team): Indicates impact | ||||||||||||||||||
CCVPN | No Impact?? (Wiki lists nothing) | ||||||||||||||||||||
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 | ||||||||||||||||||||
CHANGE MANAGEMENT | No Impact (Confirmed) Wiki: Change Management Frankfurt Extensions (Spreadsheet/Use Case Team): Indicates impact; CHANGED to No Impact SUMMARY: No A&AI 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. SUMMARY: Needs investigation. (No responses as of Oct 30).
| 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. SUMMARY: Needs investigation | ||||||||||||||||||
RUN TIME SECURITY | No Impact?? (Wiki lists nothing) | ||||||||||||||||||||
K8S Based Cloud Region Support | Wiki Page: K8S based Cloud region support (Continue from R4) Does this impact A&AI? Continuous monitoring (using Kubernetes APIs) and updating the DB with latest status and resources allocated. (Spreadsheet/Use Case Team): Indicates impact SUMMARY: TEST ONLY (Confirmed) Does this impact A&AI? Continuous monitoring (using Kubernetes APIs) and updating the DB with latest status and resources allocated. (Spreadsheet/Use Case Team): Indicates impact SUMMARY: Needs investigation. Assessment - Likely to use A&AI API not a code change. No Impact to A&AI discussed Jira Ticket AAI-2673 will be closed.
| ||||||||||||||||||||
DAaaS | No Impact?? (Wiki lists nothing) | ||||||||||||||||||||
3rd Party Operational Domain Manager | A&AI Impact analysis underway via PoC see Wiki Page: Third-party Operational Domain Manager Gets CFS instance from SO and RFS instance update from 3rd party. (Spreadsheet/Use Case Team): Indicates Test only impact SUMMARY: Confirm Test Only. Atif Husain no A&AI impact. Storing service instance details, reuse service instance object. No Schema change. CLOSE AAI-2674
|
KEY PRESENTATIONS & OVERVIEWS & RECORDINGS
...