vCloud Director – automating tenant and resource deployment with Orchestration Models
Our vCloud Director portal is designed to simplify vCD for you and your customers – so it’s easier for you to sell resources, and easier for your customers to buy them.
In this post I want to talk about one of the ways we make that happen, by giving you more control of the way you allocate and deploy resources for tenants.
One of the drawbacks of vCloud Director is that creating a tenant’s Organisation VDC is a long process that involves a LOT of wizards – and you have only a limited ability to allow your customers to create their own VDCs.
In many cases you would not want to do this – but what if they had access to a specific set of predefined VDCs to choose from, like Small, Medium or Large? Or High Performance and Standard Performance? Or even different regions?
We wanted to make this whole process faster and more flexible. What we came up with was Orchestration Models. They’re a way to pre-package a complete set of resources for your tenants, so deployment can be fully automated. With Orchestration Models you can give more control to your customers, by allowing them to buy more resources when required with less input from you. That makes life easier for your sysadmins too.
Going beyond VDC templates
Isn’t this just the same as VDC Templates in vCloud Director? No, not really, although they both have a similar goal. Orchestration Models give you a much more granular approach, enabling you to give customers choice where you need to.
For example, you can create a completely pre-defined template, with no customizable options for your customers or sysadmins. Or you could decide that you will not let them choose where to place the resource pool, or what networks to create… but you would like them to be able to set CPU and Memory within a given limit.
Here’s what it looks like in OnApp. In this example, we have fixed most of the Compute values, and removed them from view during deployment. We have enabled CPU and Memory customization, but within set minimum and maximum limits:
Easy VDC creation
Orchestration Models automate the process of creating Org VDCs. They don’t not rely on VDC templates: instead they are created and stored within OnApp. You have the ability to Create, Edit, Clone and Delete Orchestration Models, and define which models are available to a tenant through Buckets (our resource access control/billing system – check out Jim’s blog post for more information.)
Orchestration Model options
Here is a detailed list of customizable options within OnApp Orchestration Models:
- Compute Resource – which vCD Instance, ideal for providers with multiple vCDs
- Provider Resource Pool
- VDC Model Type – PAYG, Allocation, Reservation
- CPU Resource Guaranteed – PAYG, Allocation
- CPU Quota – PAYG
- vCPU Speed – PAYG, Allocation
- Memory resources guaranteed (%) – PAYG, Allocation
- Memory Quota – PAYG
- Number of VSs – PAYG, Reservation, Allocation
- CPU Allocation – Reservation, Allocation
- Memory Allocation – Reservation, Allocation
- Default Network Pool
- Edge Gateway – Yes/No
- Edge Gateway Name
- Networks to Create – Isolated, Direct and/or Routed
- Thin Provisioning – Enable/Disable
- Fast Provisioning – Enable/Disable
- Datastores to Create