VMware ESX Server 3.5
By Paul Venezia | InfoWorld | Published: 01:00, 11 February 2008
Fun with virtual servers
VMware admins will notice a few new things straight away with VirtualCenter 2.5. First on that list are the annoying splash screens that now adorn most of the elements in the VMware Infrastructure Client. They're designed to be large, friendly displays with links to the most common tasks, but for anyone who's used VI3, they're not useful. However, you can turn these off.
Beyond that annoyance, the new VirtualCenter is almost identical to the previous iteration in form and function, with some new buttons linking to the new features. There is one significant departure from the previous version that's worth noting: a new plug-in architecture. By implementing this, VMware has broadened the scope of what VirtualCenter can accomplish, and potentially opened the door to integrating third-party tools into the overall management infrastructure.
The big Consolidation button at the top of the new VC client is an obvious starting point. VMware has integrated its Capacity Planner code into VC2.5, allowing admins to gauge the impact of virtualising existing physical servers without leaving the console. Coupled with VMware's physical-to-virtual (P2V) conversion tools, this is a built-in method of doing either piecemeal or wholesale migrations of an existing data centre. Although plenty of third-party tools do P2V and migration planning, having these tools built into VC2.5 is handy for many smaller infrastructures.
This feature, which requires administrator-level credentials for Windows systems, will discover servers on specified subnets and monitor their utilisation and performance over time. Following this period, reports can be produced that will provide guidance in selecting physical servers ripe for virtualisation, and provide a better picture of the overall utilisation of an existing infrastructure.
Although too much data can be a bad thing, it's generally not a bad idea to get as many viewpoints on actual server performance as possible when making these decisions. These new consolidation tools will be welcome in many IT departments.
Update Manager, descended from Shavlik's HFNetChkPro, is another big addition to VC2.5. Update Manager not only provides a control panel for applying updates and patches to groups of VMs, either ad hoc or on a scheduled basis, but can automate the entire process, taking a snapshot of the VM prior to patch application and retaining those snapshots for a configurable time period. So even if the patch makes a mess of your server infrastructure, you can quickly roll back to the snapshots and get things back up and running.
As with all patch management tools, Update Manager is subject to the vagaries of any automated system that attempts to make fundamental changes at the OS layer. Some patches will error, and some will work, but the display and configuration of Update Manager make that dicey reality tolerable to some extent. It's unlikely that we'll ever see a smooth and truly elegant multi-platform patch management solution in our lifetimes, but Update Manager is functional enough to be used on a regular basis, even when dealing with Linux patches -- which should be simpler than Windows and may be why it doesn't get the attention it deserves.