Overview

Scope

What is this release trying to address?

Further integrate CPS into ONAP architecture through additional components and interfaces such as

• Network CM Proxy NCMP, moving from MVP to integrated component using SDN-C, DMaap and A&AI and an agreed new REST interface
• ONAP Data Model Inventory (DMI) Plugin to register supported CM handles and delegate data acces to the xNFS using ODL interface in SDN-C
• Model and Data Sync for nodes in DMI Plugin Inventory
• Storing and querying Temporal data

Requirements

• REQ-717 - Getting issue details... STATUS
• REQ-720 - Getting issue details... STATUS
• REQ-721 - Getting issue details... STATUS

Minimum Viable Product

• Ability to add xNF (initial) inventory using 'side-door' interface
• Read Operation support for both cached data in CPS and xNF data using 'datastores' concept
• Write operation support for datastore ncmp-datastores:running
• Model and Data Sync for (manually added) Simulator based xNF
• Temporal ?

Functionalities

Epics

CPS-350 - Getting issue details... STATUS

CPS-384 - Getting issue details... STATUS

CPS-385 - Getting issue details... STATUS

CPS-388 - Getting issue details... STATUS

CPS-386 - Getting issue details... STATUS

CPS-382 - Getting issue details... STATUS

CPS-369 - Getting issue details... STATUS

CPS-370 - Getting issue details... STATUS

CPS-446 - Getting issue details... STATUS

Stories

Longer term roadmap

• CPS-Core will have extended query capabilities based on XPath expression.
• CPS-Core will enforce and control ownership of data it holds
• NCMP will be able to sync CM Models and Data on any xNF in the network
• MCMP wil support the same query capabilities as CPS-Core and be extend with options similar to RESTConf's 'fields' and 'depth'
• Temporal DB?

Release Deliverables

Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note, etc) of this release.

onap/cps-and-ncmp

Sub-Components

• CPS-Core
  • cps-service
  • cps-rest
  • cps-ri (reference implementation)
• NCMP
  • cps-ncmp-service
  • cps-ncmp-rest
• Temporal DB
• DMI-Plugin

Architecture

High level architecture diagram

CPS is a new shared service in the ONAP Architecture:

For more detailed component description see ARC Configuration Persistence Service (CPS) Component Description - Istanbul-R9#6.SystemDeploymentArchitecture

Platform Maturity

Please fill out the centralized wiki page: Frankfurt Release Platform Maturity

• API Incoming Dependencies

No Incoming API changes required

• API Outgoing Dependencies

API this project is delivering to other projects.

• Third Party Products Dependencies

Third Party Products mean products that are mandatory to provide services for your components. 

In case there are specific dependencies  (Centos 7 vs Ubuntu 16. Etc.) list them as well.

• Testing and Integration Plans

Provide a description of the testing activities (unit test, functional test, automation,...) that will be performed by the team within the scope of this release.

Describe the plan to integrate and test the release deliverables within the overall ONAP system.
Confirm that resources have been allocated to perform such activities.

• Gaps

This section is used to document a limitation on a functionality or platform support. We are currently aware of this limitation and it will be delivered in a future Release.
List identified release gaps (if any), and its impact.

• Known Defects and Issues

Please refer to Frankfurt Defect Status

• Risks

List the risks identified for this release along with the plan to prevent the risk to occur (mitigation) and the plan of action in the case the risk would materialized (contingency).

Please update any risk on the centralized wiki page - Frankfurt Risks

• Resources

Fill out the Resources Committed to the Release centralized page.

• Release Milestone

The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.

• Team Internal Milestone

This section is optional and may be used to document internal milestones within a project team or multiple project teams. For instance, in the case the team has made agreement with other team to deliver some artifacts on a certain date that are not in the release milestone, it is erecommended to provide these agreements and dates in this section.

It is not expected to have a detailed project plan.

• Documentation, Training

Please update the following centralized wiki: Frankfurt Documentation

That includes

• Team contributions to the specific document related to he project (Config guide, installation guide...).
• Team contributions to the overall Release Documentation and training asset
• High level list of documentation, training and tutorials necessary to understand the release capabilities, configuration and operation.
• Documentation includes items such as:
  • Installation instructions
  • Configuration instructions
  • Developer guide
  • End User guide
  • Admin guide
  • ...

Other Information

• Vendor Neutral

If this project is coming from an existing proprietary codebase, ensure that all proprietary trademarks, logos, product names, etc. have been removed. All ONAP deliverables must comply with this rule and be agnostic of any proprietary symbols.

• Free and Open Source Software

FOSS activities are critical to the delivery of the whole ONAP initiative. The information may not be fully available at Release Planning, however to avoid late refactoring, it is critical to accomplish this task as early as possible.
List all third party Free and Open Source Software used within the release and provide License type (BSD, MIT, Apache, GNU GPL,... ).
In the case non Apache License are found inform immediately the TSC and the Release Manager and document your reasoning on why you believe we can use a non Apache version 2 license.

Each project must edit its project table available at Project FOSS.

Charter Compliance

The project team comply with the ONAP Charter.