My post on vCloud Director Allocations Models back in September 2010 has always done fairly well in terms of view/visits. Lately I have been receiving some offline questions about how valid this article still is with vCloud Director 1.5 so I decided to go through the same exercise here. Instead of doing a full copy I will just copy and paste the characteristics section for each of the three different Allocation Models. For those who can’t be bothered the short summary is, nothing has changed… I only discovered something which I did not notice the first time around.

Allocation Pool

No changes have been introduced with vCloud Director 1.5 compared to 1.0 for the “Allocation Pool” allocation model. Below are the characteristics of this allocation model and the resource pool / vm construct used on the vSphere layer:

• Pool of resources of which a percentage will be guaranteed
  • A reservation will be set to guarantee resources on a resource pool level
  • By default the resource pool reservations on CPU is 0% and memory 100%
  • Tenant has a guaranteed set of resources and has the ability to burst to the upper limit
  • The resource pool is not expandable!
• VM Level characteristics
  • No reservations or limits set on a per VM level for CPU
  • Reservations set on a per VM level for memory. This reservation is based on the percentage of guaranteed resources.

Pay-As-You-Go

Nothing has changed for Pay-As-You-Go either. I slightly changed the wording though to make it more obvious what happens on a vSphere layer:

• Percentage of resources guaranteed on a per VM level
  • A reservation and a limit will be set on a VM level
  • By default the VM reservation on CPU is 0% and memory 100%
  • By default the vCPU speed is set to 0.26GHz, which means you vCPU will be limited to 0.26GHz
• The Org vDC resource pool is just an accumulation of all reservations set on a per VM level
• Note that this will include the memory overhead per VM!
• The resource pool is set to expandable

Reservation Pool

When looking at the vSphere layer it appears that not much has changed. The characteristics are still the same from a Resource Pool and virtual machine perspective… However I spotted something which was apparently already part of vCoud Director 1.0 but somehow I missed this. vCloud Director 1.x offers you the capability to add a reservation for CPU and memory and even allows you customize the shares! None of the other allocation models allow you to do this!

• Fully guaranteed pool of resources
  • A reservation will be set to guarantee resources on a resource pool level
• No reservations or limits set on a per VM level for CPU
• Note that is is possible to set a reservation/limit for CPU or Memory with vCloud Director 1.x on a per VM level. See screenshot below, this is configurable on a per virtual machine basis!

Although this is documented on page 59 of the excellent Evaluators Guide I figured it wouldn’t hurt to write a tiny blog post. I found myself googling for it multiple times already with no succes, so there must be more people facing that “problem”. Below you can find the passwords of the vCloud Director Appliance and the embedded database, just in case you need it:

• VMware vCloud Director Appliance:
  username = root
  password = Default0
• VMware vCloud Director Appliance/Oracle Database 11g R2 XE instance:
  username = vcloud
  password = VCloud

Bilal Hashmi wrote a nice article about HA today and in this article he asked a couple of questions. As I think the info is useful for everyone I decided to respond through a blog article instead of by commenting.

Let me start by saying that in general HA should never be disabled. The later versions of vSphere have a neat option called “Enable Host Monitoring”. This option should be used for scheduled network maintenance. The difference between disabling host monitoring and disabling HA is that disabling host monitoring does not cause a full reconfiguration (see screenshot below) of HA and a new election process. Just the “host monitoring” functionality is disabled, which is what you want in this scenario.

Bilal asked multiple questions / made multiple statements in his article, I will respond to two of these specifically to explain the way HA handles failures/isolation:

In this case within 30 sec of the management network outage, each host would have declared itself isolated and wont attempt to restart any VMs like the primaries would in vSphere 5.

So why is this? As soon as a Master is isolated it will drop “ownership” of datastores on which VMs are running that are part of its cluster. Before the other hosts trigger the isolation response for a given VM they will validate if the datastore on which this VM is stored is “owned” by a master. In the case of a cluster wide isolation due to a network outage / maintenance the ownership would be dropped and this would result in HA not triggering the isolation response. This is a major change compared to vSphere 4.x and prior!

Now what happens when the network outage is over and the hosts are in a position to talk to each other? I have not been able to find documentation on whether an isolated host will enter an election (vSphere 4 or 5) ones the communication channel is open and bring the cluster back to life.

Lets focus on vSphere 5.0 as that seems most relevant. A host remains isolated until it observes HA network traffic, like for instance election messages OR it starts getting a response from an isolation address. Meaning that as long as the host is in “isolated state” it will continue to validate its isolation by pinging the isolation address. As soon as the isolation address responds it will initiate an election process or join an existing election process and the cluster will return to a normal state.

There’s absolutely no need to manually intervene. HA takes care of all of this for you.

Yes, it is that time of the year again… vSphere-land.com’s voting for the Top 25 Blogs worldwide has started again. I had the honor of placing 1st four consecutive times, but the competition is huge this year with excellent newcomers like Chris Colotti, scripting warriors like William Lam and Alan Renouf and of course my long time rival/friend Chad Sakac.

I am hoping each of you will select the top-10 blogs based on quality, longevity and frequency. (I personally find length of the article irrelevant, content is King!) I did want to list my top 10 articles over the last 12 months:

1. The vSphere 5.0 – HA Deepdive
2. Using vSphere Auto-Deploy in your home lab
3. Multiple-NIC vMotion in vSphere 5…
4. esxtop
5. vSphere 5.0: Storage vMotion and the Mirror Driver
6. vSphere 5.0: What has changed for VMFS?
7. HA Architecture Series (1 – 5)
8. “Hacking” Site Recovery Manager (SRM) / a Storage Array Adapter
9. ESXi 5.0 and Scripted Installs
10. vSphere 5.0 vMotion Enhancements

The voting is very straight forward and will only take 2 minutes of your time, all you have to do is select your Top 10 favourite VMware related virtualization blog sites and then sort them in your order of preference (ie: 1 – 10) – it’s as easy as that! Don’t wait any longer, cast your vote now!

It took us a while to figure this one out, but finally we managed to create a proper epub version of our book. Converting from Kindle to iBooks / Nook is not easy, but after using multiple tools and manually editing the book using Sigil we managed to create version which was submitted to the iBooks store and Barnes & Nobles a couple of weeks ago. This morning I noticed that the book has been made available. So for all those who have been asking about it, here are the links:

• iBook – $ 9.99
• Nook – $ 9.99

We hope you will enjoy it!

A couple of weeks back I posted my session details for PEX. I just had a session added to my schedule which I wanted to inform you about. This session was originally hosted by no one less than Mike DiPetrillo. Chris Colotti and I have been asked to take over the session.

Session 1262 (Wednesday 2/12 @ 12:30pm): DR of the Cloud and to the Cloud

This session will look at DR and the cloud. Two different DR scenarios will be presented in depth – DR of the cloud and DR to the cloud. DR to the cloud is how end consumers fail over resources to a cloud provider. DR of the cloud is how you fail over cloud resources from one site to another. This session will go in depth on the consumer and provider side of the architecture. We’ll look at how to replicate the data, what applications are primary targets, how to size environments, how to maintain multi-tenancy, and what to avoid when architecting these solutions. This session is a must for anyone considering tier 1 applications for the cloud.

Presenters: Chris Colotti and Duncan Epping

Don’t forget to add it to your schedule, it is going to be a really cool session!

I was just reading some of the comments posted today and Marc Sevigny, one of the vSphere HA developers, pointed out something which I did not know. I figured this is probably something that many are not aware of so I copied and pasted his comment:

Another thing to check if you experience this error is to see if you have jumbo frames enabled on the management network, since this interferes with HA communication.

This is document here in a note: http://kb.vmware.com/kb/2006729

To make it crystal clear: disable jumbo frames on your management network with vSphere 5.0 as there’s a problem with it! This problem is currently being investigated by the HA engineering team and will hopefully be resolved.

<Update> Just received an email that all the cases where we thought vSphere HA issues were caused by Jumbo Frames being enabled were actually caused by the fact that it was not configured correctly end-to-end. Please validate Jumbo Frame configuration on all levels when configuring. (Physical Switches, vSwitch, Portgroup, VMkernel etc)</Update>