...
The roadmap for CPS and what will be delivered in the upcoming releases:
Updated C&PS ROADMAP
...
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) |
...
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 | Title of the Use CaseCONFIGURATION & PERSISTENCY SERVICE | ||||||||||||||||||||||||
Actors (and System Components) | SDC, A&AI, C&PS, Use Cases (PCI, E2E NS, A1E, Mirror), DBMS, TSDB, xNF, DCAE, DMaaP | ||||||||||||||||||||||||
Description | The list of Actors and System Components that participate in the Use Case | ||||||||||||||||||||||||
Description | Short overview of the Use Case | ||||||||||||||||||||||||
Points of Contact | Authors and maintainers of the Use Case. Use Case Lead, Key Use Case members and code contributors. | ||||||||||||||||||||||||
Preconditions | A list of conditions that are assumed to be true before the Use Case is invoked Includes description of Information Consumed | ||||||||||||||||||||||||
Triggers / Begins when | Describes the trigger for beginning the Use Case | ||||||||||||||||||||||||
Steps / Flows (success) | Describes the sequence of steps and interactions that occur during the Use Case (may include: description, data exchanges, functionality, state changes) Interaction diagrams may be included or referenced | ||||||||||||||||||||||||
Post-conditions | The expected results of the execution of the Use Case Includes description of Information Produced | ||||||||||||||||||||||||
Alternate / Exception Paths | Description of any exceptions or special process that could occur during Use Case | ||||||||||||||||||||||||
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
| Related Use Cases | List of the Use Cases referenced by this Use Case | ||||||||||||||||||||||
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 |
...