Project Name:
- Proposed name for the project:
Policy Framework
- Proposed name for the repository:
policy/common
- policy/drools-pdp
- policy/engine
- policy/drools-applications
- policy/docker
Project description:
- This project will be dedicated to determine how policy is captured, translated, deployed and updated when designing and on-boarding VNF's and network services.
Scope:
- Deliver points of interoperability within ONAP for VNF and network service On-boarding to capture policy/rule expressions VNF vendor specific policies and network service policies.
- Classification of Policies
- Placement
- Resource allocation
- Remediation Actions (eg. Scaling)
- Compliance Checking (eg. Security)
- SLA
- Health
- Control Loops
- Platform Level Policies
- Governance
- Users
- Customers
- Deliver where/how Policies are expressed
- Policy Domain Specific Language(s) (DSL) - work with the Modeling project to define how policy expressions are captured
- Policy Design GUI - work with SDC project to integrate the Policy Design GUI during VNF/Service design for capturing Policy Expressions
- Deliver requirements for Policy Conflict Detection and mitigation
- Deliver requirements for capturing vendor-embedded policy (Stretch)
- Classification of Policies
- Deliver points of interoperability within ONAP in which captured policies are translated into enforceable actions/outcomes
- Identify how translation of DSL will work
- Instantiation
- Orchestration
- Remediation
- Controllers
- Control Loop
- Analytics, Collectors and Microservices
- CLAMP
- Identify how policy translation works
- A common framework for the decision engines/languages used
- The translation tools needing development
- Identify the Enforcement points within ONAP to support the Use Cases
- Common API design to support enforcement
- Deliver points of interoperability for Day2Day Operations
- Identify architecture, flow and API's for how operations teams can update/deploy/un-deploy Policies
- Deliver points of interoperability to support Adaptive Policy (Stretch)
- Reverse planning, inference rules, machine learning
- Deliver architecture and points of interoperability for Policy Distribution
- How Policy Decision Engines are deployed/un-deployed
- What policies are supported in the various Decision Engines
- Deliver API and flow for updating policy with the decision engines and the enforcement points
- Identify how translation of DSL will work
Architecture Alignment:
- How does this project fit into the rest of the ONAP Architecture?
- Please Include architecture diagram if possible
- What other ONAP projects does this project depend on?
- Modeling - provide input for Policy Expression
- VNF SDK
- SNIRO
- SDC
- Control Loop
- CLAMP
- DCAE
- Orchestration
- Controllers
- Basically every component in ONAP should be policy-enabled
- How does this align with external standards/specifications?
- APIs/Interfaces
- Information/data models
- Are there dependencies with other open source projects?
- XACML (github.com/att/xacml)
- Drools (drools.org)
Resources:
- Primary Contact Person
- Pamela Dragosh - AT&T
- Names, gerrit IDs, and company affiliations of the committers
- Pamela Dragosh - AT&T
- Jorge Hernandez-Herraro - AT&T
- Ralph Straubs - AT&T
- ding yi-ZTE
- xinyuan wang-ZTE
- Names and affiliations of any other contributors
- Alex Vul - Intel
- Avinash S - Huawei
- Nermin Mohamed - Huawei
- Bobby Mander - AT&T
- Project Roles (include RACI chart, if applicable)
Other Information:
- policy/common
- policy/engine
- policy/drools-pdp
- policy/drools-applications
- policy/docker
Use the above information to create a key project facts section on your project page
Key Project Facts
Project Name:
- JIRA project name: Policy Framework
- JIRA project prefix: Policy
Repo name:
Lifecycle State: incubation
Primary Contact: Pamela Dragosh
Project Lead: Pamela Dragosh
mailing list tag [policy]
Committers:
pdragosh@research.att.com
ding.yi5@zte.com.cn
*Link to TSC approval:
Link to approval of additional submitters: