Project Name: Policy Framework Project
Project Description:
The Policy subsystem of ONAP maintains, distributes, and operates on the set of rules that underlie ONAP’s control, orchestration, and management functions. Policy provides a centralized environment for the creation and management of easily-updatable conditional rules. It enables users to validate policies and rules, identify and resolve overlaps and conflicts, and derive additional policies where needed. Policies can support infrastructure, products and services, operation automation, and security. Users, who can be a variety of stakeholders such as network and service designers, operations engineers, and security experts, can easily create, change, and manage policy rules.
Project Landing Page:
Project Meeting Minutes:
Leadership Resources :
Role | First Name Last Name | Linux Foundation ID | Email Address |
|---|---|---|---|
| PTL | pdragosh | ||
| Committers | jhh | ||
| liamfallon | |||
| ramverma | |||
| jrh3 |
Project & Release History
The Policy Framework Project has been an active ONAP Project since Amsterdam and has participated in ALL releases through Frankfurt.
Use Case Participation
The key use cases that the Policy Framework project has contributed to are the following:
vFirewall
Scale Out
vCPE
CCVPN
5G OOF SON
BBS
Bitergia Statistics from the Last 2 Years
| Release Name and Timeframe | Commits | Contributors | Companies | Notes |
|---|---|---|---|---|
| Amsterdam | 713 | 38 | 8 | |
| Beijing | 631 | 36 | 6 | |
| Casablanca | 720 | 28 | 10 | |
| Dublin | 1053 | 45 | 13 | This release the team won "Top 3 Demo Award" |
| El Alto | 426 | 28 | 5 | |
| Frankfurt | 1269 | 38 | 8 |
Architecture Alignment:
Last Architecture Review was for Frankfurt on 12/17/2019 with the results posted here: Policy R6 Frankfurt Architecture Review
Artifact Information:
| Artifact | Repo | Line Coverage | Description | Notes |
|---|---|---|---|---|
| policy/parent | https://github.com/onap/policy-parent | n/a | Our main parent repo that contains shared dependency/pom.xml configurations for all the repos | |
| policy/docker | https://github.com/onap/policy-docker | n/a | Builds the base docker images for all the policy repos. | |
| policy/common | https://github.com/onap/policy-common | 86.9% | Common code shared among the policy repos. | |
| policy/models | https://github.com/onap/policy-models | 92% | Model code shared among the policy repos. | |
| policy/api | https://github.com/onap/policy-api | 91% | Lifecycle API component. | |
| policy/pap | https://github.com/onap/policy-pap | 94.7% | Policy Administration Point component. | |
| policy/apex-pdp | https://github.com/onap/policy-apex-pdp | 81.1% | Apex PDP engine component. | |
| policy/drools-pdp | https://github.com/onap/policy-drools-pdp | 76.1% | Drools PDP engine component. This is a vanilla version that does not include ONAP application code. | |
| policy/xacml-pdp | https://github.com/onap/policy-xacml-pdp | 90.3% | XACML PDP engine component and Decision API implementation. | |
| policy/distribution | https://github.com/onap/policy-distribution | 80.9% | Policy SDC Distribution component. | ONAP Community Award in Casablanca - https://wiki.onap.org/display/DW/ONAP+Community+Awards:+Casablanca+Release |
| policy/drools-apps | https://github.com/onap/policy-drools-applications | 84.8% https://sonarcloud.io/dashboard?id=onap_policy-drools-applications | Drools PDP engine component that includes ONAP applications. | NOTE: This repo was created pre-Amsterdam and had split the PDP with its apps. Apex and XACML were created later and decided to combine the PDP and its application code into one repo. |
| policy/engine | https://github.com/onap/policy-engine | 55.1% | Legacy Policy components from Amsterdam seed code. | NOTE: Will be deprecated in Guilin |
| policy/gui | https://github.com/onap/policy-gui | 47.9% https://sonarcloud.io/component_measures?id=onap_policy-gui&metric=line_coverage&view=list | Newly introduced in Frankfurt, this repo contains GUI code. Currently only a PDP Monitoring GUI is available for experimentation. | Remains experimental PoC for Guilin. Expected to boost code coverage in Guilin. |
Integration Testing Support
The Policy Team supports the Integration vFirewall Use Case Testing every release and contributes changes to the Integration Robot Framework and Testsuite when updates are necessary.
Some example JIRA's for this:
INT-319 - Getting issue details... STATUS
INT-445 - Getting issue details... STATUS
INT-1350 - Getting issue details... STATUS
integration/oparent support
Policy team members support the Integration oparent project, our main policy/parent integration pom.xml inherits from the latest artifact produced by Integration.
Team actively supports oparent checkstyle in all our repos.
In addition, our ci-management verify jobs are configured to fail on any checkstyle violation vs the default 'warn' only. Thus, adhering to a more strict enforcement of integration code style rules.
Companies that run ONAP Policy internally
To our knowledge, the following companies have used ONAP Policy Framework internally: AT&T, Ericsson, Bell Canada, Tech Mahindra, Wipro.
Other Information:
ONAP Policy Framework has had topics and demo's at the ONAP Developer and LFN ONES conferences. Here is a list of recent demo's:
2019-06-12 LFN DDF Plugfest Kista, Sweden
2019-09-23-25 ONS at Antwerp, Belgium Policy Framework Demonstration - won Best Demo Award!
2020-01-15 LF ONAP Prague DDF Policy Framework - Frankfurt Improvements
2020-04-23 LF Virtual Technical Event - Policy Framework Overview
Policy Framework Won: Top 3 Demo Award - Dublin
ONAP Community Awards: Dublin Release (Demos Only)
Project Innovation Award - Casablanca
The Policy Framework Project received an ONAP Community Award in Casablanca - https://wiki.onap.org/display/DW/ONAP+Community+Awards:+Casablanca+Release
wiki.onap.org
ONAP Community Awards: Casablanca Release - Developer Wiki - Confluence
Control Loop Sub Committee Participation
The Policy Framework Project has been active in the Control Loop subcommittee from its inception. Working very closely with CLAMP and DCAE to support the automation and enhancement of Control Loops in ONAP.
The project shares weekly meetings with the CLAMP Project.