VMworld is run on a killer ESX cluster(s) (So how’d it go?)

From a very interesting tweet:
@MeghanAtBMC: VMWorld infrastructure is running 37,248 VM’s on 776 ESX servers w/total of 37TB of Memory 348TB Storage

SWEET!!!

The next set of questions coming from someone that manages a datacenter:

Can we get a whitepaper/post mortem report on:

  • How this datacenter ran during the show?
  • What issues did you see?
  • What worked well?
  • How many VMotions happened?
  • How many HA events occurred?
  • How many IOPS occurred?
  • How many last minute change requests for more CPU, Memory, Disk, Extra VMs come through?
  • What kind of change management was in place for this?
  • What were the support policies?
  • How many admins were involved?
  • How many hack attacks occurred?
  • What kind of security issues were seen?
  • What kind of repair worked happened?
  • What was Lab Manager used for?  
  • What was View used for?  
  • What versions of everything that were used?  
  • Did you have any FT VMs?   How did they work?

Any other questions datacenter folks would be intersted in?  I know I’m just itching to know.

4 thoughts on “VMworld is run on a killer ESX cluster(s) (So how’d it go?)

  1. I’m interested in “Why?”

    Couldn’t a smaller, less power hungry infrastructure have provided the necessary demo capability? What was the average CPU utilisation of those 37000 VMs?

  2. Pingback: VMworld 2009 Virtual Infrastructure Design – Lab Manager vPODS Enable Conference Cloud | VM /ETC

  3. Pingback: VMworld 2009 Trends and Summary | It's Just Another Layer

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <pre lang="" line="" escaped="" highlight="">