For R7 GuiLin release the Data Persistency Service
USE CASE KEY INFORMATION
Topic | Description | Wiki |
---|---|---|
Contacts | ||
Requirements Tracking | Project Management requirements Jira Ticket (clone++ of REQ-1) | |
OOF SON PCI for NFR | ||
Architecture Sub-committee Jira tracker | Link to Architecture Jira for Architecture sub-committee w/ presentation link | |
R7 Functional Requirements Page | Guilin release - functional requirements proposed list#Configuration&PersistencyServiceProject | |
Base Project Page | CONFIGURATION & PERSISTENCY SERVICE R6 | |
Meetings Register | Configuration & Persistency Service Meeting Notes & Recordings | |
PoC Jira REQ | Model Driven C&PS PoC | |
High Level Design PoC | Page for the High Level Design of the Model Driven C&PS PoC (R7) | High Level Design (PoC) |
High Level Design PoC | Issues decisions & assumptions for the C&PS PoC (R7) | Issues decisions and assumptions |
BUSINESS DRIVER
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.
ROADMAP
The roadmap for CPS and what will be delivered in the upcoming releases:
Updated C&PS ROADMAP
C&PS 1.0 - This is the evolution of ConfigDB in the CC-SDK / SDN-C. this solution was initially coded in R3 for the OOF/SON/PCI Use Case and was referred to as "ConfigDB" using a MariaDB ITDM solution. Because in R7 GuiLin planning, there is some clarity needed to identify the different tracks of development, the notation is introduced here, "C&PS 1.0" to allow people to have a common "language" to refer to a body of work. This was done in the R6 time frame.
C&PS 1.1 - This is the continuation of the C&PS 1.0 solution (see above). Updates will involve schema and interface changes for additional data supported in the C&PS database. This will be introduced in the R7 Guilin time frame. Thus, when someone refers to C&PS, in the R7 time frame they are referring to the C&PS 1.1 solution. Additionally, there are two C&PS related PoC going on the Model-Driven C&PS and State Management PoC (Bell Canada) and when referring to R7 C&PS, work done in these PoC are also included.
C&PS 2.0 - C&PS 2.0 is the stand-alone project. In R8 Honolulu, the goal is to have C&PS become its own stand-alone project. Thus, a presentation to the Architecture S/C and TSC will be made again to petition for a stand-alone project.
Updated Roadmap:
RELEASE | CONTENT | WIKI |
---|---|---|
R6 Frankfurt | CONFIGURATION & PERSISTENCY SERVICE | |
R7 Guilin | Store Real-Time Configuration Data Update Data Access Control | 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
PROJECT PROPOSAL | Target for R7 Guilin |
---|---|
DPS Project Proposal | Configuration Persistency Service Project Proposal (Oct 25 2019) |
COMPONENT DESCRIPTION | ARC RunTime DB Component Description - R6 Frankfurt |
ARCHITECTURE FLOWS | ARCHCOM: InfoFlow - RunTime Config DB Information Flow |
MEETINGS REGISTER | Configuration & Persistency Service Meeting Notes & Recordings |
DEVELOPMENT STATUS (R6 Extension)
PROJECT | PTL | User Story / Epic | Requirement |
A&AI | |||
AAF | No Active PTL | ||
APPC | |||
CLAMP | |||
CC-SDK (incl. CDS) | Epic #1 - OOF SON PCI U/C
Epic #2 - E2E Network Slicing | ||
DCAE | |||
DMaaP | |||
External API | |||
MODELING | |||
Multi-VIM / Cloud | |||
OOF | |||
POLICY | |||
PORTAL | |||
SDN-C | |||
SDC | |||
SO | |||
VID | |||
VNFRQTS | |||
VNF-SDK |
DEVELOPMENT STATUS (R7 as New Project)
PROJECT | PTL | User Story / Epic | Requirement |
A&AI | |||
AAF | No Active PTL | ||
APPC | |||
CLAMP | |||
CC-SDK (incl. CDS) | |||
DCAE | |||
DMaaP | |||
External API | |||
MODELING | |||
Multi-VIM / Cloud | |||
OOF | |||
POLICY | |||
PORTAL | |||
SDN-C | |||
SDC | |||
SO | |||
VID | |||
VNFRQTS | |||
VNF-SDK |
List of PTLs:Approved Projects
*Each Requirement should be tracked by its own User Story in JIRA
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).
The R7 Model Driven C&PS PoC diagram:
Use Case Functional Definitions
Use Case Title | CONFIGURATION & PERSISTENCY SERVICE | ||||||||||||||||||||||||
Actors (and System Components) | SDC, A&AI, C&PS, Use Cases (PCI, E2E NS, A1E, Mirror), DBMS, TSDB, xNF, DCAE, DMaaP | ||||||||||||||||||||||||
Description | Configuration & Persistency 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 & Persistency 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). C&PS FUNCTIONS - The Configuration & Persistency 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 | Use Case Lead: Benjamin Cheung Tony Finnerty Joanne Liu Rudel Key Use Case Members: Toine Siebelink user-4e793 theodore johnson Code Contributors: (same as above) | ||||||||||||||||||||||||
Preconditions | 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.
| ||||||||||||||||||||||||
Post-conditions | 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) - (4) 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 C&PS
| ||||||||||||||||||||||||
Assumptions | Describes any assumptions that are made for this use case | ||||||||||||||||||||||||
Tools / References / Artifacts | List of any tools or reference material associated with this Use Case as well as any JIRA trace-ability. List of any associated diagrams or modelling artifacts associated with the Use Case |
Weekly Meetings - Recordings & Discussion Log
Link to the team's weekly discussion, attendees & Recordings
Configuration & Persistency Service Meeting Notes & Recordings
SUPPORTING FILES
ITEM | DESCRIPTION | FILE |
---|---|---|
Project Proposal Presentation | TSC Project presentation Present at TSC | |
Project Proposal Presentation | Answers discussion updates ( Version) | |
C&PS Model Driven PoC (Ericsson) | PoC demonstrating Model Driven management using C&PS database | |
State DB (Bell Canada) PoC | Bell Canada Leading a PoC related to State management using the C&PS project. | |
Time series database mgmt | Time series database mgmt Presented by theodore johnson | |
VIRTUAL DDF Presentations | C&PS Overview Presentation | |
VIRTUAL DDF Presentations | Model-Driven C&PS PoC Presentation | |
C&PS PoC Architecture Options | C&PS PoC Architecture Options | |
C&PS V-DDF C&PS Overview | C&PS Overview Update | |
Testing
Current Status
Testing Blockers
- 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 | COMPLETE |
3 | Test cases should cover entire Use Case | PARTIALLY COMPLETE |
4 | Test Cases should include enough detail for testing team to implement the test | FAILED |