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
...
Other optional capabilities as the ability to swap databases underneath, validation of Tosca Policies will be implemented as time and resources allow.
Requirements
Describe Please see the use case this release is targeted for (better if reference to customer requirements).
TODO
Requirements are requirements planned as identified in Policy Honolulu-R8 Architecture Review
...
Deliverable Name | Deliverable Description |
|---|---|
| Policy Drools PDP | Executable (supports both legacy and latest components)- supports Tosca Policies execution in the Drools PDP |
| MariaDB | SQL database
|
| Nexus Repo | This repository is used by optional component is a maven repository from which the Policy Drools PDP to retrieve distributed policies and their dependent jars.will load application jars. This component is disabled by default. |
| Policy SDC Distribution Integration | Executable - receives SDC Service Distribution notifications and translates VNF/Service policies into runtime policies. |
| Policy Apex PDP | Executable - supports Tosca Policies execution in the Apex PDP |
| Policy Lifecycle API | Executable - supports the provisioning of Tosca Policies. |
| Policy PAP | Executable - supports the administration of policies to PDPs at runtime. |
| Policy XACML PDP | Executable - supports Tosca Policies execution in the XACML PDP. |
| Policy CLAMP (PoC) | PoC that integrates CLAMP functionality into Policy. |
Sub-Components
Policy Framework does not have any sub-components.See the table above for the Policy subcomponents.
Architecture
High level architecture diagram
...
https://docs.onap.org/projects/onap-policy-parent/en/latest/architecture/architecture.html
Platform Maturity
...
Please fill out the centralized wiki page: 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.Current version TBD - any upgrades must be defined before M3 | M3 | |||
| Dmaap | Message Router | We are not expecting any upgrades for any of our requirements. Current version TBD - any upgrades must be defined before M3 | M3 | |||
| SDC | Service Distribution | We are not expecting any upgrades for any of our requirements. Current version TBD - any upgrades must be defined before M3DMaaP | M3 | |||
| AAI | Schema for custom query calls | We are not expecting any upgrades for any of our requirements. Current schema TBD - any upgrades must be defined before M3 aai-schema TBD - any upgrades required must be defined before M3 | M3 | 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. Current version TBD - any upgrades must be defined before M3gRPC | 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. | TBD10.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 | TBD |
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.
...
| 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
The 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
Please refer to
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 Risks
Resources
Fill out the Resources Committed to the Release centralized page and the INFO.yaml for each policy repo:
https://git.onap.org/policy/xacml-pdp/tree/INFO.yaml
https://git.onap.org/policy/pdp/tree/INFO.yaml
https://git.onap.org/policy/parent/tree/INFO.yaml
https://git.onap.org/policy/pap/tree/INFO.yaml
https://git.onap.org/policy/models/tree/INFO.yaml
https://git.onap.org/policy/gui/tree/INFO.yaml
https://git.onap.org/policy/engine/tree/INFO.yaml
https://git.onap.org/policy/drools-pdp/tree/INFO.yaml
https://git.onap.org/policy/drools-applications/tree/INFO.yaml
https://git.onap.org/policy/docker/tree/INFO.yaml
https://git.onap.org/policy/distribution/tree/INFO.yaml
https://git.onap.org/policy/common/tree/INFO.yaml
https://git.onap.org/policy/clamp/tree/INFO.yaml
https://git.onap.org/policy/api/tree/INFO.yaml
https://git.onap.org/policy/apex-pdp/tree/INFO.yaml
Release Milestone
The milestones are defined at the Release LevelPlanning: Honolulu 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: Honolulu 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
- ...
| Note | ||
|---|---|---|
| ||
The Documentation project will provide the Documentation Tool Chain to edit, configure, store and publish all Documentation asset. |
Minor updates are expected as documented in the Honolulu Documentation.
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.NA
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 Please refer to the Policy project section in Project FOSS.
Charter Compliance
The project team comply complies with the ONAP Charter.