Page Comparison

CLAMP-Controlloop Control loop interacts with Policy framework to create and deploy policies.

This test makes sure the interaction between policy and controlloop is working as expected.

Testing Procedure:

1. Control loop runtime, DMaap, Policy participant are deployed in k8s cluster along with POLICY.
2. Commission a TOSCA template containing the definition of a Control loop from POLICY GUI. The definitions include policy participant and a control loop element that creates and deploys required policies.
   1. (Sample TOSCA template used for policy creation and deployment  click-here)
3. Verify commissioning is successful from GUI to control loop runtime.
4. Instantiate the control loop from GUI.
   1. Verify instance properties of Control loop elements are editable.
   2. Verify the instance created successfully with default state "UNINITIALISED".
5. Change the state of Control loop from "UNINITIALISED" to "PASSIVE" and make sure the policy participant has created the defined policy types from TOSCA template by querying the policy types from POLICY API.
   1. (https://<POLICY-API-IP>/policy/api/v1/policytypes)
6. Change the state of Control loop from "PASSIVE" to "RUNNING". Verify the policy participant has deployed the policies defined for the control loop element in POLICY PAP for all the pdp groups.
   1. (https://<POLICY-PAP-IP>/policy/pap/v1/pdps)
7. Change the state of Control loop from "RUNNING" to "PASSIVE". Verify the policies are undeployed in Policy PAP for all the pdp groups.
8. Change the state back to "UNINITIALISED". This should delete the policy types that was created in POLICY API.
   1. (https://<POLICY-API-IP>/policy/api/v1/policytypes)

      Repeat the test with multiple combinations of control loop state changes and make sure the policy participant can create/deploy/undeploy policies and the interaction between CLAMP policy participant and POLICY is working fine.