Server scalability

With this release VMware has increased the scalability substantially. vSphere 6 clusters can now support 64 hosts with 8.000 virtual machines. vSphere 6 Hosts can now support 480 physical CPU’s and 12 TB of RAM, each host can now also support up to 1.000 virtual machines.

You may wonder why VMware has done this, because there are no servers with these kind of specifications. VMware likes to be ready and sees the following use case:

• Hadoop/Big Data Workloads
• Scale-out applications will see greater consolidation ratios and improved performance with larger cluster sizes and greater virtual machine densities.
• vSphere Big Data Extensions simplifies and automates the process of provisioning and configuring production Hadoop clusters.

Virtual Machine scalability

The virtual machine maximums have also increased substantially. In vSphere 4 VMware introduced the ‘Monster VM’ with 8 vCPU’s and 255GB of RAM. If that’s a ‘Monster VM’ a vSphere 6 (hardware version 11) virtual machine must be ‘GODZILLA’.

A virtual machine running hardware version 11 can now support:

• With 128 vCPUs and 4 TB of RAM, vSphere 6 is capable of virtualizing even the most demanding applications.
• Complete vNUMA support, including hotplug support. Currently, hot-add memory only gets added to region 0. This is changed to distributed the newly added memory according to the numa architecture.
• WDDM 1.1 – Hardware acceleration of operations helps reduce memory footprint in Windows, because the Desktop Window Manager compositing engine no longer needs to keep a system memory copy of all surfaces used by GDI/GDI+, as it did in WDDM 1.0. WDM 1.1 is supported on Windows 7 and above.
• xHCI 1.0 allows USB 3 devices to run at full speed.
• Many customers wish to remove all unused devices from virtual machines, utilizing vHW11 customers can now remove serial and parallel ports. In addition customers can now add up to 32 serial ports to a virtual machine.

Use Case:

• Business-Critical Applications (e.g. Oracle, SQL Server, Exchange, SAP HANA)
• Virtualized scale-up applications will see greater performance as a result of the increased scale and configuration maximums
• In virtualized SAP HANA environments, customers have seen 400% performance gains over RDBMS and 9x gains in planning load times as well as significant CapEx and OpEx savings versus non-virtualized environments. The Increased memory size made it possible to house the SAP HANA’s in- memory database in its entirety

vGPU graphics acceleration

vSphere 6 also includes support for NVIDIA GRID vGPU which delivers rich 3D graphics from the data center that can be easily accessed across devices and locations–more affordably than ever before.

VMware Horizon and vSphere 6 with NVIDIA GRID vGPU enables designers, architects and engineers to run the most advanced, graphics-rich applications in a remote desktop – using NVIDIA professional 3D graphics and certified application drivers. This graphics mode shares the DirectX and OpenGL support of VDGA with the density of VSGA. The best of both worlds.

Serial and Parallel Port Enhancements

Serial and parallel ports can now be removed from a virtual machine when using compatibility 6 (vHW 11). In addition, the maximum number of serial ports has been increased to 32. Security-conscious organizations like the ability to control all aspects of the hardware that the applications are running on. With vSphere 6.0, they can remove unused serial and parallel ports. Point-of-sale systems often require a large number of serial devices. With vSphere 6.0, each virtual machine can contain as many as 32 serial ports, enabling virtualization of more point-of-sale systems.

vCenter Server

The great news is, that the vCenter virtual appliance and the installable vCenter Server are on par. Meaning that the scalability and feature set of both vCenter versions are identical.

There is a minute difference in the supported databases though. The Windows installable vCenter Server supports Postgres and External SQL and Oracle DBs, the vCenter virtual appliance supports embedded Postgres and external Oracle DBs (so no external SQL).

• Both the classic Windows installation and the vCenter Server appliance support all the new vCenter Server 6 scale numbers.
• There is no longer a difference in scale between Windows and the Appliance!
• Supported databases for the Windows installation are SQL 2008 R2, 2012 and 2014, Oracle 11g and 12c as well as the option to use an embedded vPostgres database.
• vPostgres on Windows is limited to 20 hosts and 200 virtual machines. Upgrades where SQL express was installed will be converted to vPostgres.
• The vCenter Server Appliance supports embedded vPostgres at full scale, 1000 host and 10,000 virtual machines and is the recommended database for the vCenter Server appliance.
• The Appliance supports embedded Postgres or external Oracle Databases. Full scale is still supported when running the embedded Postgres database.
• Customers can now deploy the version that makes sense for their business without worrying about sacrificing stability or scalability.
• Customers can begin to move to the Appliance at their own pace while still having full interoperability between the Windows and Appliance vCenter Servers.

Platform Services Controller (PSC)

The Platform Services Controller (PSC) includes common services that are used across the suite. These include SSO, Licensing and the VMware Certificate Authority (VMCA).

The PSC removes services from vCenter and makes them centralized across the vCloud Suite. This gives customers a single point to manage all their vSphere roles and permissions along with licensing and reduces vCenter Server installation which enables faster install or upgrade to vSphere 6.

The PSC is the first piece that is either installed or upgraded. When upgrading a SSO instance becomes a PSC. There are two models of deployment, embedded and centralized.

• Embedded means the PSC and vCenter Server are installed on a single virtual machine. – Embedded is recommended for sites with a single SSO solution such as a single vCenter.
• Centralized means the PSC and vCenter Server are installed on different virtual machines. – Centralized is recommended for sites with two or more SSO solutions such as multiple vCenter Servers, vRealize Automation, etc. When deploying in the centralized model it is recommended to make the PSC highly available as to not have a single point of failure, in addition to utilizing vSphere HA a load balancer can be placed in front of two or more PSC’s to create a highly available PSC architecture.

Use of the embedded model is meant for standalone sites where this vCenter Server will be the only SSO integrated solution and replication to another PSC is not needed. The recommendation is to deploy external PSC’s in any environment where there is more then one SSO enabled solution (vCenter Server, vRealize Automation, etc) or where replication to another PSC, such as another site, is needed.

When performing an upgrade the PSC will be placed wherever SSO is currently.

Linked mode

Linked mode in previous versions was restricted to the Windows installation of vCenter Server only. This is no longer the case in vSphere 6. By using the PSC’s built in replication Windows and Appliance based vCenter Servers joined to the same SSO domain will be in vSphere 6 enhanced linked mode. Yes, the Appliance and Windows based vCenter Servers will be in enhanced linked mode simply by joining the same SSO domain.

This differs from what we had previously when pointing vCenter Servers at the same SSO server, in that scenario we only had a single pane of glass view, with vSphere 6 enhanced linked mode we have full replication of roles and permissions, licensing, tags, and policies.
 

vSphere Client

The first major improvement because it irritated a lot of people, including me, the Windows installable vSphere Client now has the ability to manage virtual hardware 10 and 11 virtual machines. Any new feature to virtual hardware 10 and 11 are read only. Still one ‘missing feature’ ESXi patching using VUM still requires the regular Windows installable vSphere Client.

Another frustration for a lot of people was the Web Client performance. VMware put the vSphere Web Client went through extensive optimization around both performance and usability.

Performance

On the performance side engineering went screen by screen optimizing every query being made back to the Inventory Service, and SSO. This resulted in 13 times faster login. Right click menus appear and are useable 4 times faster. And most tasks are now at least 50% faster. Performance charts now render and are usable in less then half the time.

VMRC has also been integrated, now administrators can perform the same actions from a virtual machine console as they did in the Windows client. Below is a chart which shows the improvements made, feature by feature.

Looking at the chart the blue lines represent the time in milliseconds an operation took in previous web client versions.

NOTE: Firefox is still a supported browser but the performance when using it is 3-4 times slower compared to using Chrome or Internet Explorer. So do NOT use FireFox.

The vSphere Web Client is the client going forward. In this release VMware has made significant gains in performance bringing it on-par with the Windows Client.

Usability

On the usability side improvements include an enhanced “Home” button. Simply hover over it and you can get to any area in the Web Client in a single click. Also, the Right Click Menu has been flattened and to make getting to where you need as fast and easy as it was in the vSphere Client.

VMware moved the recent tasks list back to the bottom, allowing for more information to be displayed and a more consistent feel when compared to the vSphere Client. And lastly the UI is dockable. You can re-arrange your screen layout in anyway you want.

Content Library

Centralized repository that provides simple and effective management for content including virtual machine templates, ISO images and scripts. With vSphere Content Library, it is now possible to store and manage content from a central location and share through a publish/subscribe model.

Many organizations have several vCenters servers across diverse geographic locations, and on these vCenters there is most likely a collection of templates and ISOs. Currently there is function within vCenter to centrally manage the templates and distribute them to all locations. The Content Catalog provides the ability to centrally manage content and ensure it’s distributed across the infrastructure.

 vCenter’s Content Library provides simple and effective management for:

• VM templates
• vApps
• ISO images
• Scripts

 There are three types of Catalog Libraries

• Local Catalog – Local only to the local vCenter
• Published Catalog – A local library that is published for catalog subscribers
• Subscribed Catalog – A library that syncs with a published library

There are also two types of subscriptions to a published catalog.

• Immediate Download (aka Automatic Subscription) – The entire contents of the published catalog are copied to the subscriber.
• On-Demand – Instead of downloading all the data at once, only the metadata is downloaded as a reference to the content on the published library. This allows the administrator to download full catalog items only when needed by synchronizing individual items of within the catalog.

Here are some of the technical details for the Content Library.

• The Content Library and Transfer service are the main services and are included as part of vmware-vdcs which is the Virtual Datacenter Service that is installed as part of the vCenter Management Node.
• The Content Library Service is responsible for keeping track of the metadata of all the Content Libraries it is in charge of as well as checking for updates on a publisher.
• The Transfer Service does most of the heavy lifting and is called by the Content Library Service to copy content between libraries
• The Content Library also utilizes the same database as vCenter, that is the VCDB.
• If stored on a datastore, 64TB is the maximum size
• Maximum of 256 content items per library.
• Maximum of 10 simultaneous copies.
• Synchronization occurs once every 24 hour.

Key Features

VMware Horizon Client for Linux makes it easy to access your Windows virtual desktop from a supported Linux system with the best possible user experience on the Local Area Network (LAN) or across a Wide Area Network (WAN).

• Support for Ubuntu 12.04 or 14.04, Red Hat Enterprise Linux (RHEL) 6.5, SUSE Linux Enterprise Desktop (SLED) 11 SP3, and CentOS 6.5 – The Horizon Client 3.2 installer provides support for these operating systems.
• Unmatched performance – The adaptive capabilities of the PCoIP display protocol are optimized to deliver the best user experience, even over low-bandwidth and high-latency connections. Your desktop is fast and responsive regardless of where you are.
• Simple connectivity – Horizon Client for Linux is tightly integrated with VMware Horizon for simple setup and connectivity.
• Secure from any location – At your desk or away from the office, your data is delivered securely to you wherever you are. Enhanced certificate checking is performed on the client. Horizon Client for Linux also supports optional RADIUS and RSA SecurID authentication.

What’s New in This Release

• Support for additional operating systems with the client installer — The new client installer provides both a graphical UI and a command-line UI for silent installations on the supported operating systems. See Before You Begin.
• New UI for selecting which monitors to use for Horizon Client – If you specify that you want to use all monitors, and if you are using the PCoIP display protocol, you can specify a subset of adjacent monitors to use.
• Persistent settings in location-based printing — Printer settings for location-based printers are retained after a user logs out or disconnects from the desktop. After the user logs in to the desktop again, the location-based printer continues to use the previously configured settings. The remote desktop must have View Agent 6.0.2 installed.

Download