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
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Enter the name of the release you are targeting to deliverIstanbul |
| Project Lifecycle State | Either Incubation, Core, Mature. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information |
| Participating Company | List the company participating in this release. At least 3-4 organizations, including an operator are recommended. |
Scope
What is this release trying to address?
Describe the problem being solved by this release
Requirements
Describe the use case this release is targeted for (better if reference to customer requirements).
Minimum Viable Product
Describe the MVP for this release.
| Mature | |
| Participating Company | AT&T, Ericsson, Bell Canada |
Scope
Planned Updates
- Make policy-clamp official
- Make TOSCA Control Loop official
- Multi-cluster support
- Only send policy deltas to PDPs
- Allow rules to specify EventManagerService
- DB Enhancements
- Unify the representation of control loops in CLAMP
- Update control loop TOSCA to support design-time and runtime roles
- APEX-PDP enhancements
- SSL support in Kafka IO plugin
- Send notifications to DMaaP/Kafka
- Context album improvements
- Mount truststore via helm charts
- Add more flexible time and dayOfWeek capabilities in xacml-pdp
- Store audit details of policy deploy/undeploy in PAP
- Enhance consolidated health check to include dependencies (e.g., DMaaP connectivity)
- Usual sonar/code coverage improvements
- Archive policy-engine repo and change its status to “unmaintained”
Requirements
Please see the release requirements planned as identified in Policy Istanbul-R9 Architecture Review
Minimum Viable Product
The following application components are the MVP from this release.
- Policy Lifecycle API component
- Policy Administration Point component
- PDP-A - Apex PDP Engine
- PDP-D - Drools PDP Engine
- PDP-X - XACML PDP Engine
- Policy Distribution Component
Functionalities
List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.
Epics
Jira server ONAP JIRAJira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project =sanbox = POLICY AND fixVersion = "Istanbul Release" and issuetype in (epic) serverId 425b2b0a-557c-3c0c-b515-579789cceedb
Stories
Jira server ONAP JIRAJira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project = sanbox POLICY AND fixVersion = "Istanbul Release" and issuetype in (story) serverId 425b2b0a-557c-3c0c-b515-579789cceedb
...
| Deliverable Name | Deliverable Description |
|---|---|
| To fill out | To fill out |
Sub-Components
List all sub-components part of this release.
Activities related to sub-components must be in sync with the overall release.
| Policy Drools PDP | Executable - supports Tosca Policies execution in the Drools PDP |
| MariaDB | SQL database
|
| 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 | Executable(s) - supports Policy creation via a GUI and TOSCA Control Loops |
Sub-Components
See the table above for the Policy subcomponents. Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
Architecture
High level architecture diagram
At that stage within the Release, the team is expected to provide more Architecture details describing how the functional modules are interacting.
Indicate where your project fit within the ONAP Architecture diagram.
Block and sequence diagrams showing relation within the project as well as relation with external components are expected.
Anyone reading this section should have a good understanding of all the interacting modules.
Platform Maturity
ARC Policy Framework Component Description - Istanbul-R9
https://docs.onap.org/projects/onap-policy-parent/en/latest/architecture/architecture.html
Platform Maturity
Please see Istanbul Please fill out the centralized wiki page: Frankfurt Release Platform Maturity
API Incoming Dependencies
...