We found vSphere faster than its predecessor, VMWare's ESX 3.51, easier to manage, and good for provisioning fleets (dare we say 'clouds'?) of virtual machine farms.
As part of its updated licensing scheme, the company offers vSphere in four gradations called Standard, Advanced, Enterprise and Enterprise Plus, which costs a hefty $3,495 per processor.
The basic components of what VMWare calls the vSphere 'cloud operating system' are an improved hypervisor and VMware's VirtualCenter management application, along with graduated improvements per edition, including options like vMotion (live VM inter-server migration), vSphere Zones (network security aggregation), distributed resource allocation, and even a distributed network switch.
These improvements allow vSphere 4.0 to manage and automate provisioning of internally-controlled VM farms and infrastructure with hosting platforms located outside an organizations traditional computing 'perimeter'.
In terms of enterprise deployment options, we recommend the Standard package for internal use only. A secure deployment also calls for advanced firewalls, virtual LANs, authentication, and VPNs. Many organizations already have these security resources on hand. Others will find that the additional resources feel like a tax.
The pricier Enterprise versions are needed to control external server resources. However, the 'full meal deal' still provides cost effectiveness compared with provisioning individual servers with dedicated apps/line-of-business applications. Longer term, as the cost of hardware falls, the VM substrate, while convenient, could lose some of that cost effectiveness.
Powerful new features
The term cloud is synonymous with what were once called 'farms' or 'hotels' in systems terminology. To this end, VMware has added many components to the core of what was once VMware Infrastructure and its ESX hypervisor that manage the aggregate assets associated with virtualization for an enterprise.
For example, vSphere adds to Microsoft's own Powershell as the basis for new vSphere commandlets. These VMware PowerCLI 'cmdlets' allowed us to mass-provision a 'skyful' of virtual machines into the computing geography of our choice.
There more than 150 cmdlets available, and while their use is just as terse as those cmdlets provided by Microsoft, they're also very powerful in some cases. We could provision massive numbers of VMs with a simple PowerShell script, and tear them down just as easily. Security for use of PowerCLI cmdlets is controlled strictly via Microsoft's Active Directory services, which need to be perfected prior to deployment. An absconded administrative logon could wreak havoc.
Obtaining this functionality for VMware ESX existing servers via upgrade was mindlessly simple in our lab environment. We used an NFS share to load the upgrade components -- a CD or DVD of the upgrade components can't be used.
One note of warning: We found that the upgrade can disturb bootloaders (grub in our case) if your ESX 3.5 setup isn't the "expected" way; caution is needed here. The vSphere installation routine upgrades all VMware tools after installation, too. These tools are VM guest-dependent, and contain administratively optional 'hooks' that improve management.
Once vSphere was alive, we tried vApp, a resource that groups together VMs as aggregations for object control purposes, like starting them, powering them down, and allowing them to be treated as a single object. We're reminded of the big red switch that turns on stadium lights.
Better still is Datastore Migration that allows a running VM's connected storage to be virtualized - and moved to a different logical drive on the fly. Our drive might be in the local server, or it could be changed to another drive via iSCSI (or an NFS share, Fibre Channel) at will.
This further abstracts storage from a virtualized operating system/application instance in a way that makes far better utilization of SAN resources -- by trapping and redirecting storage. If you're not prepared for what your applications might do, of course, it could be a disaster when files/folders/locks are missing, so using this is state-dependent on what a particular VM is doing at the time. Nonetheless, we liked the VM instance availability that could be anchored from this ad hoc disk change capability.
VSphere allows up to eight virtual CPUs (vCPU) for any specific VM instance, double the vCPUs permitted in the prior version. With this addition comes the capacity to also add/subtract VM instance allocated memory or vCPUs on the fly, depending upon the guest operating system in the VM.
The implications of hardware resource additions/changes are interesting, especially in test platforms where 'tinkering' with these settings can find performance optimization points with varying resources for a virtualized operating system and hosted application performance.
The new vSphere ESX 4.0 hypervisor performed about the same as its predecessor when we ran three virtual machine guests on a single virtual CPU, but improved when we gave the VM guests more vCPUs. We tested vSphere's ESX 4 versus the older 3.51 and found across the board improvements. We also upgraded virtual hardware drivers to see its impact, in our table below.
We tested vSphere 4.0 on the same HP DL-580G5 server that we've used in the past, in order to compare performance numbers between vSphere and its latest competitors, including speed demon Citrix XenServer. We tested with SPEC's SPECjbb2005 using the exact same Windows 2008 Enterprise Server (R1) and Novell SUSE Linux 10.2 that we've used in other tests.
Overall, VMware's vSphere is keeping up with the competition, but the performance numbers weren't dramatic - just very good.
Describing vSphere 4.0 as a 'cloud operating system' is both a marketing and an ideological product direction change on the part of VMware. VSphere is faster. It manages resources regardless of location, and regardless of where VM clouds are located and abstracts storage as well as VM guest/applications in ways that are currently unique and flexible.
We feel it's more than a simple 'dot' release and lays down a gauntlet for Microsoft and the Xen (and Sun's VirtualBox/xVM) communities to work on.
Henderson is principal researcher and Allen is a researcher for ExtremeLabs in Indianapolis. They can be reached at email@example.com.
Henderson is also a member of the Network World Lab Alliance, a cooperative of the premier reviewers in the network industry each bringing to bear years of practical experience on every review. For more Lab Alliance information, including what it takes to become a member, go to www.networkworld.com/alliance.
This story, "VMware upgrade reaches for the clouds" was originally published by Network World.
You may still be better off sticking with Win7 or Win8.1, given the wide range of ongoing Win10...
Now that we're down to the wire, many upgraders report that the installer hangs. If this happens to...
Based on a technique created by a German blogger, here's how to stop wasting hours checking for Windows...
Everyone benefits from Network Time Protocol, but the project struggles to pay its sole maintainer or...
We reviewed a lot of gadgets and services in 2016, and here are our top 12 recommendations for tech...
The kit helps developers build apps that boot as OSes and are less dependent on hardware
Were it not for an alert customer, attackers could have compromised every RHEL instance on Microsoft...