VMware vSphere 5.0

• ESXi Convergence – No more ESX, only ESXi (they said they would do it, they meant it)
• New VM Hardware:  Version 8 – New Hardware support (VS5 still supports VM Hardware 4 & 7 as well if you still want to migrate to the old hosts)
  • 3D graphics Support for Windows Aero
  • Support for USB 3.0 devices

• Platform Enhancements (Blue Requires Hardware v8)
  • 32 vCPUs per VM
  • 1TB of RAM per VM
  • 3D Graphics Support
  • Client-connected USB devices
  • USB 3.0 Devices
  • Smart-card Readers for VM Console Access
  • EFI BIOS
  • UI for Multi-core vCPUs
  • VM BIOS boot order config API and PowerCLI Interface
• vSphere Auto Deploy – mechanism for having hosts deploy quickly when needed ( I’m going to wait and see how customers use this one.)
• Support for Apple Products – Support for running OSX 10.6 Server (Snow Leopard) on Apple Xserve hardware. (although I betting technically, you can get it to run on any hardware, you will just not be compliant in your license)
• Storage DRS – Just like DRS does for CPU and Memory, now for storage
  • Initial Placement – Places new VMs on the storage with the most space and least latency
  • Load Balancing – migrates VMs if the storage cluster (group of datastores) gets too full or the latency goes too high
  • Datastore Maintenance Mode  - allow you to evacuate VMs from a datastore to work on it (does not support Templates or non-registered VMs yet…)
  • Affinity & Anti-Affinity – Allows you to make sure a group of VMs do not end up on the same datastore (for performance or Business Continuity reasons) or VMs that should always be on the same datastore.  Can be at the VM or down to the individual VMDK level.
  • Support for scheduled disabling of Storage DRS – perhaps during backups for instance.
• Profile-Driven Storage – Creating pools of storage in Tiers and selecting the correct tier for a given VM.  vSphere will make sure the VM stays on the correct tier(pool) of storage.  (Not a fan of this just yet.  What if just 1GB of the VM needs high-tier storage? This makes you put the whole VM there.)
• vSphere File System – VMFS5 is now available.  (Yes, This is a non-disruptive upgrade, however I would still create new and SVmotion)
  • Support for a single extent datastore up to 64TB
  • Support for >2TB Physical Raw Disk Mappings
  • Better VAAI (vStorage APIs for Array Integration) Locking with more tasks
  • Space reclamation on thin provisioned LUNs
  • Unified block size (1MB) (no more choosing between 1,2,4 or 8)
  • Sub-blocks for space efficiency (8KB vs. 64KB in VS4)
• VAAI now a T10 standard – All 3 primitives (Write Same, ATS and Full Copy) are now T10 standard compliant.
  • Also now added support for VAAI NAS Primitives including Full File Clone (to have the nas do the copy of the vmdk files for vSphere) and Reserve Space (to have the NAS create thick vmdk files on NAS storage)
• VAAI Thin Provisioning – Having the storage do the thin provisioning and then vSphere telling the storage which blocks can be reclaimed to shrink the space used on the storage
• Storage vMotion Enhancements
  • Now supports storage vMotion with VMs that have snapshots
  • Now supports moving linked clones
  • Now supports Storage DRS (mentioned above)
  • Now uses mirroring to migrate vs change block tracking in VS4.  Results in faster migration time and greater migration success.
• Storage IO Control for NAS – allows you to throttle the storage performance against “badly-behaving” VMs also prevents them from stealing storage bandwidth from high-priority VMs.  (Support for iSCSI and FC was added in VS4.)
• Support for VASA (vStorage APIs for Storage Awareness) – Allows storage to integrate tighter with vcenter for management.  Provides a mechanism for storage arrays to report their capabilities, topology and current state.  Also helps Storage DRS make more educated decisions when moving VMs.
• Support for Software FCoE Adapters – Requires a compatible NIC and allows you to run FCoE over that NIC without the need for a CNA Adapter.
• vMotion Enhancements
  • Support for multiple NICs.  Up to 4 x 10GbE or 16 x 1GbE NICs
  • Single vMotion can span multiple NICs (this is huge for 1GbE shops)
  • Allows for higher number of concurrent vMotions
  • SDPS Support (Slow Down During Page Send) – throttles busy VMs to reduce timeouts and improve success.
  • Ensures less than 1 second switchover in almost all cases
  • Support for higher latency networks (up to ~10ms)
  • Improved error reporting – better, more detailed logging (thank you vmware!)
  • Improved Resource Pool Integration – now puts VMs in the proper resource pool
• Distributed Resource Scheduling/Dynamic Power Management Enhancements
  • Support for “Agent VMs” – These are VMs that work per host (currently mostly vmware services – vshield, edge, app, endpoint, etc)  DRS will not migrate these VMs
  • “Agents” do not need to be migrated for maintenance mode
• Resource pool enhancements – now more consistent for clustered vs. non-clustered hosts.  No longer can modify resource pool settings on the host itself when it is managed by vcenter.  It does allow for making changes if the host gets disconnected from vCenter
• Support for LLDP Network Protocol – Standards based vendor-neutral discovery protocol
• Support for NetFlow – Allows collection of IP traffic information to send to collectors (CA, NetScout, etc) to provide bandwidth statistics, irregularities, etc.  Provides complete visibility to traffic between VMs or VM to outside.
• Network I/O Control (NETIOC) – allows creation of network resource pools, QoS Tagging, Shares and Limits to traffic types, Guaranteed Service Levels for certain traffic types
• Support for QoS (802.1p) tagging – provides the ability to Q0S tag any traffic flowing out of the vSphere infrastructure.
• Network Performance Improvements
  • Multiple VMs receiving multicast traffic from the same source will see improved throughput and CPU efficiency
  • VMkernel NICs will see higher throughput with small messages and better IOPs scaling for iSCSI traffic
• Command Line Enhancements
  • Remote commands and local commands will now be the same (new esxcli commands are not backwards compatible)
  • Output from commands can now be formatted automatically (xml, CSV, etc)
• ESXi 5.0 Firewall Enhancements
  • New engine not based on iptables
  • New engine is service-oriented and is a stateless firewall
  • Users can restrict specific services based on IP address and Subnet Mask
  • Firewall has host-profile support
• Support for Image Builder – can now create customized ESXi CDs with the drivers and OEM add-ins that you need.  (Like slip-streaming for Windows CDs) Can also be used for PXE installs.
• Host Profiles Enhancements
  • Allows use of an answer file to complete the profile for an automated deployment
  • Greatly expands the config options including: iSCSI, FCoE, Native Multipathing, Device Claming, Kernel Module Settings & more)  (I don’t think Nexus is supported yet)
• Update Manager Enhancements
  • Can now patch multiple hosts in a cluster at a time.  Will analyze and see how many hosts can be patched at the same time and patch groups in the cluster instead of one at a time.  Can still do one at a time if you prefer.
  • VMTools can now be scheduled at next VM reboot
  • Can now configure multiple download URLs and restrict downloads to only the specific versions of ESX you are running
  • More management capabilities: update certificates, change DB password, proxy authentication, reconfigure setup, etc.
• High Availability Enhancements
  • No more Primary/Secondary concept, one host is elected master and all others are slaves
  • Can now use storage-level communications – hosts can use “heartbeat datastores” in the event that network communication is lost between the hosts.
  • HA Protected state is now reported on a per/VM basis.  Certain operations no longer wait for confirmation of protection to run for instance power on.  The result is that VMs power on faster.
  • HA Logging has been consolidated into one log file
  • HA now pushes the HA Agent to all hosts in a cluster instead of one at a time.  Result:  reduces config time for HA to ~1 minute instead of ~1 minute per host in the cluster.
  • HA User Interface now shows who the Master is, VMs Protected and Un-protected, any configuration issues, datastore heartbeat configuration and better controls on failover hosts.
• vCenter Web Interface – Admins can now use a robust web interface to control the infrastructure instead of the GUI client.
  • Includes VM Management functions (Provisioning, Edit VM, Poer Controls, Snaps, Migrations)
  • Can view all objects (hosts clusters, datastores, folders, etc)
  • Basic Health Monitoring
  • View the VM Console
  • Search Capabilities
  • vApp Management functions (Provisioning, editing, power operations)
• vCenter Server Appliance – Customers no longer need a Windows license to run vCenter.  vCenter can come as a self-contained appliance (This has been a major request in the community for years)
  • 64-bit appliance running SLES 11
  • Distributed as 3.6GB, Deployment range is 5GB to 80GB of storage
  • Included database for 5 Hosts or 50 VMs (same as SQL Express in VS4)
  • Support for Oracle as the full DB (twitter said that DB2 was also supported but I cannot confirm in my materials)
  • Authentication thru AD and NIS
  • Web-based configuration
  • Supports the vSphere Web Client
  • It does not support:  Linked Mode vCenters, IPv6, SQL, or vCenter heartbeat (HA is provided thru vSphere HA)
• vCenter Heartbeat 6.4 Enhancements
  • Allows the active and standby nodes to be reachable at the same time, so both can be patched and managed
  • Now has a plug-in to the vSphere client to manage and monitor Heartbeat
  • Events will register in the vSphere Recent Tasks and Events
  • Alerts will register in the alarms and display in the client
  • Supports vCenter 5.0 and SQL 2008 R2

That’s what I have on vSphere 5, next up is SRM5, vShield5, Storage Appliance, and vCloud Director 1.5.

vCenter 4.0 (vCenter is now 4.0 to be on par with ESX) includes linked mode in the standard edition of vCenter.  Those users who have current support on vCenter standard edition will receive linked mode as part of their included subscription.  Linked mode is not included in the foundation edition of vCenter or in the vSphere essentials editions .  Linked mode uses a ADAM (Active Directory Application Mode) database to replicate it’s configuration between multiple vCenter servers.  Some of the things stored in the ADAM database include:

• Connection information (IP addresses and ports)
• Certificates and thumbprints
• License Information
• User Roles

When vCenter servers are "linked," connecting to any one will allow an administrator to see and manage any of the vCenters in the link group thru one vSphere Client assuming they have rights to do so (as seen below).

Permissions can be configured so that an admin may only have rights to certain vCenter servers in the link group and not others.  The scalability has also been increased dramatically.  A single vCenter instance can manage 300 ESX hosts and 3000 VMs.  A linked mode group can manage 1000 ESX hosts and 10,000 VM’s (now you know why a search field was added to the client.)

You can read about linked mode and all of the new features in vCenter here .

Stephen talked about the main focus of VMware.  That is, to enable customers to deliver IT as a service, at the same time remembering 3 key factors:  Efficency, Control, and Choice .  He went on to discuss vSphere.  He gave some awesome statistics on vSphere, particularly: over 3 million Engineering hours have gone into vSphere .  For the Efficiency section, he discussed the scalability and performance.  He talked about power savings and storage savings .  For Control , he talked about Config-Control and how to maintain consistency in host configuration.    He then discussed distributed switches and how they add control to the networking layer.  vApp and how it will let admins control their apps better as a single unit.  He then went on to demo a very polished Fault Tolerant configuration.  This was received very well and with a resounding applause from the crowd.  He talked about vShield Zones and how they protect applications from talking to the infrastructure that they shouldn’t for customers without advanced firewall experience.  Lastly, Choice .  The goal is to allow any server, any storage, any OS, and any app to run local in the private cloud or a cloud in a different location, public or private.  He showed a list of the supported OSes for vSphere compared to those of Hyper-V and it was not even close.  I guess it is an advantage to not have an OS business.

After the functionality section Stephen introduced Bogomil Balansky (below), VP of Product Marketing, VMware.

Bogomil introduced the Partners to the licensing and packaging of vSphere.  I apologize, due to legal restrictions I cannot list those here.  Hopefully we will find out more information from the announcement coming April 21st .

Stephen returned to the stage and discussed the API and plug in capability of vSphere which was a great segway to the next presenters: Adam Famularo (below on left) SVP and GM, Recovery Management and Data Modeling Business Unit, CA, and the second presenter was Roger Pilc (below, seated), Corporate SVP and GM, CA.

Adam showed a great video on the University of Texas, Brownsville, and how they used CA XOsoft to recover their MS Exchange environment on VMware at their disaster recovery site during Katrina.  He went on to discuss CA’s organization and how they are all aligned.  He discussed many of the channel programs that are available (this is a Partner conference after all).  He talked about upcoming Arcserve and XOsoft releases.  I apologize, I don’t know what is public or not from the information that was presented so I’m going to leave the details out on that one.  Roger took the lead at this point.  He discussed the cloud and how it is transforming business.  That management is one of the key pieces needed to take it to the next level.  He closed with an explanation of the VMware – CA relationship and how that joint effort can truly improve overall service quality from the cloud.

Now onto my labs today, I’ll check back in soon.

Great information and thank you all that responded to the poll.

Just as a FYI, I run mine in a VM.

An article by Desmond Chan was written back in September. I saw it on an internal Wiki but did not realize he had published it externally. It’s a good article describing what to consider if you only have a limited amount of bandwidth. The article describes some of the common administrative functions that are performed in VC on a daily basis and the amount of bandwidth they require. Definately some good reading if you need to manage ESX with VC over WAN links.  You can find the full article here .