Scott Lowe’s post about the Storage VMotion GUI beat mine by a couple of hours. I don’t even have to post, because he said exactly what I was going to say. Including his comment at the end.
What bothers me most about Virtual Infrastructure 3.5 is that overall it is a step backwards. Sure, there are new features, but each new feature has some Achilles heel that makes it hard to use. The RCLI is a major problem, and any feature that relies on it suffers. ESX 3i? Not with the RCLI, and not until it is feature-identical to normal ESX 3.5. Storage VMotion? Neat, but there are two people in my organization that can do a storage migration now, and that’s it. I can’t, I won’t, roll this out to my operations staff, mainly because it’ll be a disaster. The document alone would be the single most convoluted document I’ve written in years, again because of the RCLI. Why isn’t that part of VirtualCenter? Update Manager? The first time I ran Update Manager I lost the ability to VMotion anything. I called support to report the problem and ended up having to fix it on my own. VirtualCenter 2.5? 30% of what I do in VirtualCenter 2.5 gives me errors, and when I repeat the same action it succeeds. Out of the box VMotion causes CPU spikes, which can be resolved with a workaround, but that workaround doesn’t seem to work for me. I opened a support case and was told to wait several days for the update to take effect. Are you kidding me? Instead I figured out my own way of getting it to work. I’m not even going to open a support case about my administrative network interfaces dropping out, because what’s the point? VMware support is useless. They’ll search the KB, tell me to reboot the ESX Server with running VMs on it, I’ll object, they’ll ask for a support dump and tell me they’ll get back to me, and I’ll fix it on my own as I do with everything else. Distributed Power Management? Actual round-robin multipathing? All listed as experimental, which is basically using released software as a beta test. Will I use them? Absolutely not.
Now, a single developer created a GUI for Storage VMotion, and it just solidifies what I’ve been thinking all along: every new feature is about half done, shoved out the door as fast as possible so that they could say they have it, with little thought about how people use the products and even smaller amounts of testing. At best the features don’t work right. At worst they compromise the basic functionality of the product, making it far less stable than Virtual Infrastructure 3.0 ever was, running on the same hardware. It’s disappointing. I was a huge VMware fan prior to this, and could be again, but the honeymoon is over. My partner is off cavorting with sexier things while I’m at home paying the bills and taking care of the kids. This marriage needs counseling; I just hope we can meet half way.