Page Status: Updated by PTL  
Component Status: Updated by PTL  ; Pending PTL Updates and ArchCom Review
Last Reviewed:
Certified by:

1. High Level Component Definition and Architectural Relationships 

In the Honolulu release the CLAMP component is being integrated into the Policy component as a PoC (see REQ-473 - Getting issue details... STATUS ) .     CLAMP's functional role to provision Policy stays the same, as the project and associated resources are simply moved under the policy umbrella.

2. API Definitions

2a. Exposed APIs

Interface NameDefinitionCapabilitiesVersionStatusPayload Model(s)API Spec (Swagger)
POE-1Policy Type DesignAllows applications to create, update, delete, and query PolicyType entities so that they become available for use in ONAP by applications such as CLAMP.1.0.0production


POE-2Policy DesignAllows applications (such as CLAMP and Integration) to create, update, delete, and query Policy entities.1.0.0production


POE-3Policy AdministrationSupport CRUD of PDP groups and subgroups and to support the deployment and life cycles of PolicyImpl entities (TOSCA Policy and PolicyTypeImpl entities) on PDP sub groups and PDPs.1.0.0productionEmbedded
POE-4Data IngressListen on a DMaaP topic. 

Messages of interest are described in the policy logic


POE-5Decision QueryPolicy decisions are required by ONAP components to support the policy-driven ONAP architecture. Policy Decisions are implemented using the XACML and Apex PDPs. The calling application (which may be another policy – e.g. invocation of a guard policy from PDP-D) must provide attributes in order for the PDP to return a correct decision.NAproductionDefined by policy

2b. Consumed APIs

Interface NameConsumed byDescriptionAPI Spec (Swagger)
AAFPolicy FrameworkAuthentication and authorization

Policy Framework


Policy framework uses DMaaP for SDC subscriptions and internal communication.

Policies use DMaaP as a transport for contextual information from various sources

SDCPolicy FrameworkNotification of CSAR; Retrieval of CSAR
AAIPoliciesEnrich ingress data with topology information
SOPoliciesTrigger orchestration actions (policy driven)




PoliciesTrigger control actions (policy driven)
OtherPoliciesTrigger any interface defined in a policy, for example, trouble ticketing

3. Component Description

The ONAP Policy Framework is a comprehensive policy design, deployment, and execution environment. The Policy Framework is the decision making component in an ONAP system. It allows you to specify, deploy, and execute the governance of the features and functions in your ONAP system, be they closed loop, orchestration, or more traditional open loop use case implementations. The Policy Framework is the component that is the source of truth for all policy decisions

Please see the TOSCA Policy Primer page for an introduction to TOSCA policy concepts. See the Policy Design and API flow page for a description of the component interactions.

TOSCA defines a PolicyType, the definition of a type of policy that can be applied to a service. It also defines a Policy, the definition of an instance of a PolicyType. In the Policy Framework, we must handle and manage these TOSCA definitions and tie them to real implementations of policies that can run on PDPs.

Each TOSCA PolicyType must have a corresponding PolicyTypeImpl in the Policy Framework. The TOSCA PolicyType definition can be used to create a TOSCA Policydefinition, either directly by the Policy Framework, by CLAMP, or by some other system. Once the Policy artifact exists, it can be used together with the PolicyTypeImpl artifact to create a PolicyImpl artifact. A PolicyImpl artifact is an executable policy implementation that can run on a PDP.

The TOSCA PolicyType artifact defines the external characteristics of the policy; defining its properties, the types of entities it acts on, and its triggers.  A PolicyTypeImpl artifact is an XACML, Drools, or APEX implementation of that policy definition. PolicyType and PolicyTypeImpl artifacts may be preloaded, may be loaded manually, or may be created using the Lifecycle API. Alternatively, PolicyType definitions may be loaded over the Lifecycle API for preloaded PolicyTypeImpl artifacts. A TOSCA PolicyType artifact can be used by clients (such as CLAMP or CLI tools) to create, parse, serialize, and/or deserialize an actual Policy.

The TOSCA Policy artifact is used internally by the Policy Framework, or is input by CLAMP or other systems. This artifact specifies the values of the properties for the policy and specifies the specific entities the policy acts on. Policy Design uses the TOSCA Policy artifact and the PolicyTypeImpl artifact to create an executable PolicyImpl artifact. 

Internally, Policy has three main functional areas: Policy Development; Policy Administration; Policy Decision Execution.

Policy Development abstracts persistence and supports the creation of policies/policy types.

Policy Administration also abstracts persistence (from a different user roles). It's main purposes are to ensure that policies are allocated correctly and to manage the life-cycle of policies.

Policy Decision Execution is where policy decisions are made, i.e. where the policy logic executes. Three languages are used to describe policies in ONAP: XACML; Drools; APEX. Policy designers may select the language that is most appropriate to their use case. The policies are interpreted and executed by a language specific PDP. Where necessary additional PDP may be added, thus allowing for new policy languages.

Policy Enforcement is in general not handled by the Policy Framework. Enforcement is handled by either the originator of a decision query (PDP-D does enforce guard policy decisions made in the XACML PDP), or by a reaction to a policy output (trigger). 

4. Known System Limitations

5. System Deployment Architecture

6. New Release Capabilities

The main new capability introduced in this release as a PoC is the integration of the CLAMP component under the policy umbrella (see REQ-473 - Getting issue details... STATUS ).   The software is being moved under the policy/clamp repository (    The OOM helm charts are also moving as a subcomponent of policy  (

And additional PoC experiments with defining Control Loops fully in Tosca.   This is covered by  REQ-478 - Getting issue details... STATUS .

As outlined in the architecture review page (Policy Honolulu-R8 Architecture Review) the only new use case that may be supported as a stretch goal is the 5G one ( REQ-429 - Getting issue details... STATUS ).   Existing use cases will be supported (no change).

Conformance with ONAP wide requirements ( REQ-441 - Getting issue details... STATUS , REQ-437 - Getting issue details... STATUS , REQ-398 - Getting issue details... STATUS , REQ-396 - Getting issue details... STATUS , and REQ-439 - Getting issue details... STATUS  (there are some risks, see Honolulu Risks page)) are already or will be supported.

Additional enhancements to the Policy components will be introduced in this release that have no external impact.    These include but are not limited to:

  • Stateless PAP (Keep no state in PAP runtime container, so state retrieval would be from database).
  • Interoperability of Native and non-native policies in the Drools PDP. 
  • Healthcheck status improvements as well as statistics reporting.

7. References

  1. Honolulu architecture description
  2. Policy Framework API's -

  • No labels