...
- CPS can store the module used for E2E Network Slicing and SON PCI (but any other model could be stored too)
- Yang json dat file can be stored for same model (with some validation)
- Support concept of Anchors (data entry points) even if only used one for MVP
- An xNfProxy interface wil be used to access xNF configuration data in CPS (hide soem of teh CPS housekeeping from xNF data users)
- Dataspace, model and dat will be hardcoded as part of xNfProxy stub in this release
- Query support wil be limited to whatever is needed for E2E Network Slicing use cases
Functionalities
Epics
| Jira | ||||||
|---|---|---|---|---|---|---|
|
| Jira | ||||||
|---|---|---|---|---|---|---|
|
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key CPS-168
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key CPS-120
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key CPS-118
(stretch)Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=cps and issuetype in (epic) serverId 425b2b0a-557c-3c0c-b515-579789cceedb key CPS-86
Stories
Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project = sanbox "Configuration Persistence Service" and issuetype in (story(Story) and ("Epic Link" = CPS-168 or fixVersion = "Honolulu Release" ) serverId 425b2b0a-557c-3c0c-b515-579789cceedb
...
| Name | Description | Version |
|---|---|---|
| Docker | VM Container | 18 and above |
| ODL Yang Tools | Yang model and Data Parser | 5.0.6.0.6 |
| Postgres Docker image | VM container for Postgres | 13.1 (will use 'latest' image released at built time) |
| Open JDK image | Base image | 11-jre-slim |
| Jetty | Application server | 9.4.31 |
| Swagger | OpenAPI library | 2.1.4 |
| SpringFox | OpenAPI library | 3.0.0 |
| Hibernate types | Support for Postgres datatype JSONB | 2.10.0 |
| Spring Boot | Application Framework | 2.3.3.RELEASE |
| cglib-nodep | 3pp | 3.1 |
| commons-lang3 | 3pp | 3.11 |
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.
...
- CPS has high level of built jUnit test (>90%) which is enforced by our maven build scripts
- CPS has built in Persistence Layer test ie. test that integrate with real DB covering all use cases and are part of WoW
- CIST test need to be identified as part of Deployment Epic but will be included in Honolulu timeframe
SeeJira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key CPS-188
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.
| Gaps identified | Impact | ||
|---|---|---|---|
| xNF-Proxy data mirroring and syncing | data instance hardcode (ie. loaded upon deploy) | To fill out | To fill out |
Known Defects and Issues
Please refer to Frankfurt Defect Status CPS Release note when available
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. Honolulu Risks No risk identified at the moment
Release Milestone
The milestones are defined at the Release LevelPlanning: Honolulu and all the supporting project agreed to comply with these dates.
...
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 Honolulu Documentation – To be updated when avail
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
- ...
...