Use Case Overview & Description
The Configuration Persistence Service is a Common Data Layer Service providing database functionality to persist network element run-time information. CPS will perform key DB operations such as syncing data with xNFs. CPS enables OSS configuration, optimization and E2E LCM operations. It will be a new Platform Component in R8.
State Management DB (Bell) project is aimed at tracking states of network elements in a network.
Use Case Key Information
|Requirements Proposal||This is a link to the requirements proposal made on the Requirements Sub-committee||Honolulu release - functional requirements proposed list|
|Architecture S/C info||Information on the Architecture sub-committee presentation|
|Prior Project "Base" Wiki||Link to the "base" wiki for the Use Case, or work from a prior release.|
|Requirements Jira (REQ-###) Ticket||Link to the REQ Jira ticket for this use case|
|Key Use Case Leads & Contacts|
|Meetings Register & Recordings||Link to Use Case Team meetings.||Configuration Persistence Service Meeting Notes & Recordings|
|CPS team meetings 2021||Configuration Persistence Service Meeting Notes & Recordings 2021|
|Architectural Issues & Decisions||Issues decisions and assumptions|
This section describes Business Drivers needs. These business drivers are presented on the Requirements Sub-committee and should also be put into the release requirements sub-committee page.
EXECUTIVE SUMMARY - The 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.
|PROJECT||PTL||User Story / Epic||Requirement|
|End to End Network Slicing (Use Case)|
|OOF SON (PCI) Use Case|
List of PTLs:Approved Projects
*Each Requirement should be tracked by its own User Story in JIRA
Supporting files for R8 CPS
CPS slides for DDF
USE CASE DIAGRAM
Use cases define how different users interact with a system under design. Each use case represents an action that may be performed by a user (defined in UML as an Actor with a user persona).
Use Case Functional Definitions
Use Case Title
Configuration Persistence SERVICE
Actors (and System Components)
SDC, A&AI, C&PS, Use Cases (PCI, E2E NS, A1E, Mirror), DBMS, TSDB, xNF, DCAE, DMaaP
Configuration Persistence Service is a platform component that is designed to serve as a data repository for Run time data that needs to be persistent. It is characterized by the following.
DATA REPOSITORY - The types of data that is stored in the Run-Time data storage repository for:
DATA LAKE - Architecturally, the Configuration Persistence Service is designed to be a common services data layer which can serve as a data lake to other run time entities (ONAP components or external tools).
CPS FUNCTIONS - The Configuration Persistence Service enables functionality to be performed by other entities. It will ENABLE the capability of another components or external tools within/or external to ONAP to perform the functions.
Points of Contact
Code Contributors: (same as above)
DEPLOYMENT - The C&PS container/project is deployed and up and running.
AUTHENTICATION - Authentication is performed by C&PS to allow access and interaction with other ONAP platform components.
Triggers / Begins when
(See "Flow Step" for Design Time Activities, and Initial Database Setup below in the Steps/flows)
Steps / Flows (success)
Steps in Basic Operation and setup of C&PS.
SETUP OF C&PS - C&PS database is setup with initial schema
RUN-TIME OPERATION OF C&PS - the above run-time types of actions/operations (1) - (4A/B) above in the flow steps results in updates of C&PS or the interacting entity successfully retrieving information from C&PS DB.
Alternate / Exception Paths
The following describes error cases or conditions for each of the flow steps above:
Related Use Cases
These are associated use cases or requirements depending on CPS
Tools / References / Artifacts
- High visibility bugs
- Other issues for testing that should be seen at a summary level
- Where possible, always include JIRA links
End to End flow to be Tested
**This should be a summary level Sequence diagram done in Gliffy**
Test Cases and Status
|1||There should be a test case for each item in the sequence diagram|
NOT YET TESTED
|2||create additional requirements as needed for each discreet step|
|3||Test cases should cover entire Use Case|
|4||Test Cases should include enough detail for testing team to implement the test|