I've worked in Big IT for 25 years. During that time I've worked with three major virtualization technology vendors: IBM, VMware, and Microsoft. I've learned the hard way about the implications of choosing one virtualization solution over another.
I'm forever grateful to IBM as their VM operating system was my ticket out of electrical engineering. I was working at Texas Instruments (TI), and I was a lousy "double-e." But I'd stumbled across a cubicle near mine that had a big IBM 3178 terminal and keyboard attached to a VM/SP system. It looked so different from the cheesy little discolored plastic minicomputer terminals that encircled it. It was industrial-strength looking, yet swoopy, with a keyboard so heavy it put a dent in your lap. Now this was computing. I started educating myself and eventually stepped over the line from knowledgeable VM user, to user consultant, and then to systems administrator. I eventually maintained all of TI's production VM systems that ran a number of company's factories.
I moved from the mainframe over to the client-server side of IT early on - back when it was still officially known as "the Client Server Project" - and left virtualization behind for a while. After all, Microsoft had Windows NT 3.1 in beta, their first real* operating system; it was too early in x86 architecture and OS development to think about virtualizing NT's resources . Before too long though, a company named VMware appeared on the market with its Workstation product. It was great for testing and lab work, a real must-have, but no one would have ever considered using it in full production.
During my tenure at Intel, we evaluated and then chose a VMware-only virtualization strategy. At the time when we had to make the decision, VMware had the more-complete product offering to meet our requirements. However, that decision left us with two issues to deal with: First, VMware was expensive, and sticking with the straight platform solution caused our virtualization deployment to be severely limited due to budget issues.
I was on the receiving end of this decision's negative implications: Some badly needed Active Directory recovery updates were put on indefinite hold because we didn't have the funding to pay for the VMware licenses. At the time, I resented not being able to implement a free solution (Microsoft Virtual Server) that did a perfectly adequate job of fulfilling my tactical requirements.
The second issue with VMware was related to virtualization management. Intel uses Microsoft's System Center suite to monitor its production systems, and it was no problem to add VMs to this solution. But the virtualization platform itself - ESX - required a separate management solution, which of course wasn't free. Naturally, the expense of managing the environment was factored into the overall virtualization platform decision. But the soft costs of heterogeneous management weren't. All in all, implementing a virtualization solution was quite expensive; it was only the fact that virtualization is such a huge cost-saver that made it workable.
Today, how much weight do you think you should given to unified management when you're considering virtualization solutions? How important is it? Are the disadvantages of supporting multiple vendors minor compared to the capabilities that having this heterogeneous environment provides? I'd like to know your opinion.
- Sean Deuby
* True 32-bit architecture, pre-emptive scheduling, with full virtual memory support