VMware vCenter Server Appliance Not Ready for Prime Time

 
 
Cameron Sturdevant Cameron Sturdevant is the executive editor of Enterprise Networking Planet. Prior to ENP, Cameron was technical analyst at PCWeek Labs, starting in 1997. Cameron finished up as the eWEEK Labs Technical Director in 2012. Before his extensive labs tenure Cameron paid his IT dues working in technical support and sales engineering at a software publishing firm . Cameron also spent two years with a database development firm, integrating applications with mainframe legacy programs. Cameron's areas of expertise include virtual and physical IT infrastructure, cloud computing, enterprise networking and mobility. In addition to reviews, Cameron has covered monolithic enterprise management systems throughout their lifecycles, providing the eWEEK reader with all-important history and context. Cameron takes special care in cultivating his IT manager contacts, to ensure that his analysis is grounded in real-world concern. Follow Cameron on Twitter at csturdevant, or reach him by email at cameron.sturdevant@quinstreet.com.
By Cameron Sturdevant  |  Posted 2011-09-02 Email Print this article Print
 
 
 
 
 
 
 

va12

Although initial results were good, we ran into trouble when the new vCenter Server appliance started falling over every night.

First, to be clear, vSphere 5.0 has two choices for implementing vCenter Server. One works, and one still needs some work.

The vCenter Server that works is the traditional vCenter as it has been shipped for several versions of vSphere. This version is installed on a Windows Server system. It works, so there isn't much more to be said, except that this is the version that I recommend to IT managers.

The new vCenter Server Appliance, which is imported from an OVF and is a virtual machine running on SUSE Linux has not worked well in eWEEK Labs tests. In the comings and goings of looking at the other new features in vSphere 5.0 and with new versions of the appliance becoming available throughout the testing process, I didn't see a stability problem until this week. You can read my vSphere 5.0 review at eWEEK.com Basically, the vCenter Server Appliance service stopped every night, and sometimes several times during the day. Hitting the "update" button brought down a 4GB update. There is very little documentation for the appliance. And our troubles were complicated by the fact that vSphere 5.0 was released at the start of VMworld in Las Vegas. For those reading this posting in the future, I'm filing this on the Friday before Labor Day.

Thus, the release of the first version of vCenter as an appliance occurred in a perfect storm of circumstances that thwarted a good first experience.

As of today, eWEEK Labs has fallen back to the traditional vCenter installed on a Windows Server installation. I think the virtual appliance is a good idea but at this time I cannot recommend using it.

 
 
 
 
del.icio.us | digg.com
 
 
 
 
 
 

Submit a Comment

Loading Comments...

 
 
Manage your Newsletters: Login   Register My Newsletters























 
 
 
 
 
 
 
 
 
 
 
Rocket Fuel