...
| Scope | Priority | Committer Lead | Resources Committed | Epics | Dependencies |
|---|
| Policy Architecture Finishing ReBuild started in Dublin | Highest | | | | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | POLICY-1840 |
|---|
|
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | POLICY-2025 |
|---|
|
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | POLICY-2026 |
|---|
|
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | POLICY-2028 |
|---|
|
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | POLICY-2067 |
|---|
|
Control Loop Sub Committee Functional Requirements | High | | | |
| Liam Fallon TSC Must Have Test Coverage Target 55% (waiver granted in El Alto resolution) | Highest | | Pamela Dragosh Internal AT&T Policy Team Other folks when available | | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | POLICY-20271937 |
|---|
|
|
|
| S3P Requirements | Highest | | | | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | POLICY-2087 |
|---|
| | Jira Legacy |
|---|
|
|
|
Control Loop Sub Committee Functional Requirements
| High | | | | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | POLICY-2118 |
|---|
|
| Native API - introduction of Native API for supporting raw PDP policies in the platform. | High | | Chenfei Gao Jorge Hernandez Ali Hockla | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | POLICY-1845 |
|---|
|
| Contributions from AT&T | Medium | | Internal AT&T Team | | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | POLICY-1943 |
|---|
|
| Technical Debt - addressing bugs, leftover work from El Alto, code coverage, sonar fixes, etc. | Medium | | | |
| Native Policy Types - introduction of Policy Types for Native PDP policies/rules. | High | | | | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | POLICY-19301845 |
|---|
|
|
|
| Contributions from AT&T | Medium | | Internal AT&T Policy Team | | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | POLICY-2069 |
|---|
|
|
|
| Technical Debt - addressing bugs, leftover work from El Alto, code coverage, sonar fixes, etc. | Medium | | All resources are supporting these tasks. | | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | POLICY-2162 |
|---|
|
| PDP Monitoring GUI | Low | | Ericsson China Team | | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | POLICY-1751 |
|---|
|
|
Requirements
| Requirement | Impact | Epic | Notes |
|---|
|
|
| 5G OOF Use Cases - Control Loop Coordination usage | Medium | | | | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key |
|---|
|
|
REQ9X-Small | | Jira Legacy |
|---|
|
|
| PDP Monitoring GUI | Low | | Ericsson China Team | | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | POLICY- |
|---|
|
|
2027Medium |
|
| 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. | | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key |
|---|
|
|
REQ-21 | Requirements
| Requirement | Impact | Epic | Notes |
|---|
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | POLICYREQ-2118 |
|---|
|
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | REQ-25 |
|---|
|
| | X-Small | | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | POLICY- |
|---|
|
| 1840 |
|
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | REQ- |
|---|
|
| 29 | X-Small | User Stories in Technical Backlog:
Medium | | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | POLICY- |
|---|
|
| 1866 |
|
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | REQ-3325 |
|---|
|
| MediumSmall | | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | POLICY-20871840 |
|---|
|
|
|
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | REQ- |
|---|
|
| 162 | MediumX-Small | User Stories in Technical Backlog: | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | POLICY- |
|---|
|
| 1740 |
|
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key |
|---|
|
| POLICY | 1869 | Medium | | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | REQPOLICY-1542087 |
|---|
|
| Small |
|
Longer term roadmap
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| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key |
|---|
|
| POLICY-2162 |
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
The following legacy applications components will be part of this release:
- Policy Portal Dashboard - GUI
- Policy PAP web application - Policy backend that manages communication with PDP engines for policy distribution.
- Policy XACML PDP - legacy XACML PDP for policies/templates that are translated into XACML Policies. Also is the entry point for API requests which get routed through legacy PAP to Drools PDP.
- Policy BRMS Gateway - intermediary backend for distributing policies to the Drools PDP and configuration details to the Drools PDP controller.
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 Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | project=Policy and issuetype in (epic) and fixVersion='Frankfurt Release' |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
|
Stories
| Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | project=Policy and issuetype in (story) and fixVersion='Frankfurt Release' |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
|
| Medium | User Stories in Technical Backlog: | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | POLICY-1740 |
|---|
|
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | POLICY-1869 |
|---|
|
|
|
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | REQ-154 |
|---|
|
| Small | | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | POLICY-2162 |
|---|
|
|
|
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
The following legacy applications components will be part of this release:
- Policy Portal Dashboard - GUI
- Policy PAP web application - Policy backend that manages communication with PDP engines for policy distribution.
- Policy XACML PDP - legacy XACML PDP for policies/templates that are translated into XACML Policies. Also is the entry point for API requests which get routed through legacy PAP to Drools PDP.
- Policy BRMS Gateway - intermediary backend for distributing policies to the Drools PDP and configuration details to the Drools PDP controller.
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 Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | project=Policy and issuetype in (epic) and fixVersion='Frankfurt Release' |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
|
Stories
| Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | project=Policy and issuetype in (story) and fixVersion='Frankfurt Release' |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
|
Longer term roadmap
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 |
|---|
| 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 - Stores policies and their versions
- Stores templates/models and their versions
- Stores PDP grouping information
- Stores Policy distribution details
- Operational History 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.
...
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
...
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 |
|---|
|
|
Please refer to Frankfurt Defect Status
...
Please update any risk on the centralized wiki page - Frankfurt Risks
Fill out the Resources Committed to the Release centralized page.
...