...
| Name | Description | Version |
|---|---|---|
| Docker | VM Container | 18 and above |
| ODL Yang Tools | Yang model and Data Parser | 5.0.6 |
| Postgres Docker image | VM container for Postgres | 13.2-alpine |
| 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.5.0 |
| cglib-nodep | 3pp | 3.1 |
| commons-lang3 | 3pp | 3.11 |
| antlr4-runtime | Language parser | 4.9.2 |
| liquibase | DB Schema (version) management | 4.3.1 |
...
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.
...
- CPS has high level of built jUnit test (CPS-Core+NCMP >95%, Temporal DB >75% ) 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 are part of CPS -Repo, see https://gerrit.onap.org/r/gitweb?p=cps.git;a=tree;f=csit;h=8505b66089f62b6431c1091edf820cbdbf4363d4;hb=HEAD
And executed automatically through the cps-review-verification-maven-master CI Job - E2E Integration with ONAP components introduced in I-release (like SDN-C, A&AI) will be added/tracked by
Jira server ONAP Jira serverId 425b2b0a-557c-3c0c-b515-579789cceedb key INT-1902
Gaps
No gaps Identified
Known Defects and Issues
See dynamic Jira filter:
| Jira | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Risks
No Risks identified, see also Istanbul Risks
Resources
| Excerpt Include | ||||
|---|---|---|---|---|
|
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.
...
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 recommended 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
...