...
What is this release trying to address?
| Scope | Priority | Committer Lead | Resources Committed | Epics | Dependencies | ||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Policy Architecture Finishing ReBuild started in Dublin | Highest |
| |||||||||||||||||||||||||||||||||||||||||||
TSC Must Have Test Coverage Target 55% (waiver granted in El Alto resolution) | Highest |
| |||||||||||||||||||||||||||||||||||||||||||
| S3P Requirements | Highest |
| |||||||||||||||||||||||||||||||||||||||||||
Control Loop Sub Committee Functional Requirements | High |
| |||||||||||||||||||||||||||||||||||||||||||
| Native |
| Policy Types - introduction of |
| Policy Types for Native PDP policies/rules. | High |
| |||||||||||
| Contributions from AT&T | Medium | Internal AT&T Policy Team |
| ||||||||||
| Technical Debt - addressing bugs, leftover work from El Alto, code coverage, sonar fixes, etc. | Medium |
| All resources are supporting these tasks. |
| |||||||||||||||||
| 5G OOF Use Cases - Control Loop Coordination usage | Medium |
Wipro Team |
| ||||||||||||
| PDP Monitoring GUI | Low | Ericsson China Team |
| ||||||||||
| JDK 11 Upgrade | Low | If resources become available and oparent upgrade to JDK 11 is available and the oparent changes work with the policy repos. |
|
Requirements
| Requirement | Impact | Epic | Notes | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| X-Small |
| |||||||||||||||||||||||||
| Medium |
| |||||||||||||||||||||||||
| Small |
| |||||||||||||||||||||||||
| X-Small | User Stories in Technical Backlog:
| |||||||||||||||||||||||||
| Medium |
| |||||||||||||||||||||||||
| Medium | User Stories in Technical Backlog:
| |||||||||||||||||||||||||
| Small |
|
Minimum Viable Product
The following application components are the MVP from this release.
...
Indicate at a high level the longer term roadmap. This is to put things into the big perspective.
Policy Framework Project - Architectural Roadmap for Frankfurt
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note, etc) of this release.
| Deliverable Name | Deliverable Description | To fill out | To fill out|
|---|---|---|---|
| Policy Portal Dashboard | Executable (to be deprecated after this release) | ||
| Policy PAP web application (legacy) | Executable (to be deprecated after this release) | ||
| Policy Drools PDP | Executable (supports both legacy and latest components) | ||
| Policy XACML PDP (legacy) | Executable (to be deprecated after this release) | ||
| Policy BRMS Gateway | Executable (to be deprecated after this release) | ||
| MariaDB | SQL database
| ||
| Nexus Repo | This repository is used by the Policy Drools PDP to retrieve distributed policies and their dependent jars. | ||
| Policy SDC Distribution Integration | Executable - receives SDC Service Distribution notifications and translates VNF/Service policies into runtime policies. | ||
| Policy Apex PDP | Executable | ||
| Policy Lifecycle API | Executable | ||
| Policy PAP | Executable | ||
| Policy XACML PDP | Executable |
Sub-Components
List all sub-components part of this release.
Activities related to sub-components must be in sync with the overall release.
Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
Policy Framework does not have any sub-components.
Architecture
High level architecture diagram
...
Please fill out the centralized wiki page: Frankfurt Release Platform Maturity v1.
This has been filled out.
API Incoming Dependencies
List the API this project is expecting from other projects.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.
Prior to the delivery date, it is a good practice to organize an API review with the API consumers.
| 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 |
| Portal | Portal SDK | Current version 2.6.0 - any upgrades required must be defined before M3 | M3 | |
| AAF | Authentication | We are not expecting any upgrades for any of our requirements. Current version v2.1.2 - any upgrades required by AAF must be defined before M3 | M3 | |
| Dmaap | Message Router | We are not expecting any upgrades for any of our requirements. Current version v1.1.8 - any upgrades required must be defined before M3 | M3 | |
| SDC | Service Distribution | We are not expecting any upgrades for any of our requirements. Current version v1.6.0 - any upgrades required must be defined before M3 | M3 | |
| AAI | Schema for custom query calls | We are not expecting any upgrades for any of our requirements. Current schema v16 aai-schema 1.0.3 - any upgrades required must be defined before M3 | M3 | |
| SO | VF Module Create | We are not expecting any upgrades for any of our requirements. REST | M3 | |
| SDNR | We are not expecting any upgrades for any of our requirements. Dmaap - No direct link to any libraries | M3 | ||
| SDNC | We are not expecting any upgrades for any of our requirements. Dmaap - No direct link to any libraries | M3 | ||
| VFC | We are not expecting any upgrades for any of our requirements. REST | M3 |
API Outgoing Dependencies
...
| 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/en/latest/submodules/policy/parent.git/docs/api/api.html#api-label |
| PAP API | PDP Group API and Deploy/Undeploy of Policies | M3 | M3 | https://docs.onap.org/en/latest/submodules/policy/parent.git/docs/pap/pap.html#pap-label |
| Decision API | Client API for ONAP components to ask for Decision as to which policy they should be enforcement for a set of given attributes. | M3 | M3 | https://docs.onap.org/en/latest/submodules/policy/parent.git/docs/xacml/xacml.html#decision-api-label |
| Legacy Policy Client API | This is the legacy Policy API is used by other ONAP components to create, update and delete policy(s). | El Alto version - no changes | n/a | https://docs.onap.org/en/latest/submodules/policy/engine.git/docs/platform/offeredapis.html#legacyapis-label |
| Legacy Policy Query API | This is the legacy Policy API is used by other ONAP components responsible for enforcing policy during runtime. | El Alto version - no changes | n/a | https://docs.onap.org/en/latest/submodules/policy/engine.git/docs/platform/offeredapis.html#legacyapis-label |
Third Party Products Dependencies
Third Party Products mean products that are mandatory to provide services for your components. Development of new functionality in third party product may or not be expected.
List the Third Party Products (OpenStack, ODL, RabbitMQ, ElasticSearch,Crystal Reports, ...).
| Name | Description | Version | To fill out | To fill out | To fill out
|---|---|---|---|---|
| MariaDB | The MariaDB is the repository that holds all the policies, templates, PDP group, and deployment information. | 10.2.25 | ||
| Nexus | The Nexus repository holds all the currently deployed Operational (i.e. Drools policies) and their dependent artifacts. | 2.14.13-01 | ||
| Ubuntu | Operating system | 16.04 |
In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.
...
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.
Policy R6 Frankfurt CSIT/External Lab Functional Test Cases
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 | To fill out | To fill out|
|---|---|---|---|
Known Defects and Issues
Please refer to Frankfurt Defect Status
...
Please update any risk on the centralized wiki page - Frankfurt Risks
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
...