Monthly Archives: October 2013

vCenter SSO 5.5 Backwards Compatability: Mixed Mode Install

While at a post #vFourmAU event last week a group of us where talking about SSO in vCenter 5.1 and what a disaster it had been (credibility wise) and that VMware had done their best to improve the experience in the 5.5 release. Out of that conversation came word that if people where looking to upgrade from 4.x or 5.0 to 5.1 as an interim step to 5.5, you could install SSO 5.5 in that 5.1 Environment so as not to go through the relative pain that SSO 5.1 brings to the table…that is to say SSO 5.5 was backwards compatible.

http://blogs.vmware.com/vsphere/2013/10/backwards-compatible.html

That post above goes through a little background and case examples where it might be relevant to run SSO 5.5 mixed in with vCenter5.1.

While I have been doing a bunch of upgrade testing in the ZettaGrid Labs for 5.0 to 5.1/5.5 Upgrades I thought I’d go through the process of installing SSO 5.5 into the environment before upgrading the rest of the vCenter components to 5.1. My main driver here was the opportunity to not have to configure an SSO database and to be ahead of the game when it comes time to jump to 5.5.

vCenter 5.0 to 5.1 Upgrade Mixed Mode SSO 5.5 Install:

Load up the vCenter 5.5 Installer and select vCenter Single Sign On Install. You can see I’m running this installer on a vCenter 5.0 Update 2 instance. The aim here is to have this version upgraded to 5.1 while utilizing the mixed mode capability of SSO 5.5

Run through the installer as you would for a standard SSO 5.5 install

One of the differences to point out here with SSO 5.5 is that the infamous [email protected] account has been replaced with a domain name, in this case I’m rolling with the default vsphere.local domain.

Much like an AD install, you have the ability to choose the default first site name…which does use Default-First-Site is left unchanged.

Once the SSO Service has been installed you can swap out the vSphere 5.5 Media for the 5.1 version and proceed with the upgrade of the Inventory Service and the Upgrade of vCenter it’s self. Both installs ask you for the SSO information relating to the SSO service as shown below. 5.1 will default to [email protected] so you need to modify that to reflect the account details as configured during the SSO 5.5 installer.

Once both the Inventory Service and vCenter have been upgraded, the final step for mixed mode is to install the vCenter 5.5 Web Client as the 5.1 Web Client will not recognise the SSO 5.5 install so you will be unable to modify the Configuration until it’s installed. I did run into a few issues with the install from a 5.0 environment, but that was more due to the fact that I had expired certs in the 5.0 Web Client SSL Folder, which the 5.5 installer checks and than attempts to copy into the new install location. While on the vCenter Single Sign On Information page I got an error saying the SSL cert was invalid, however it was not reflecting the Lookup Service URL as you would assume…but actually doing a check against c:\ProgramData\VMware\vSphere Web Client\ssl\rui.crt which it validates and copies to the new install location.

Once installed it’s business as usual and we have a fully operational mixed mode environment ready for action.


vForum 2013: Session Details

vForum returns to the Sydney Convention and Exhibition Center next week and I’ll be attending for the 3rd year in a row, but this time around I’ll be there with ZettaGrid as a Platinum Sponsor, and also as a VMware vChampion. The vChampion Program is run in APJ and brings together a group of dedicated VMware IT professional who are passionate about all things VMware and work to evanaglise the VMware solution stack amongst the greater community.

I’ll be presenting two sessions next week at vForum, one with ZettaGrid and one with the vBrownBag Tech Talks. For a full schedule of vBrownBag talks, click the link above and check out the great line-up of presenters on a range of topics from fellow vExperts and vChampions. These talks are not sales or marketing related, but are more focused on the sharing of experiences learnt in our collective journeys.

Build me a Cloud Now! – The Power of Automation:
Monday 21st October @ 14:20-1440 Cloud Theatrette Main Hall

The ZettaGrid talk is a live demo showing off the investment ZettaGrid has made into providing end to end automation for the provisioning of VMware vCloud Virtual Datacenter resources. I’ll be going through the whole process as a end user going through the purchasing of a Virtual Datacenter through our Customer Portal, to the creation and deployment of a template VM and a ready to use cloud in less than 15 minutes.

Differentiate or Die?:
Tuesday 22nd October @ 14:25 Parkside Foyer Lever 1 (Map)

Based on a blog post I wrote a couple months back, I will go through my experiences in working for a pure Application and Hosting Provider, a Managed Services Company and in my current role working for a Infrastructure as a Service Company and what I believe can be done to fend off the public cloud threat that major players like Amazon AWS, Azure or Google represent to traditional service providers.

Be great to have as many people show up (refraining from heckling) and allow me to share my experiences and attempt to blow you away with the automation benefits of ZettaGrid vCloud…hopefully the demo gods are good to me, and the 4G internet connection is strong!

See you there!

Quick Tip: Disapearing Datastore Cluster in vCloud after adding Datastore to vCenter with Storage Profiles

Had an interesting occurrence pop up early in the week while we where adding a new Datastore to a vCloud Hosting Zone. We are running vCloud Director 5.1.2 and have implemented two tiers of Datastore Cluster from which the Provider vDCs can consume storage from.

We went about adding a new datastore to the SATA Cluster through vCenter without too much worry as per usual. Upon going back into vCloud Director we noticed that the SATA Datastore Cluster had disappeared from the list of datastores…just gone!

After an initial panic we realised that a step had been missed in the provisioning and setup of the new datastore. Because we have Storage Profiles with Storage Capabilities being passed through from vCenter to vCloud any datastore to be consumed by vCloud requires a User-Defined Storage Capability Assigned to it as shown below:

Once the Policy was applied the Datastore Cluster reappeared in vCloud Director and the panic was over. Not sure if this is by design or a bug, but one to look out for. I’m keen to test this against vCloud Director 5.5 and might look to provide an update once that’s been done in the lab.