latoga labs

Alliances & Partnership Advising

© 2006–2025 · Log in

Getting Ready for VMworld 2010 (Are You?)

Leave a Comment

VMworld 2010 Banner
VMworld 2010 San Francisco is set to start in just four weeks (August 30th – September 2nd).  This year’s VMworld is already shaping up to be a killer event.  Compared to last year’s VMworld, I personally am seeing a 500+% increase in the number of clients of mine who are signed up to attend.  The reasons for this are multiple:

  • Increased demand for virtualization within my clients
  • Expansion from core virtualization (server consolidation) to virtualization to drive business efficiency
  • Planning and deployment of internal private clouds
  • Increased activity in desktop virtualization to help reign in desktop costs and provide a more dynamic and managable desktop environment

If you’re planning on attending VMworld this year, here are a few bits of advice:

  • Browse through the VMworld FAQ soon as possible
  • Use the Schedule Builder early to get into the sessions you want (ever year I hear from clients that the couldn’t get into the sessions they wanted, plan ahead and book early!)
  • The breakout sessions and labs this year are all Self Paced, no need to preregister for anything.  Just show up, pick a technical session from the menu and the environment will be dynamically provisioned for you in the VMworld Cloud.  This is similar to the environment that was used for the VMware Internal Technical Summit earlier this year and I think all VMworld attendees will be amazed by it…  (I’m hoping the Lab Team has the same real time lab cloud portal which shows how many labs are running at any give time, it was mesmerizing to watch.)
  • Make sure you reach out to your VMware account team or TAM (if you have one) and let them know you’re going.  There are lots of opportunities for more direct 1-on-1 conversations that we can arrange, but only if we have time in advance to do it.
  • Bring with some snack bars…there is so much to do and see, I am sure you’ll completely forget about lunch at least one day if not more…

I’ve also been asked by a number of people if I was going to do another VMworld Portrait Project again this year.  Sadly, I won’t be able to.  This year I will be on stand by during all of VMworld as my wife and I are expecting our first born and his due date is right around VMworld.  I’m also planning on taking a few weeks off once he arrives to help adjust to family life, which will make it impossible to quickly turn around photos for people.  What this all means is no portrait project this year…we’ll see what next year looks like.  (I may be walking the halls with camera in tow, so smile if you see me pointing it in your direction!)

vSphere 4.1 Hidden Gem: Host Affinity Rules

Leave a Comment

During the vSphere 4.1 beta period, two of my clients were very interested in the new Host Affinity Rules for issues they were having.  The day vSphere 4.1 was released I had a call to discuss Host Affinity Rules with another client to explore issues they were having that host affinity rules could solve.  Each of these global enterprise clients are running 1000’s of VMs in production and each have different uses for Host Affinity Rules that the average user may overlook.

I was planning on providing a quick overview of the Host Affinity Rules in this post, but Frank Denneman already provided a great overview that I can’t really improve on.  Start with his post to to understand the basics of the new Host Affinity Rules.

A few Host Affinity Rule use cases:

  • Physical server based software licensing:  As hard as it is to believe, some software vendors still tie their software to physical computers.  Using Host Affinity rules allow you to purchase licenses for a subset of your physical servers in your vSphere cluster. (typically 2 so you have HA).  By forcing the VMs running the software in question to run on specific servers, you can ensure compliance with the software licensing.
  • Isolation for troublesome VMs: as with most troubleshooting processes, the newest thing in an environment usually gets the blame.  For one of my clients this means that new workloads moved into the vSphere environment that have performance issues result in the application owners blaming vSphere for the performance issues.  Even after using something like vCenter AppSpeed to show the user where the performance problem exists in their application, app owners still won’t believe it until their VM is running by itself.  With Host Affinity Rules, you can force the problem-some VM to run on a server that has nothing else on it.  (Take that non-believer app owner!)
  • Another approach to host pinning and reservations:  Some clients use pinning and reservations to help ensure certain levels of performance for some of their end users.  Like any over-riding control, you can eventually end up with more of these rules than can be realistically managed.  Host Affinity rules could be used in their place by forcing a more large grained control.  Of course, the same rule sprawl can occur with host affinity rules.  So it’s best to use them sparingly at first and really make sure the end users really need them before using them.  After all, cloud computing is supposed to make things easier for both end users and IT administrators…fight the gravitational pull of end user special needs.  More often than not these needs don’t really exist.

VMware Releases vSphere 4.1 & Licensing Changes

1 Comment

Today is the big day that vSphere 4.1 is finally released. This dot release is jam packed with new features that some of my clients have been testing for the past six months in beta. The ones that have been strongly received by my enterprise clients include:

  • Increased vSphere scalability (2-3x increase in vCenter scale, see config maximums pdf for details)
  • Storage IO Control (SIOC)
  • Additional Storage Statistics in vCenter
  • NFS Performance Enhancements
  • Network IO Control (NIOC)
  • VMware HA Healthcheck and Operational Status
  • Host Affinity Rules
  • vMotion Enhancements (5x better vMotion performance, note that small v… 🙂 )
  • Memory Compression
  • USB Device Passthrough from an ESX/ESXi Host to a Virtual Machine (a peer of mine said he was amazed at how every USB device he could think to throw at it just work, though I’m sure someone will find exceptions to this.)

There was also some changes in the vSphere licensing. Specifically formalization of vSphere Kits and Editions:

  • Kits are pre-packaged for specific use case needs.
  • Editions are the different tiers of of increasing product capability to cover the spectrum from small businesses to global enterprises. There were some feature changes between Editions as well.

vSphere 4.1 Editions

Update: Here is Steve Herrod’s blog post on this release as well as Bogomil Balkansky’s blog post.  I also forgot to mention that free ESXi is now being referred to as vSphere Hypervisor, the first tier in the above diagram.

Additional product releases coinciding with vSphere 4.1:

  • vCenter Site Recover Manager (SRM) 4.1 was released today as well.  This version of SRM is compatible with vSphere 4.1 and contains a number of new features, see release notes.
  • VMware Studio 2.1 was released today as well.  This version is compatible with vSphere 4.1 and adds support for new Linux GOS and OVF versions as well as a slew of other features, see release notes.
  • vCenter Server Heartbeat 6.3 was release today as well.  This version is compatible with VC 4.1 as well as additional features, see release notes.