The Virtualization Room

Mar 24 2008   4:20PM GMT

Happy new version, VMware!

Kutz Profile: Akutz


Warning: The following blog post contains biting sacarsm and marginally humorous commentary that may offend sensitive VMware executives. Reader discretion is advised.

An open letter to VMware:

Hey VMware, it’s me again. I know you’re probably still mad at me for last week. Well, I’m going out on a very public limb here to apologize for something that I did.

I’m sorry that I forgot your version.

Yes, you let everyone know that your version was coming up, but I forgot to create a calendar reminder for it and I just plain forgot. You know how that goes, right?

Now I don’t mind owning up to my bad memory, but here’s the thing — you have sooo many versions! Most people just have one version per year, you have at least five. There’s the version for VMware Infrastructure (VI), currently at 3.5. ESX is already 3.5 versions old, and ESX 3i has its own version too. Then there is the VirtualCenter and the VI client at 2.5. VMware Consolidated Backup (VCB) is straggling behind at 1.1. I think the VI SDK is also 2.5 versions old, but with the VI Perl Toolkit at version 1.5 and the VI Toolkit (for Windows) in beta, it is hard to keep up.

VMware, your enterprise portfolio has expanded far beyond simply ESX, and none but two of the versions align. Therefore, with so many available products, it is fast becoming impossible to understand which version works with which. You should release minor point releases between major revisions in order to maintain a consistent major version number for your enterprise product offerings.

I know you’re a busy company, and it is hard to get everybody together on one day out of the year to celebrate your version, but I beg you, please try. Except for those closest to you, it is getting extremely difficult to remember your versions, or figure out which version we actually mean. Here’s an idea: for the rest of the year, skip all of your versions and then start over your versions all at once on a single day. Maybe even at VMworld? It can be your special version day. I’ll even bring party hats and cake (if you will invite me.)

VMware Infrastructure 4 (VI4) can include:

– ESX 4
– ESX 4i
– VirtualCenter 4
– VI SDK 4
– VI Perl 4
– VI Toolkit (for Windows) 4
– VCB 4

I know it will throw people off at first; your customers might think they missed some of your versions. However, I think in the end you’ll have a lot of people thanking you.

I feel real bad about missing your version, and I don’t want to let the announcement pass me by again. Maybe I should use Outlook?

6  Comments on this Post

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when other members comment.
  • Jose
    it is the same with windows (how many versions?) do you identify know the citrix products??? may be VMware is innovating you know btw, I am an independent consultant, and a really know all the virtualization products (VMware, Citrix, VirtualIron, OracleVM, SunxVM, Virtualbox, etc)
    0 pointsBadges:
  • Schley Andrew Kutz
    If Hyper-V or XenServer start having version nuttiness I'll call them out too.
    0 pointsBadges:
  • jtroyer
    I think the haters of this article need to get a sense of humor. Andrew, you forgot updates - Converter is at 3.0.2 Update 1, and if you haven't updated to ESX 3.5, you are running ESX 3.0.2 Update 1 and VC 2.0.2 Update 3. Where's the VC plugin that can track this? This is a critical gap in our platform!
    15 pointsBadges:
  • Inaki Borrero
    Yes, it is a funny article, and there is some truth about it: too many releases in too short and new products... kind of messy. Btw, also Converter 4.0 for cold migration skipped! ;-) Anyway I believe it is a great product, as long as you only use what you really need!
    0 pointsBadges:
  • jamie
    so we run 90% percent vi where i work (15 hosts, 60-somethign vm's. i can relate to this. i hate the version crap, so do the server admins i have to explain them to. wtf? i agree, get the heck on the proper versioning bandwagon. (and dont ask about licensing. academic and enterprise, talk about one messsed up vmlic.lic file! :( jp
    0 pointsBadges:
  • emzy
    I don't know about SDK or VCB, but in VI4 VC and ESX are using the same version ---> 4
    0 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

Share this item with your network: