Today VMware announced the release of VMware vSphere 5.0 by surprise! The following is  some of the key features of this release: 

• Convergence. vSphere 5.0 is the first vSphere release built exclusively on the vSphere ESXi 5.0 hypervisor architecture as the host platform.
• VMware vSphere Auto Deploy. VMware vSphere Auto Deploy simplifies the task of managing ESXi installation and upgrade for hundreds of machines.
• New Virtual machine capabilities. 32-way virtual SMP, 1TB virtual machine RAM, Software support for 3D graphics, and more.
• Expanded support for VMware Tools versions. VMware Tools from vSphere 4.x is supported in virtual machines running on vSphere 5.0 hosts.
• Storage DRS. This feature delivers the DRS benefits of resource aggregation, automated initial placement, and bottleneck avoidance to storage.
• Profile-driven storage. This solution allows you to have greater control and insight into characteristics of your storage resources.
• VMFS5. VMFS5 is a new version of vSphere Virtual Machine File System that offers improved scalability and performance, and provides Internationalization support.
• Storage vMotion snapshot support. Allows Storage vMotion of a virtual machine in snapshot mode with associated snapshots.
• vSphere Web Client. A new browser-based user interface that works across Linux and Windows platforms.
• vCenter Server Appliance. A vCenter Server implementation running on a pre-configured Linux-based virtual appliance.
• vSphere High Availability. VMware High Availability has been transformed into a cloud-optimized availability platform.

Here are some of the reasons why I’m excited about this: 

• App Aware API.  This is the same API that has been used by Neverfail’s vAppHA and Symantec’s ApplicationHA products.  Now with 5.0, this API is publicly available.  This means anyone can craft a solution that allows for the monitoring of a application and interfacing with vSphere HA to restart the VM.  Couple this with the new vSphere Web Client’s ease of extensibility and you have the potential to do some great things.
• Ever had DNS resolution cause you issues when using vSphere HA?  With 5.0, all dependency on DNS for vSphere HA has been removed!
• IPv6 is now supported.
• Logging.  There have been a lot of improvements to the log messages with vSphere HA.  This was done to make the log messages more descriptive than ‘unknown HA error’ and should help with identifying configuration issues.
• Several user interface enhancements.  Now you can see more detailed state information about the hosts in your cluster and what role they play with vSphere HA.

The changes to the vSphere HA infrastructure now eliminates the primary/secondary constructs that existed in previous versions of vSphere.  Replacing that is a master/slave model.  In this model, one of the hosts is designated as a master, while the other hosts are designated as slaves.  The master coordinates most of the activities within the cluster and relays information to and from vCenter.

For now though, the reason why this is so great is that you no longer have to worry about details such as what hosts act as your primary nodes and which ones act as secondary nodes.  If you are installing vSphere HA in a blade chassis or making a stretched cluster, this is excellent news for you!

Heartbeat datastores is a feature that allows vSphere HA to utilize the storage subsystem as an alternate communication path.  Using heartbeat datastores allows vSphere HA to do things like determine the state of the hosts in the event of a network failure of the management network. Which brings up another enhancement to be excited about:  management network partitions are now supported in 5.0!

Finally, vSphere 5 has changed entitlements around CPU cores and memory use. The company has lifted licensing restrictions for cores per processor and RAM per host. It’s also eliminated the “advanced” version of vSphere plus, leaving just Essentials, Essentials Plus, Standard, Enterprise, and Enterprise Plus. vSphere 5 has also introduced a small change to the entitlement process around what is known as virtual memory or vRAM.

You must obtain new licenses to deploy VMware vSphere 5. Your existing VMware vSphere 4 licenses will not work on vSphere 5.

For more, please refer to What’s New in vSphere 5.0 and vSphere 5.0 Licensing, Pricing and Packaging Whitepaper as well as Compare VMware vSphere Editions.