The content of this template is expected to be fill out for M1 Release Planning Milestone.
| Info | ||
|---|---|---|
| ||
Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki. |
| Table of Contents | ||
|---|---|---|
|
Overview
...
Please see Honolulu Release Platform Maturity
API Incoming Dependencies
List the API this project is expecting from other projects.
API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
| To fill out | High level description of the API | Date for which the API is reviewed and agreed | To fill out | Link toward the detailed API description |
| AAF | Authentication | We are not expecting any upgrades for any of our requirements. | M3 | |
| Dmaap | Message Router | We are not expecting any upgrades for any of our requirements. | M3 | |
| SDC | Service Distribution | We are not expecting any upgrades for any of our requirements. DMaaP | M3 | |
| AAI | Schema for custom query calls | We are not expecting any upgrades for any of our requirements. REST | M3 | |
| SO | VF Module Create | We are not expecting any upgrades for any of our requirements. REST | M3 | |
| SDNR | SDN-R component interface | We are not expecting any upgrades for any of our requirements. Dmaap - No direct link to any libraries | M3 | |
| SDNC | SDN-C component interface | We are not expecting any upgrades for any of our requirements. Dmaap - No direct link to any libraries | M3 | |
| VFC | VFC component interface | We are not expecting any upgrades for any of our requirements. REST | M3 | |
| CDS | CDS component Interface | We are not expecting any upgrades for any of our requirements. gRPC | M3 |
API Outgoing Dependencies
API this project is delivering to other projects.
API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
| To fill out | High level description of the API | Date for which the API is reviewed and agreed | To fill out | Link toward the detailed API description |
| Policy Lifecycle API | CRUD for Policy Types and Policies | M3 | M3 | https://docs.onap.org/projects/onap-policy-parent/en/latest/api/api.html |
| PAP API | PDP Group API and Deploy/Undeploy of Policies Health Check Policy Deployment Status PDP-Policy Deployment Status | M3 | M3 | https://docs.onap.org/projects/onap-policy-parent/en/latest/pap/pap.html |
| Decision API | Client API for ONAP components to ask for Decision as to which policy they should enforce for a set of given attributes. | M3 | M3 | https://docs.onap.org/projects/onap-policy-parent/en/latest/xacml/decision-api.html |
Third Party Products Dependencies
Name | Description | Version |
|---|---|---|
| MariaDB | The MariaDB is the repository that holds all the policies, templates, PDP group, and deployment information. | 10.5.8 |
| Nexus | (Optional) The Nexus repository holds all the currently deployed Operational (i.e. Drools policies) and their dependent artifacts. | 2.14.13-01 |
| Alpine | Operating system | 3.12.0 |
| OpenJDK | OpenJDK for Alpine from integration images (integration/docker/onap-java11 repository) | openjdk11:jre-11.0.9.1_1-alpine |
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.
TODO
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
TODO
Please refer to Frankfurt Defect Status
N/A
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 - Honolulu RisksThe testing and integration activities are described in the following page: Policy R8 Honolulu CSIT/External Lab Functional Test Cases.
Gaps
No gaps identified.
Known Defects and Issues
There is no major known defects and issues.
Risks
There is only one risk associated with package upgrades to interface with the CDS component as documented in the following page: Honolulu 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.
...