...
- Multi-Cloud Policy Framework
- Assist OOF in target cloud region selection for VNF placement (aka homing) by summarizing cloud-specific capability, capacity & cost metrics (e.g. VMs could have different cost in different clouds, Infra High Availability (HA) for VMs in a VNF could have different cost in different clouds)
Cloud Agnostic Intent (Policy) Execution Workflow - Steps 1- 6
- Dynamically modify the cloud specific VNF deployment template based on cloud-specific realization of the specified intent (e.g. Infra HA for VMs within a VNF could have different realizations across different clouds)
Cloud Agnostic Intent (Policy) Execution Workflow - Step 7
- Assist OOF in target cloud region selection for VNF placement (aka homing) by summarizing cloud-specific capability, capacity & cost metrics (e.g. VMs could have different cost in different clouds, Infra High Availability (HA) for VMs in a VNF could have different cost in different clouds)
Intent Support
Single realization option per Cloud Region for the specified Intent
- Major Impact Projects:
- Multi-Cloud (Highest), OOF
- Minor Impact Projects:
- A&AI, SO
- End-to-end use case demonstration:
- vCPE, vDNS
...
| Code Block | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
{
"service": "cloudSelectionPolicy",
"policyName": "oofMulti-cloudCasablanca.cloudSelectionPolicy_vCPE_VNF",
"description": "Cloud Selection Policy for vCPE VNFs",
"templateVersion": "0.0.1",
"version": "oofMulti-cloudCasablanca",
"priority": "3",
"riskType": "test",
"riskLevel": "2",
"guard": "False",
"content":
{
{//new in R3
"cloudOwner": "All", //can be a specific cloud owner such as Azure, VMware VIO, Wind River Titanium Cloud etc.
"cloudRegion": "All", //can be a specific cloud region for a cloud owner
"cost-intent":
{
"dollarCostEvaluationVM-Type": "TRUE", //evaluate dollar cost per VM type if operator has configured a policy
"dollarCostEvaluationVM-FeatureGroup": "TRUE"
//evaluate dollar per feature/group of features if operator has configured a policy
//deployment-intent will be mapped to a cloud-specific realization which will be mapped to a feature group.
}
},
{//new in R3
"cloudOwner": "VMware VIO", //can be a specific cloud owner such as Azure, VMware VIO, Wind River Titanium Cloud etc.
"cloudRegion": "All", //can be a specific cloud region for a cloud owner
"deployment-intent":
{
"name": "Infrastructure Resource Isolation for VNF",
// realization possible without dedicating CPU and Memory, refer to section on "Cloud Resource Partitioning for Differentiated QoS"
// on how this can help in offering tiered services
"qosProperty":
{
{"Burstable QoS": "TRUE", "Burstable QoS Oversubscription Percentage": "25"}
}
}
},
{//new in R3
"cloudOwner": "All", //can be a specific cloud owner such as Azure, VMware VIO, Wind River Titanium Cloud etc.
"cloudRegion": "All", //can be a specific cloud region for a cloud owner
"deployment-intent":
{
"name": "Infrastructure High Availability (HA) for VNF",
}
},
}
"resources": ["vgw", "vgmux"], //"vgw" is also interchangeably used as "vg"
"applicableResources": "any",
"identity": "cloud-atrributes",
"policyScope": ["vCPE", "US", "INTERNATIONAL", "ip", "vgw", "vgmux"],
"policyType": "AllPolicy"
} |
...
| Code Block | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
//flexibility of having cloud owner and region in the new API provides fine grained control, addresses capacity/cost differences across different //cloud owners/regions and ensures backward compatibility
OOF -> MC
{
"VNFC": "vgw", //"vgw" is also intechangeably used as "vg" //new in R3
{//new in R3
"cloudOwner": "All", //can be a specific cloud owner such as Azure, VMware VIO, Wind River Titanium Cloud etc.
"cloudRegion": "All", //can be a specific cloud region for a cloud owner
"cost-intent":
{
"dollarCostEvaluationVM-Type": "TRUE", //evaluate dollar cost per VM type if operator has configured a policy
"dollarCostEvaluationVM-FeatureGroup": "TRUE" //evaluate dollar per feature/group of features if operator has configured a policy
}
},
{//new in R3
//evaluate dollar per group of features if operator has configured a policy
//deployment-intent will be mapped to a cloud-specific realization which will be mapped to a feature group.
}
},
{//new in R3
"cloudOwner": "VMware VIO", //can be a specific cloud owner such as Azure, VMware VIO, Wind River Titanium Cloud etc.
"cloudRegion": "All", //can be a specific cloud region for a cloud owner
"deployment-intent":
{
"name": "Infrastructure Resource Isolation for VNF",
// realization possible without dedicating CPU and Memory, refer to section on "Cloud Resource Partitioning for Differentiated QoS"
// on how this can help in offering tiered services
"qosProperty":
{
{"Burstable QoS": "TRUE", "Burstable QoS Oversubscription Percentage": "25"}
}
}
},
{//new in R3
"cloudOwner": "All", //can be a specific cloud owner such as Azure, VMware VIO, Wind River Titanium Cloud etc.
"cloudRegion": "All", //can be a specific cloud region for a cloud owner
"deployment-intent":
{
"name": "Infrastructure High Availability (HA) for VNF",
}
},
{//new in R3 + R2
"cloudOwner": "OpenStack", // new in R3,
// different cloud owners may need different capacities for the same VNFC because of implementation differences
"cloudRegion": "All", // new in R3,
// different cloud regions for a cloud owner may need different capacities for the same VNFC due to different SW
// versions and HW configuration
"capacityProperty": //same as R2, presence of this means capacity check needs to be done for the <cloud owner, cloud region>
{
"request":
"{\"vCPU\": {\"quantity\": {\"get_param\": \"REQUIRED_VCPU\"}, \"Memory\": {\"quantity\": {\"get_param\": \"REQUIRED_MEM\"},
\"unit\": \"GB\"}, \"Storage\": {\"quantity\": {\"get_param\": \"REQUIRED_DISK\"}, \"unit\": \"GB\"}}"
}
},
}
//return netValue per <cloud owner, cloud region>
//cloud regions which fail capacity check are not in this list
MC -> OOF
{
{
"cloudOwner": "OpenStack",
"cloudRegion": "1",
"netValue": "99"
},
{
"cloudOwner": "VIO",
"cloudRegion": "5",
"netValue": "100"
},
{
"cloudOwner": "Azure",
"cloudRegion": "3",
"netValue": "101"
},
} |
| Code Block | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
//
//Policy relevant to MC Azure Plugin
//
//<Service, VNFC> to instanceType Mapping
{
{
"Service": "vCPE"
"VNFC": "vgw", //"vgw" is also intechangeably used as "vg"
"cloudOwner": "Azure",
"instanceType": "x1"
}
}
,
"AvailabilitySetFeatureGroup": "G1" //availability set is a realization of the Intent "Infra High Availability (HA) for VMs in a VNF"
}
}
//workload deployment cost for instance type per cloud region
{
{
"cloudRegion": "5",
"instanceType": "x1",
"featureGroup": "G1",
"workloadDeploymentBaseVMCost": "100",
"workloadDeploymentFeatureGroupCost": "0"
},
{
"cloudRegion": "10",
"instanceType": "x1",
"featureGroup": "G1",
"workloadDeploymentBaseVMCost": "120"
"workloadDeploymentFeatureGroupCost": "0"
},
} |
5a) MC Processing (need MC code changes)
...
"Workload Deployment Cost Policy Example" depicted above has an exemplary description of this.For R3, to simplify implementation, all the features needed for cloud-specific realization of the deployment-intent are assumed to have no additional cost.
5. MC → OOF – Return a net value for each <cloud owner, cloud region> if the capacity check succeeds
...