Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This page will capture the design of the Policy PEP Registration API and the resulting thePolicy Update Notifications on Dmaap notifications of policy updates. This work is related to the functional requirements from Control Loop subcommittee: Policy Update Notifications.

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPOLICY-1840

Option 1 - Don't implement the API at all

Use a well-known Dmaap topic for policy updates that any application can listen to. Look for the TOSCA Policy Type the component is interested in.

Option 2 - Implement the API to register a Dmaap topic for a specific Policy Type

ONAP components register a dmaap topic for Policy PAP to send simple notifications for a Policy Type that is either newly deployed, updated with a new version, or undeployed.



Code Block
   deployed_policies:
    - 
     policy-type: onap.policies.monitoring.cdap.tca.hi.lo.app
     policy-type-version: 1.0.0
     policy-id: onap.scaleout._tca:
	 policy-version: 2
     - matchable:
       geography: US
   undeployed_policies:
     - 
	 policy-id: onap.firewall.tca










...