Sirisha Manchikanti and Wayne Dunican to update.

Control Loop Elements in the Policy Framework Participant are configured using TOSCA metadata defined for the Policy Control Loop Element type.

The Policy Framework participant receives messages through participant-intermediary common code, and handles them by invoking REST APIs towards policy-framework.

For example, When a ControlLoopUpdate message is received by policy participant, it contains full ToscaServiceTemplate describing all components participating in a control loop. When the control loop element state changed from UNINITIALIZED to PASSIVE, Policy-participant triggers creation of policy-types and policies in Policy-Framework.

When the state changes from PASSIVE to UNINITIALIZED, Policy-Participant deletes the policies, policy-types by invoking REST APIs towards policy-framework.

Run Policy Framework Participant command line using Maven

mvn spring-boot:run -Dspring-boot.run.arguments="--server.port=8082 --topicServer=localhost"

Run Policy Framework Participant command line using Jar

java -jar -Dserver.port=8082 -DtopicServer=localhost target/policy-clamp-participant-impl-policy-6.1.2-SNAPSHOT.jar

Distributing Policies

The Policy Framework participant uses the Policy PAP API to deploy and undeploy policies.

When a Policy Framework Control Loop Element changes from state PASSIVE to state RUNNING, the policy is deployed. When it changes from state RUNNING to state PASSIVE, the policy is undeployed.

The PDP group to which the policy should be deployed is specified in the Control Loop Element metadata, see the Policy Control Loop Element type definition. If the PDP group specified for policy deployment does not exist, an error is reported.

The PAP Policy Status API and Policy Deployment Status API are used to retrieve data to report on the deployment status of policies in Participant Status messages.

The PDP Statistics API is used to get statistics for statistics report from the Policy Framework Participant back to the CLAMP runtime.