...
The ONAP Policy Framework architecture separates policies from the platform that is supporting them. The framework supports development, deployment, and execution of any type of policy in ONAP. The Policy Framework is metadata (model) driven so that policy development, deployment, and execution is as flexible as possible and can support modern rapid development ways of working such as DevOps. A metadata driven approach also allows the amount of programmed support required for policies to be reduced or ideally eliminated.
...
- The Policy GUI Dashboard is created from the ONAP Portal SDK to create a consistent user experience
- The Policy GUI Designer is created from the ONAP SDC SDK to create a consistent user experience
Design Time Capabilities
- Design Time policies should be easy to specify and capture from either the SDC GUI or the Policy GUI
- High-level Conflict Detection and Resolution tools will be utilized to help identify possible conflicts
- Provide a model-driven Design Time framework for ingestion of models for policies and any optional support code
- Policy Development Environment for designing models and their support code
- Conflict Detection and Resolution for Policies should be available during development and testing phases
- Policies are be easy to specify
Discuss support for SDC.
The platform that could can policy models organically and not require any development work. The Policy GUI should be to interpret any TOSCA Model ingested and flexibly present a GUI for a user to create policies from.
2.2 Policy Deployment Architecture
...
- PDPs scale horizontally
- Policies are upgradable with state preserved within the limitations of semantic versioning (State preserved for minor/patch version upgrades), see 2.
The long term architecture view is for policy artifacts to be located in a nexus repository that are pulled by appropriate PDP micro service engines. Dependencies would be set in the policy artifact jar files themselves and not hard coded into the platform as a JSON file.
- Policy API will support Lifecycle management for policies that are deployed such as modes and retirement. This additional requirement is better suited for the new proposed Policy Lifecycle API than the current API.
2.3 Policy Execution Architecture
...