...
- Use Cases for Integration testing
- vCPE
- In the current state, this use case cannot support the intent "Infra HA for VMs in a VNF"
- This use case has been tested in R2 with OOF↔MC capacity check API
- vDNS
- Can support intent "Infra HA for VMs in a VNF" and "Infrastructure Resource Isolation for VNF"
- Nothing additional needed in OOF or MC
- Changes needed in SO to call OOF API
- Matti to follow up with Shankar
- Srini to follow up MarcusMarcus from Intel is driving this
- vCPE
- Policy DB – is there any restriction on the type of json objects that can be stored?
- Matti to follow up with Ankit
...
- Deployment-Intent
- 1. "Infrastructure Resource Isolation for VNF" – { "qosProperty": { {"Burstable QoS": "TRUE", "Burstable QoS Oversubscription Percentage": "25"} } }
- Casablanca Plan
- Only certain pre-defined over-subscription values are allowed to reflect practical deployment and simplify implementation
- Dublin & Beyond Potential Plan
- Creating instance types on demand for private clouds - to study
- Casablanca Plan
- 2. Cloud-agnostic Workload Deployment Policy (Intent)
- Casablanca Plan
- Cloud-Agnostic Workload Deployment Policy (Intent) can be directly mapped to specific realization (e.g. OpenStack Flavor, Azure Instance Type) to simplify implementation.
- Dublin & Beyond Potential Plan
- VIM Capability Discovery to populate Intent in A&AI (similar to HPA label discovery supported since R2)
- VIM selection – Intent to be populated in A&AI for capability matching
- VIM Deployment realization - Intent to specific realization mapping (e.g. OpenStack Flavor, Azure Instance Type) to be populated in A&AI
- VIM Capability Discovery to populate Intent in A&AI (similar to HPA label discovery supported since R2)
- Casablanca Plan
- 1. "Infrastructure Resource Isolation for VNF" – { "qosProperty": { {"Burstable QoS": "TRUE", "Burstable QoS Oversubscription Percentage": "25"} } }
- Policy-based & cloud-selection
- 3. Tenant Information is not passed in the OOF → MC API
- Casablanca Plan
- The tenant information is derived from a simple mapping function per <cloud owner, cloud region>
- A simple mapping would be a tenant per <cloud owner, cloud region> as part of Multi-VIM plugin configuration.
- Need to make sure that this scheme is synchronous with the SO → MC API path
- The tenant information is derived from a simple mapping function per <cloud owner, cloud region>
- Dublin & Beyond Potential Plan
- Pass Tenant Information per <cloud owner, cloud region> in the OOF → MC API
- Casablanca Plan
- 4. VM Instance type/VM Feature Group dollar-cost-based cloud selection
Casablanca Plan
- By default, the workload deployment cost is computed as a fixed cost per plugin
VM Instance type/VM Feature Group dollar-cost-based cloud selection is
optional for all Multi-Cloud Plugins
If a Multi-Cloud Plugin does not support cost based on "dollarCostEvaluationVM-Type" and/or "dollarCostEvaluationVM-FeatureGroup"
- The workload deployment cost is computed as a fixed cost per plugin
- By default, the workload deployment cost is computed as a fixed cost per plugin
Dublin & Beyond Potential Plan
- Deep dive further on dollar-cost-based cloud selection models/implementation for public/private clouds
- Deep dive further on dollar-cost-based cloud selection models/implementation for public/private clouds
- 3. Tenant Information is not passed in the OOF → MC API
...