1 .. This work is licensed under a Creative Commons Attribution 4.0 International License.
2 .. http://creativecommons.org/licenses/by/4.0
6 Policy Administration Point (PAP) Architecture
7 ##############################################
15 The Policy Administration Point (PAP) keeps track of PDPs, supporting the deployment of PDP groups and the deployment
16 of policies across those PDP groups. Policies are created using the Policy API, but are deployed via the PAP.
18 The PAP is stateless in a RESTful sense, using the database (persistent storage) to track PDPs and the deployment of
19 policies to those PDPs. In short, policy management on PDPs is the responsibility of PAP; management of policies by
20 any other manner is not permitted.
22 Because the PDP is the main unit of scalability in the Policy Framework, the framework is designed to allow PDPs in a
23 PDP group to arbitrarily appear and disappear and for policy consistency across all PDPs in a PDP group to be easily
24 maintained. The PAP is responsible for controlling the state across the PDPs in a PDP group. The PAP interacts with the
25 policy database and transfers policies to PDPs.
27 The unit of execution and scaling in the Policy Framework is a *PolicyImpl* entity. A *PolicyImpl* entity runs on a PDP.
28 As is explained above, a *PolicyImpl* entity is a *PolicyTypeImpl* implementation parameterized with a TOSCA *Policy*.
30 .. image:: images/PolicyImplPDPSubGroup.svg
32 In order to achieve horizontal scalability, we group the PDPs running instances of a given *PolicyImpl* entity logically
33 together into a *PDPSubGroup*. The number of PDPs in a *PDPSubGroup* can then be scaled up and down using Kubernetes. In
34 other words, all PDPs in a subgroup run the same *PolicyImpl*, that is the same policy template implementation (in
35 XACML, Drools, or APEX) with the same parameters.
37 The figure above shows the layout of *PDPGroup* and *PDPSubGroup* entities. The figure shows examples of PDP groups for
38 Control Loop and Monitoring policies on the right.
40 The health of PDPs is monitored by the PAP in order to alert operations teams managing policies. The PAP manages the life
41 cycle of policies running on PDPs.
43 The table below shows the deployment methods in which *PolicyImpl* entities can be deployed to PDP Subgroups.
45 ========== =========================================== ============================== ==================================
46 **Method** **Description** **Advantages** **Disadvantages**
47 ========== =========================================== ============================== ==================================
48 Cold The *PolicyImpl* (*PolicyTypeImpl* and No run time configuration Very restrictive, no run time
49 TOSCA *Policy*) are predeployed on the PDP. required and run time configuration of PDPs is possible.
50 PDP is fully configured and ready to administration is simple.
53 PDPs register with the PAP when they
54 start, providing the *pdpGroup* they
55 have been preconfigured with.
57 Warm The *PolicyTypeImpl* entity is predeployed The configuration, parameters, Administration and management is
58 on the PDP. A TOSCA *Policy* may be loaded and PDP group of PDPs may be required. The configuration and
59 at startup. The PDP may be configured or changed at run time by loading life cycle of the TOSCA policies
60 reconfigured with a new or updated TOSCA or updating a TOSCA *Policy* can change at run time and must be
61 *Policy* at run time. into the PDP. administered and managed.
63 PDPs register with the PAP when they start, Support TOSCA *Policy* entity
64 providing the *pdpGroup* they have been life cycle managgement is
65 predeployed with if any. The PAP may update supported, allowing features
66 the TOSCA *Policy* on a PDP at any time such as *PolicyImpl* Safe Mode
67 after registration. and *PolicyImpl* retirement.
69 Hot The *PolicyImpl* (*PolicyTypeImpl* and The policy logic, rules, Administration and management is
70 TOSCA *Policy*) are deployed at run time. configuration, parameters, and more complex. The *PolicyImpl*
71 The *PolicyImpl* (*PolicyTypeImpl* and PDP group of PDPs may be itself and its configuration and
72 TOSCA *Policy*) may be loaded at startup. changed at run time by loading life cycle as well as the life
73 The PDP may be configured or reconfigured or updating a TOSCA *Policy* cycle of the TOSCA policies can
74 with a new or updated *PolicyTypeImpl* and *PolicyTypeImpl* into the change at run time and must be
75 and/or TOSCA *Policy* at run time. PDP. administered and managed.
77 PDPs register with the PAP when they Lifecycle management of TOSCA
78 start, providing the *pdpGroup* they have *Policy* entities and
79 been preconfigured with if any. The PAP may *PolicyTypeImpl* entites is
80 update the TOSCA *Policy* and supported, allowing features
81 *PolicyTypeImpl* on a PDP at any time after such as *PolicyImpl* Safe Mode
82 registration and *PolicyImpl* retirement.
83 ========== =========================================== ============================== ==================================
88 The APIs in the subchapters below are supported by the PAP.
93 The purpose of this API is to support CRUD of PDP groups and subgroups and to support the deployment and life cycles of
94 policies on PDP sub groups and PDPs. This API is provided by the *PolicyAdministration* component (PAP) of the Policy
95 Framework, see the :ref:`ONAP Policy Framework Architecture <architecture-label>` page.
97 PDP groups and subgroups may be prefedined in the system. Predefined groups and subgroups may be modified or deleted
98 over this API. The policies running on predefined groups or subgroups as well as the instance counts and properties may
101 A PDP may be preconfigured with its PDP group, PDP subgroup, and policies. The PDP sends this information to the PAP
102 when it starts. If the PDP group, subgroup, or any policy is unknown to the PAP, the PAP locks the PDP in state PASSIVE.
104 PAP supports the operations listed in the following table, via its REST API:
107 :header: "Operation", "Description"
110 "Health check", "Queries the health of the PAP"
111 "Consolidated healthcheck", "Queries the health of all policy components"
112 "Statistics", "Queries various statistics"
113 "PDP state change", "Changes the state of all PDPs in a PDP Group"
114 "PDP Group create/update", "Creates/updates PDP Groups"
115 "PDP Group delete", "Deletes a PDP Group"
116 "PDP Group query", "Queries all PDP Groups"
117 "Deployment update", "Deploy/undeploy one or more policies in specified PdpGroups"
118 "Deploy policy", "Deploys one or more policies to the PDPs"
119 "Undeploy policy", "Undeploys a policy from the PDPs"
120 "Policy deployment status", "Queries the status of all deployed policies"
121 "PDP statistics", "Queries the statistics of PDPs"
126 PAP interacts with the PDPs via the DMaaP Message Router. The messages listed
127 in the following table are transmitted via DMaaP:
130 :header: "Message", "Direction", "Description"
133 "PDP status", "Incoming", "Registers a PDP with PAP; also sent as a periodic heart beat; also sent in response to requests from the PAP"
134 "PDP update", "Outgoing", "Assigns a PDP to a PDP Group and Subgroup; also deploys or undeploys policies from the PDP"
135 "PDP state change", "Outgoing", "Changes the state of a PDP or all PDPs within a PDP Group or Subgroup"
137 In addition, PAP generates notifications via the DMaaP Message Router when policies are successfully or unsuccessfully
138 deployed (or undeployed) from all relevant PDPs.
140 Here is a sample notification:
142 .. literalinclude:: notification/dmaap-pap-notif.json
146 2 PAP REST API Swagger
147 ======================
149 It is worth noting that we use basic authorization for access with user name and password set to *healthcheck* and
150 *zb!XztG34*, respectively.
152 For every call, the client is encouraged to insert a uuid-type *requestID* as parameter. It is helpful for tracking each
153 http transaction and facilitates debugging. More importantly, it complies with Logging requirements v1.2. If the client
154 does not provide the requestID in a call, one will be randomly generated and attached to the response header,
157 In accordance with `ONAP API Common Versioning Strategy Guidelines
158 <https://wiki.onap.org/display/DW/ONAP+API+Common+Versioning+Strategy+%28CVS%29+Guidelines>`_, several custom headers
159 are added in the response to each call:
162 :header: "Header", "Example value", "Description"
165 "x-latestversion", "1.0.0", "latest version of the API"
166 "x-minorversion", "0", "MINOR version of the API"
167 "x-patchversion", "0", "PATCH version of the API"
168 "x-onap-requestid", "e1763e61-9eef-4911-b952-1be1edd9812b", "described above; used for logging purposes"
171 .. swaggerv2doc:: swagger/health-check-pap.json
173 This operation performs a health check on the PAP.
175 Here is a sample response:
177 .. literalinclude:: response/health-check-pap-resp.json
180 .. swaggerv2doc:: swagger/consolidated-healthcheck-pap.json
182 This operation performs a health check of all policy components. The response
183 contains the health check result of each component. The consolidated health check
184 is reported as healthy only if all the components are healthy, otherwise the
185 "healthy" flag is marked as false.
187 Here is a sample response:
189 .. literalinclude:: response/consolidated-healthcheck-pap-resp.json
192 .. swaggerv2doc:: swagger/statistics-pap.json
194 This operation allows statistics for PDP groups, PDP subgroups, and individual PDPs to be retrieved.
197 While this API is supported, most of the statistics are not currently updated; that work has been deferred to a later
200 Here is a sample response:
202 .. literalinclude:: response/statistics-pap-resp.json
205 .. swaggerv2doc:: swagger/state-change-pap.json
207 The state of PDP groups is managed by this operation. PDP groups can be in states PASSIVE, TEST, SAFE, or ACTIVE. For a full
208 description of PDP group states, see the :ref:`ONAP Policy Framework Architecture <architecture-label>` page.
210 .. swaggerv2doc:: swagger/groups-batch-pap.json
212 This operation allows the PDP groups and subgroups to be created and updated. Many PDP groups can be created or updated
213 in a single POST operation by specifying more than one PDP group in the POST operation body.
214 This can be used to create the PDP group by providing all the details including the supported policy types for each subgroup.
215 However, it cannot be used to update policies; that is done using one of
216 the deployment requests. Consequently, the "policies" property of this
217 request will be ignored.
218 This can also be used to update a PDP Group, but supported policy types cannot be updated during the update operation.
219 So, "policies" and "supportedPolicyTypes" properties in the request will be ignored if provided during the PDP Group update operation.
222 If a subgroup is to be deleted from a PDP Group, then the policies must be removed from
226 Policies cannot be added/updated during PDP Group create/update operations. So, if provided, they are ignored.
227 Supported policy types are defined during PDP Group creation. They cannot be updated once they are created.
228 So, supportedPolicyTypes are expected during PDP Group create, but ignored if provided during PDP Group update.
230 Here is a sample request:
232 .. literalinclude:: request/groups-batch-pap-req.json
235 .. swaggerv2doc:: swagger/group-delete-pap.json
237 The API also allows PDP groups to be deleted. DELETE operations are only permitted on PDP groups in PASSIVE state.
239 .. swaggerv2doc:: swagger/group-query-pap.json
241 This operation allows the PDP groups and subgroups to be listed as well as the policies that are deployed on each PDP
244 Here is a sample response:
246 .. literalinclude:: response/group-query-pap-resp.json
249 .. swaggerv2doc:: swagger/deployments-batch-pap.json
251 This operation allows policies to be deployed on specific PDP groups.
252 Each subgroup includes an "action" property, which is used to indicate
253 that the policies are being added (POST) to the subgroup, deleted (DELETE)
254 from the subgroup, or that the subgroup's entire set of policies is being
255 replaced (PATCH) by a new set of policies. As such, a subgroup may appear
256 more than once in a single request, one time to delete some policies and
257 another time to add new policies to the same subgroup.
259 Here is a sample request:
261 .. literalinclude:: request/deployment-batch-pap-req.json
264 .. swaggerv2doc:: swagger/policy-deploy-pap.json
266 This operation allows policies to be deployed across all relevant PDP groups.
267 PAP will deploy the specified policies to all relevant subgroups. Only the
268 policies supported by a given subgroup will be deployed to that subgroup.
271 The policy version is optional. If left unspecified, then the latest version of the policy is deployed. On the other
272 hand, if it is specified, it may be an integer, or it may be a fully qualified version (e.g., "3.0.2").
273 In addition, a subgroup to which a policy is being deployed must have at
274 least one PDP instance, otherwise the request will be rejected.
276 Here is a sample request:
278 .. literalinclude:: request/policy-deploy-pap-req.json
281 .. swaggerv2doc:: swagger/policy-undeploy-pap.json
283 This operation allows policies to be undeployed from PDP groups.
286 If the policy version is specified, then it may be an integer, or it may be a fully qualified version (e.g., "3.0.2").
287 On the other hand, if left unspecified, then the latest deployed version will be undeployed.
290 Due to current limitations, a fully qualified policy version must always be specified.
292 .. swaggerv2doc:: swagger/deployed-policy-pap.json
294 This operation allows the deployed policies to be listed together with their respective deployment status.
295 The result can be filtered based on policy name & version.
297 Here is a sample response:
299 .. literalinclude:: response/deployed-policy-pap-resp.json
302 .. swaggerv2doc:: swagger/pdp-statistics-pap.json
304 This operation allows the PDP statistics to be retrieved for all registered PDPs.
305 The result can be filtered based on PDP group, PDP subgroup & PDP instance.
307 Here is a sample response:
309 .. literalinclude:: response/pdp-statistics-pap-resp.json
316 3.1 Disable policies in PDP
317 ===========================
319 This operation will allow disabling individual policies running in PDP engine. It is mainly beneficial
320 in scenarios where network operators/administrators want to disable a particular policy in PDP engine
321 for a period of time due to a failure in the system or for scheduled maintenance.