VMware released their long awaited version 6 of its vSphere 6 products today and as I’m sure you’ll be running out tomorrow to go update all your production environments….
Ok now that we’re done laughing what you probably are going to want to get into is getting your lab updated or built so you can work out the changes yourself, possibly using your EvalExperience licenses you got with VMUG Advantage? Once you get it up and running you’ll notice that a few things have changed from the administration point of view. In this post I’m going to take a quick look at the Management features of vSphere 6.
Platform Services Controller
One thing you’ll find right off is that many of the underlying vCenter services have now been lumped together into what they are calling the Platform Services Controller. These services include Single Sign-On, licensing and certificate management. At installation you are given two options on how to deploy the PSC, either embedded, where the PSC always rides along with vCenter, or External where the PSC is installed on its own VM and each vCenter talks back to the central services controller.
There are a couple of design requirements here if you chose to go the embedded route. You can have a maximum of 8 embedded or external PSCs per Single Sign-On site, and if you choose to go the embedded route it will increase the minimum RAM required to 8 GB.
vSphere Web Client
As has been the trend VMware has spent some serious time improving the Web Client, this time focusing on loading time, login time and a more streamlined component layout. It is still Flash based, but still a bit better. Time will tell with this one.
vSphere Host Client
Is the death of the installable VI client we’ve been hearing about for years here?
Yes but it’s been replaced with a new version that is to be used only for connecting to the hosts directly or Update Manager. No, the new C# client for vSphere 6 will function much in the same way as the 5.5 client, you will be able to manage your infrastructure fully with it, but in terms of editing virtual hardware you will only be able to do so fully on VMs version 5-8.* The good part about it is the new C# client is not version based, rather it can be used to manage hosts running hardware versions 8-11.
Multi-Site Content Library
This one is probably what I am most excited about. Instead of having to update the ISO datastore in each of your locations, as well as building or copying your base templates for each vCenter, with the Content Library you can create a repository for all of your ISOs, templates, vApps and scripts and that repository will automatically be synchronized across all sites and vCenter Servers.
Virtual Datacenters and Policy Based Management
These two are the ones that I frankly still need to dive deeper into. The concept is that you create virtual datacenters, spanning multiple locations (both local and cloud service) and then use policy to define what resources are available and where when spinning up a VM.
Certificate Lifecycle Management
Finally on the management side a new command line interface has been added for managing both the VMware and third-party certificates. I recently used fellow vExpert Derek Seaman’s excellent tool and blog series to use Microsoft Certificate Services certs in my vSphere infrastructure, I have to believe this will make that process easier. As the documentation gets finalized I’ll provide a link to the docs for this here.
All in all it should be an exciting time for us virtualized folks, with lots of new toys and technology to try out.
*After the big Feb. 6 announcement VMware saw fit to let everybody know that there are major changes between what was there in the betas and what will be there in the GA build, this being one of them.