You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 8
Next »
Contents
Summary
Introduction
The OOF retrieves applicable constraints and objective functions as policies from the policy platform. These policies are retrieved at runtime, thus allowing an operator to change policies as and when needed. These policies are specified using available policy models in the policy platform. The OOF-related policy models are typically generated from models specified by VNF vendors, service designers, and site administrators. Currently, for R2, these models will be pushed into the policy platform manually using the OOF policy uploader module.
The OOF relies on the following features of the policy platform: (a) policy specification (typically based on policy models for constraints and objectives), (b) policy prioritization (typically for the same policy name, each with different priorities), and (c) querying of policies based on different criteria (e.g. by scope, by name patterns, etc.)
OOF Policy Examples
OOF-HAS Policy Examples
OOF-HAS VNF Attribute Policies.
{
"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"]
}
}
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.
{
"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": "customer_loc",
"distance": { "value": "500", "operator": "<", "unit": "km" },
"resourceInstanceType": ["vGMuxInfra"]
},
"identity": "distance-bGMuxInfra",
"policyScope": {
"serviceType": ["vCPE"],
"geoRegion": ["US", "INTERNATIONAL"],
"networkType": ["ip"],
"resourceInstanceType": ["vGMuxInfra"]
},
"type": "distance"
}
}
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.
OOF-HAS Service Policies
CMSO Policy Examples