You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »


For R7 GuiLin release the Data Persistency Service

To link to R6 C&PS: CONFIGURATION & PERSISTENCY SERVICE R6

BUSINESS DRIVER

EXECUTIVE SUMMARY - The RunTime Configuration Database / Data Persistency Service is a new platform component that is designed to serve as a data repository for Run-time data that needs to be persistent. As a stand-alone ONAP component, this project provides data layer services to other ONAP platform components and use cases that require persistent configuration or operational data. The R6 development will be enhanced as well.      

BUSINESS IMPACT - The ability for service operators to visualize and manage data in a RAN network (PNFs, VNFs, and logical constructs) with ONAP is a critical business function because they are key Life Cycle Management (LCM) and OA&M operations. The project has business impacts to enhance the operation of data-handling within ONAP by providing efficient data layer services.

BUSINESS MARKETS - This project applies to any domain (wireless, transport, optical, and wireline) that ONAP may manage. It is not a market or geographical specific capability. It is expected that scaled ONAP installations such as Edge & Core ONAP deployments will also deploy the database across each installation.

FUNDING/FINANCIAL IMPACTS - This project represents a large potential Operating Expense (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.


ROADMAP

The roadmap for CPS and what will be delivered in the upcoming releases:


RELEASECONTENTWIKI
R6 Frankfurt
CONFIGURATION & PERSISTENCY SERVICE
R7 Guilin

Store Real-Time Configuration Data

Update Data

Access Control

Guilin release - functional requirements proposed list#RunTimeConfigurationDatabase/DataPersistencyServiceProject

Management framework (not mgmt policy to run network, ONAP mgmt policy)

Network Elements (config info, policy for NE, A1 for NE)

R8 Honolulu

Data Recovery

Model Adaptation (Dynamic Schema)


R-Future

Data Auditing

Topology Traversal

Data History

Roll-Back

Data Syncing

Performance Optimization (Scaling)


PROPOSALS

  • No labels