Caution: Articles written for technical not grammatical accuracy, If poor grammar offends you proceed with caution ;-)
There are two types of vSphere reservation within vCAC. Reservations against a vSphere host and reservations against vSphere clusters. In order to create either a vCenter server is required. To make a reservation against a vSphere host it cannot be part of a vSphere cluster. Unlike physical reservations when creating a vSphere reservation you do not need to consume the entire vSphere host or Cluster in one reservation. You can create multiple reservations against a vSphere resoruce consuming parts of it in each reservation. You also have the ability to over subscribe the vSphere host or cluster.
When creating a vsphere reservation you have the ability to reserve memory, storage, and determine what networks are available within the reservation. vSphere reservation also give you the ability to determine how workloads can consume the resources. This is achieved in a number of ways. The first of which is a reservation priority. The reservation priority allows you some control over how you consume your resources. Let’s say you have two reservations assigned to a business group. If you wanted workloads to fully consume one before being placed against the other you would give the different priorities. The one you would want to fill first would be say a priority of 1,and the other would be a priority of 2. If you want to fill them equally you would give them the same priority. This will cause vCAC to round robin the placement of the workloads.
You can also implement the same types of placement priority for datastores within the reservation using the priorities you associate to each datastore.
Creating a vSphere reservation
- Start by going to Infrastructure -> Reservations -> Reservations and from the “New Reservations” menu select Virtual then vSphere
- On the New reservation screen screen there is a few fields you will need to fill out. First select the Compute resource you would like to create the resource against. Next select the tenant you would like to assign the reservation to as well as the business group within the tenant. Finally you must set a priority for the reservation.
- Next on the resources tab you will select the amount of memory you want to reserve as well as the datastores you would like to reserve capacity capacity against along with the amount of disk space to reserve. You will also need to set a priority for each datastore you enable and reserve capacity against. Optionally you may also map the reservation to a vCenter resource pool.
- Next on the network tab you can select the networks you would like to make available to the reservation. On this screen you also have the ability to assign a network profile to the selected network. For more information on network profiles please send the network profile tutorial.
- Finally if you click on the alters tab and configure your desired thresholds and notification email address(es) and click ok to save the reservation.
3 Replies to “vCloud Automation Center – vCAC 6.0 Creating a vSphere Reservation”
I have a problem, when I reached the step of 3 above at the “Resource” tab – resources shows as “0” for both Memary and Storage. I’m sure Fabric Group set correctly, endpoints added with admin acct (same acct used to installed and configured everything) – even I tried different accounts etc but still when I go to Reservations I can see my (vSphere – vCenter) cluster lists in “Compute resource” (under “Reservation Information” tab) but it shows “0” values for everything when I go to “Resources” tab, no Storage listed either.
Any helps will be appreciated guys?
Cab you go to the compute resource and see the status of the data collection? It sounds like you are having an issue with the data collection finishing properly. Also do you see anything in the logs that can help lead to what the problem might be?
Thank you very much for the reply mate,
The status of the data collection is “on”, Proxy Agent status is “ok”. As you know there is a few errors in the vSphere agent log as usual, so not sure what errors I should be looking for?
Hopefully there is a solution for this?