...
- Delta policy update between PAP & PDP
Currently the whole list of policies are transferred always between PAP & PDP for any deploy/undeploy operation. This should be changed to only send the policy for which deploy/undeploy operation has to be performed by the PDP.
This will help in not affecting other policies while trying to enable/disable a policy in PDP. Also, improves the overhead of sending the whole list again and again and PDP scanning through the li
As discussed on Policy weekly call (15th July):
- Drools PDP : Already has support of scanning the policy list coming from PAP and only deploy/undeploy the policy which is either new in the list
...
- or missing in the list. Hence, no impact to other running policies.
- Xacml PDP : Also has the same support like drools-pdp.
- Apex PDP : Currently when it receives the list of policy, the current instance of engine is brought down and started again with new set of policies. Hence, impacting the other running policies. NEED TO BE FIXED
When
- Graceful undeploy of policy in PDP
When a PDP engine receives undeploy request from PAP, it should ideally try to finish the processing of any ongoing event and then gracefully undeploy the policy.
As discussed on Policy weekly call (15th July):
- Drools PDP : Already has the support.
- Xacml PDP : Also has the same support like drools-pdp.
- Apex PDP : Currently when it receives the list of policy, the current instance of engine is brought down immediately. Hence, impacting the ongoing event processing. NEED TO BE FIXED