...
| Scope | Priority | Committer Lead | Resources Committed | Epic | Dependencies | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Technical Debt | Highest | Pamela Dragosh |
| ||||||||||||||||||||||
| Policy Architecture Build | Highest | Liam Fallon - Models, PDP policy distribution, Apex Ram Krishna Verma - PDP policy distribution, Distribution, Apex Jorge Hernandez - PDP policy distribution Jim Hahn - PDP target locking Joshua Reich - PDP target locking, CLC policies Michael Mokry - API Chenfei Gao - API Pramod Jamkhedkar - Models (A&AI), XACML Pamela Dragosh - XACML |
| ||||||||||||||||||||||
| Logging Requirements | High |
| |||||||||||||||||||||||
| Security Requirements | High |
|
| ||||||||||||||||||||||
| Control Loop Sub Committee Functional Requirements | High |
|
Use Cases
DRAFT - not committed until resources are identified
| Use Case | Scope | Priority | Committer Lead | Resources committed | JIRA | Dependencies | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| vDNS (via Scale Out) | Control Loop Hardening | Highest |
| |||||||||||
| vFW | TBD - use APP-C LCM API vs old API for ModifyConfig
| High |
| |||||||||||
| 5G - FM Meta Data | VES Event Registration - auto-generate control loop policies | LowLowest | ||||||||||||
| 5G - Configuration with NetConf | TBD | |||||||||||||
| 5G - OOF & PCI | Adding 2nd control loop Add Control Loop Coordination Policies to support both control loops | Low |
| |||||||||||
| vCPE | Test ONLY
| Med | ||||||||||||
| CCVPN | Test ONLY | Med | ||||||||||||
| BBS | Simple Pass through Policy | Low |
| |||||||||||
| Change Management Dublin Extensions | TBD Schedule optimization with Automated Conflict Avoidance Traffic Migration Workflow | LowLowest | VOLTE | Compilation and CSIT ONLY - no resources for Testing ? Deprecated | Lowest |
Minimum Viable Minimum Viable Product
The following application components are the MVP from the Amsterdam, Beijing and Casablanca releases.
- Policy Portal Dashboard - Console GUI where Models, Templates can be imported, updated, deleted, as well as, policies can be created, updated and deleted. The console GUI also has a dashboard where PDP's can be grouped and where Operators can control where policies are distributed to.
- Policy PAP web application - Policy backend that manages communication with PDP engines for policy distribution.
- Policy Drools PDP - run-time execution of Control Loop operational policies. Supports queries from other ONAP components to retrievePDP Engine for policies/templates that are translated into Drools Rules.
- Policy XACML PDP - run-time execution of Control Loop configuration policies of DCAE collectors, analytics and micro serviceslegacy 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.
- Policy SDC Service Distribution - integration with SDC for service distribution
- Policy Apex PDP - new PDP engineApex PDP - PDP engine for policies that are translated into Apex Policies.
The following application components are being newly developed for the Dublin release to support the New Policy Architecture.
- Policy API - Lifecycle API that supports onboarding Policy models/templates and the creation of raw policies from the models/templates.
- Policy PAP (2nd Gen ?) - PAP component that allows PDP engines to be grouped in order to support a set of policies and Deploy/Undeploy of Policies into these PDP groups.
- Policy XACML (2nd Gen) - lightweight XACML PDP
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.
...
| Deliverable Name | Deliverable Description |
|---|---|
| Policy Portal Dashboard | Executable |
| Policy PAP web application (legacy) | Executable |
| API - internal to the Policy Platform. The Policy PDP engines use this API to synchronize policies being distributed. | |
| Policy Drools PDP | Executable |
| Policy XACML PDP (legacy) | Executable |
| Existing API - external to ONAP components. The API is used to CRUD Policies, Deploy Policies, and query for Policy Decisions. | |
| Policy BRMS Gateway | Executable |
| 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 |
| Stretch Goals | The following will only be a deliverable if they are available for community to use. As they are not MVP, they will only be a stretch goal |
| Policy Lifecycle API (2nd Generation) | Description/DocumentationExecutable |
| Policy PAP (2nd Generation) | Executable |
| Policy PDP SDK (2nd Generation) | Code Deliverable |
| Policy XACML PDP (2nd Generation) | Executable |
...
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
| Policy Client API | This is the legacy Policy API is used by other ONAP components to create, update and delete policy(s). | Casablanca version - no changes | n/a | Policy API |
| Policy Query API | This is the legacy Policy API is used by other ONAP components responsible for enforcing policy during runtime. | Casablanca version - no changes | n/a | Policy API |
| Policy Lifecycle API | The new Policy Lifecycle API description, documentation, models, etc. | API will be designed and documented over the course of Casablanca. We do not expect our clients to be able to utilize this API in Casablanca.M3 Dublin | M4 Dublin | TBD |
Third Party Products 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 Releasein the Dublin Release we are working on re-building the current Policy Framework Software Architecture that does not have these limitations.
List identified release gaps (if any), and its impact.
...