Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

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

POLICY-1840 - Getting issue details... STATUS



   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.0.0
     - matchable: ???
       geography: US
     success-count: 3
     failure-count: 0
   undeployed_policies:
     - 
     policy-type: onap.policies.firewall
     policy-type-version: 1.0.0
	 policy-id: onap.firewall.tca
	 policy-version: 6.0.0
     success-count: 3
     failure-count: 0



  1. policy-id was initial approach
  2. matchable filters was introduced later


  - per team meeting: 

  • For Policy Update - need to add complexity of multiple PDP groups. How does the client know which group?
    • Agree to just get the first cut done and address this later. Perhaps in G Release.


Options for Decision API calls:


{
  "ONAPName": "DCAE",
  "ONAPComponent": "PolicyHandler",
  "ONAPInstance": "622431a4-9dea-4eae-b443-3b2164639c64",
  "action": "configure",
  "resource": {
     "policy-type": "onap.policies.monitoring.cdap.tca.hi.lo.app"
  }
}


{
  "ONAPName": "DCAE",
  "ONAPComponent": "PolicyHandler",
  "ONAPInstance": "622431a4-9dea-4eae-b443-3b2164639c64",
  "action": "configure",
  "resource": {
      "policy-id": [
        "onap.scaleout.tca",
        "onap.restart.tca"
        ]
  }
}


Can also use abbrev=true to get abbreviated results:

/policy/pdpx/v1/decision?abbrev=true





  • No labels