...
Resources Related to Policy
OOF Policy
...
Details
OOF-HAS Policy ExamplesPolicies
OOF-HAS
...
Service Design Policies.
Service design policies are typically defined as a part of a service design model and evaluated/enforced prior to the service instantiation phase. For example, Hardware Platform Enablement (HPA) policies are defined in an SDC service model and evaluated/enforced during the homing optimization process in ONAP.
The HPA requirements are captured in a VNF descriptor provided by a vendor. During the service-design phase, these requirements are extracted out from the VNF descriptor and captured in a service model. Some of the HPA requirements cannot be changed during the lifecycle of a service; while other optional requirements can be changed by a service designer or operator over time (e.g. the use of SR-IOV may be preferred by an operator if the SR-IOV capability is optionally provided by a vendor). Once a service model is designed and uploaded into the SDC repository, SDC notifies the policy service about the distribution of a new service model. The policy service then fetches the service model and extracts out the HPA requirements through model decomposition. Next, the policy service creates HPA policies for the homing service (OOF-HAS) by populating the HPA requirements in policy models provided by OOF, and stores the policies in a repository. When the homing service receives a homing request from SO, the homing service asks for the associated HPA policies from the policy platform. Finally, the homing service finds homing solutions based on the evaluation of theĀ received HPA policiesĀ and returns the solutions to SO.
Section |
---|
|
Column |
---|
| Code Block |
---|
language | js |
---|
theme | Eclipse |
---|
title | HPA Hyper-Threading Policy Example |
---|
linenumbers | true |
---|
collapse | true |
---|
| {
"service": "HPA_Hyper_Threading_Policy",
"policyName": "OOF_Beijing.vGMuxInfra",
"description": "Hyper threading policy for vGMuxInfra",
"templateVersion": "0.0.1",
"version": "ONAP_Beijing",
"priority": "3",
"riskType": "test",
"riskLevel": "2",
"guard": "False",
"content": {
"hyper_threading_properties": {
"cpu_cores": { "value": 4, "operator": "="},
"cpu_threads": { "value": 2, "operator": "="},
"cpu_threads_policy": { "value": "dedicated", "operator": "="},
"cpu_sockets": { "value": 2, "operator": "="}
},
"identity": "hyper_threading_vGMuxInfra",
"policyScope": {
"serviceType": ["vCPE"],
"geoRegion": ["US", "INTERNATIONAL"],
"networkType": ["ip"],
"resourceInstanceType": ["vGMuxInfra"]
},
"type": "HPA_hyper_threading",
"resourceInstanceType": ["vGMuxInfra"]
}
} |
|
Column |
---|
| Expand |
---|
title | Comments and Notes: HPA Hyper-Threading Policy Example |
---|
| The fields in this example policy are typically generated from a TOSCA service model specified by VNF vendors or service designers. |
|
|
OOF-HAS
...
Operation Policies
Section |
---|
|
Column |
---|
| Code Block |
---|
language | js |
---|
theme | Eclipse |
---|
title | Distance Policy Example |
---|
linenumbers | true |
---|
collapse | true |
---|
| {
"service": "DistancePolicy",
"policyName": "OOF_Beijing.DistancePolicy_vGMuxInfra",
"description": "Distance Policy for vGMuxInfra",
"templateVersion": "0.0.1",
"version": "ONAP_Beijing",
"priority": "3",
"riskType": "test",
"riskLevel": "2",
"guard": "False",
"content": {
"distance_properties": {
"locationInfo": { "value": "customer_loc"location", "operator": "="},
"distance": { "value": "500", "operator": "<", "unit": "km" },
"resourceInstanceType": { "value": ["vGMuxInfra"], "operator": "="},
},
"identity": "distance-bGMuxInfra",
"policyScope": {
"serviceType": ["vCPE"],
"geoRegion": ["US", "INTERNATIONAL"],
"networkType": ["ip"],
"resourceInstanceType": ["vGMuxInfra"]
},
"type": "distance"
}
} |
|
Column |
---|
| Expand |
---|
title | Comments and Notes: Distance Policy |
---|
| The fields in this example policy are typically generated from a TOSCA service model specified by VNF vendors or service designers. |
|
|
CMSO
...
Policies
TBD
Policy Fetching Modes
OOF can fetch optimzation policies using the getConfig API of the policy system. The policies can be searched and filtered in two different modes; by-name and by-scope from the policy system.
...