...
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | POLICY-1845 |
|---|
|
- Some support for this in the legacy components, this work greatly enhances the ability to load PDP native policies that either execute alone or in conjunction with TOSCA Policy Types. Adds in Apex Native Policy Types in addition to XACML, Drools.
Optimization
...
and Naming Policies - Better Use of the Decision API Pamela Dragosh
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | REQ-162 |
|---|
|
- Finishing the transition to new Policy Types In working with the OOF team that began in Dublin. This release we are working with the SDNC team to complete their transition in Frankfurt., we are moving some of the decision making that the legacy engine could not support into the new xacml PDP engine which supports a Decision API. Previously, OOF had to make 2 separate API calls.
The addition of "matchable" attributes in the Optimization and Naming policies allow the XACML PDP to dynamically translate TOSCA policies to XACML for more fine-grained policy Decisions.
The OOF optimize uses a "best matches" algorithm on top of the XACML engine fine-grained decision in order to further refine the decision to return only the "best matching" policy given the attributes in the Decision API call.
| Code Block |
|---|
| language | js |
|---|
| title | Base Optimization Policies - including "matchable" |
|---|
| linenumbers | true |
|---|
|
tosca_definitions_version: tosca_simple_yaml_1_0_0
policy_types:
onap.policies.Optimization:
derived_from: tosca.policies.Root
version: 1.0.0
description: The base policy type for all policies that govern optimization
properties:
scope:
description: Scope for the policy - could be for a specific release.
type: list
metadata:
matchable: true
required: true
entry_schema:
type: string
geography:
description: One or more geographic regions
type: list
metadata:
matchable: true
required: true
entry_schema:
type: string
constraints:
- valid_values:
- US
- International
identity:
description: Used internally for identification
type: string
required: true |
The OOF optimization Decision includes the ability to ask the decision to take in "context" when returning policy decisions. Eliminates one less call the OOF project had to make to the Policy Decision API to retrieve policies during runtime.
| Code Block |
|---|
| language | js |
|---|
| title | Example Decision API call Payload |
|---|
| linenumbers | true |
|---|
|
{
"ONAPName": "OOF",
"ONAPComponent": "OOF-component",
"ONAPInstance": "OOF-component-instance",
"context" : {
"subscriberName": []
},
"action": "optimize",
"resource": {
"scope": [],
"services": [],
"resources": [],
"geography": []
}
}
|
TOSCA Compliant Operational and Guard Policies Pamela Dragosh
...