...
| Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | POLICY-1840 |
|---|
|
| 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.0.0
success- matchablecount: 3
geographyfailure-count: US0
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
|
- policy-id was initial approach
- 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:
| Code Block |
|---|
{
"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
|