...
- Cloud Agnostic Intent Execution Workflow
- 1) OOF → MC runtime check for a specific cloud region which can support capability/capacity/cost metrics (enhance current capacity check API appropriately)
- 2) MC processes request from OOF
- Retrieve target Cloud Region specific policy from "Policy"
- Evaluate each of the cloud specific options in the policy from a perspective of resource allocation, utilization and cost
- Return to OOF the option which minimizes <resource allocation, utilization and cost> and the net value of the option
- In case the requirement cannot be met, return appropriate error
- Cache the option in MC for the specific cloud region as part of the VNF deployment workflow
- 3) OOF processes request from MC and picks the target cloud region which maximizes the net value
- 4) SO → MC VNF deployment request is processed by MC
- MC looks up the cache for the target cloud request with the VNF deployment request details
- MC replaces appropriate details in the cloud specific template (Heat, ARM etc.) based on the chosen option in the cache
- MC deploys workload on target cloud region with dynamically modified cloud specific template
- MC removes the cache entry for the specific cloud region for the specific VNF deployment
Gliffy Diagram name Cloud Agnostic Intent Execution Workflow pagePin
name | Cloud Agnostic Intent Execution Workflow |
---|---|
pagePin |
...
14
14 |
Cloud Resource Partitioning for Differentiated QoS
...