Description
5G RAN physical/logical topology information (SDN-R) Core & RAN elements. 5G Configuration, provisioning of a 5G Network. SDN-R should contain the 5G Network Topology. CM Audit. CM Mediation. CM run-time storage / data persistency (MariaDB)
- it was decided that the RunTime Config DB will be part of CCSDK in R6. The new project proposal as RunTime Config DB will be for R7, but it is being worked on in the R6 timeframe.
| Topic | Wiki Link |
|---|---|
| PROJECT PROPOSAL | Configuration Persistency Service Project Proposal (Oct 25 2019) Target for R7 Guilin |
| (All Project Proposals) | Proposed Projects |
| COMPONENT DESCRIPTION | ARC RunTime DB Component Description - R6 Frankfurt |
| ARCHITECTURE FLOWS | ARCHCOM: InfoFlow - RunTime Config DB Information Flow |
BUSINESS DRIVER
This section describes Business Drivers needs.
Executive Summary - 5G RAN physical/logical topology information (SDN-R) Core & RAN elements. 5G Configuration, provisioning of a 5G Network. SDN-R should contain the 5G Network Topology. CM Audit. CM Mediation. CM run-time storage / data persistency (MariaDB). Configuration Management is a major LCM/OAM function with many operations. This use case will be a multi-release effort.
- Data Persistency - Storage of run-Time data storage. A configuration database (such as Maria DB) for data persistency and access to configuration information.
Business Impact - The ability to configure a RAN network (CU/DU) PNF and VNF with ONAP is a critical business function because configuration management is a core LCM/OAM operation.
Business Markets - This use case applies to any domain (wireless, transport, optical, wireline) that ONAP will manage. It is not a market specific function.
Funding/Financial Impacts - This use case represents a large potential OPEX savings for operators because of the ability to configure networks saving time and expenses.
Organization Mgmt, Sales Strategies - There is no additional organizational management or sales strategies for this use case outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.
Other CM Topics (future releases)
- CM Audit - Auditing configuration parameters for consistency, accuracy.
- CM Mediation - Configuration functions to correct and mediate settings.
- Data Persistency - Storage of run-Time data storage. A configuration database (such as Maria DB) for data persistency and access to configuration information.
- Topology Management - the configuration and view of a RAN network topology.
- Standardizing - Harmonizing management between vendors, and alignment to standards bodies such as 3GPP for CM topics.
- Golden Standard - Managing CM with Golden "Templates" and base-lined parameters.
DEVELOPMENT IMPACTS
The REQ (requirements) epic for this Use Case is
REQ-267 - Getting issue details... STATUS
NOTE: 1. Collect Configuration data via Netconf with VES CM notify notification.descoped from R6
2. Support all vendor specific Configuration Information Model ( CIM/Yang) descoped from R6
| PROJECT | PTL | User Story / Epic | Requirement |
| A&AI | Epic #1: Base RunTime DB Development | E1: A&AI Provides initial physical inventory info to ConfigDB | |
| AAF | |||
| APPC | |||
| CLAMP | |||
| CC-SDK (Controller) | Epic #1: Base RunTime DB Development | E1a. Provide RunTime DB yang model to RunTime DB. | |
| DCAE | Epic #1: Base RunTime DB Development | E1a. VES/DCAE pathway to provide configuration notification RunTime DB E1b. VES Event Listener Document to be updated. E1c. New VES Event domain (CM Notify) to be introduced (DCAE VES Listener) DCAEGEN2-1769 - Getting issue details... STATUS | |
| DMaaP | Epic #1: Base RunTime DB Development | E1a. VES/DCAE pathway to provide configuration notification RunTime DB | |
| External API | |||
| MODELING | Epic #1: Base RunTime DB Development | E1a. Design-Time modeling; Platform ONAP Model for RunTime DB to build initial structure. Use of onboarded Yang model (in vendor PNF package). | |
Multi-VIM / Cloud | |||
| OOF | Shankaranarayanan Puzhavakath Narayanan | ||
| POLICY | |||
| PORTAL | |||
| Controller | Epic #1: Base RunTime DB Development SDN-R and Controller Impact | E1a. Provide RunTime DB yang model to RunTime DB. E1a. SO + Controller pathway BACK to the PNF through Netconf to update RunTime DB. | |
| SDC | |||
| SO | |||
| VID | |||
| VNFRQTS | |||
| VNF-SDK | |||
| CDS |
List of PTLs:Approved Projects
ARCHITECTURE DISCUSSION
The architecture discussion held on Sept 10, 2019 and Sept 3, 2019 centered around the discussion about where the RunTime DB should architecturally live.
some choices are: (1) have RunTime DB as a platform component (2) have it was a part of a controller (3) have it as part of the common services (4) have it as part of CC-SDK (as part of common services).
See the supporting files which has the slides & discussion notes
The WIKI page for ARC RunTime DB Component is at:
ARC RunTime DB Component Description - R6 Frankfurt
MEETINGS
-
SUPPORTING FILES:
| Document | Files |
|---|---|
| Run Time DB Overview and presentation | |
| Run Time DB Architecture Presentation (Made to Arch S/C) with discussion | |
| Data Persistency Service |
INTEGRATION & TESTING
This section discusses the Testing & Integration for R6 PnP
- WHO IS TESTING - what company, team, and people will be doing the testing & responsibilities for testing.
- TEST ENVIRONMENT - which does the lab & test environment.
- RESOURCES NEEDED - what resources are needed.
- WHO IS CONTRIBUTING RESOURCES - what resources will be provided and by whom/what company.
- NETWORK CONNECTIVITY - Network connectivity
- TEST/INTEGRATION LEADER - Sandeep Shah , Dongho Kim
- INTEGRATION LEAD DEFINITION - ONAP "Use Case/Requirement" Integration Lead
RunTime Config DB Integration Test Cases. These can be navigated to from the Integration team page hierarchy.