No I didn’t set my alarm clock like Eric Sloof, just to be one of the first to post it… hence the reason this is “late”. But I got some more lined up for you though in the upcoming days. Now that the vCloud Suite 5.1 is available. Make sure to start your download engines and prep to upgrade. Before you start downloading, make sure to hit the launch page. I created a nice short URL for it
VMware NOW – Get the Latest Info on VMware Product Launches:
http://vmwa.re/vcloudnow
Download links:
- ESXi 5.1.0 Installable
- vCenter Server 5.1.0 and modules
- VMware vCloud Director 5.1.0
- VMware vCenter Site Recovery Manager 5.1.0
- VMware vCenter Infrastructure Navigator 1.2.0
- VMware vCenter Operations Management 5.0.3
- VMware vCenter Configuration Manager 5.5.1
- vSphere Data Protection 5.1.0
- vSphere Replication 5.1.0
- vSphere Storage Appliance 5.1.0
- vCloud Networking and Security 5.1.0
- vSphere PowerCLI 5.1
- vSphere CLI 5.1
- vCenter Orchestrator Appliance 5.1.0
- vSphere Management Assistant 5.1
What’s new docs:
- What’s New in VMware vSphere 5.1
- What’s new in VMware vCenter 5.1
- What’s New in VMware vSphere 5.1 – Networking
- What’s New in VMware vSphere 5.1 – Platform
- What’s New in VMware vSphere 5.1 – Storage
- What’s New in VMware vSphere 5.1 – Performance
- Introduction to VMware vSphere Replication
- Introduction to VMware vSphere Data Protection
- What’s new in VMware vSphere Storage Appliance
- What’s new in vCloud Director 5.1
hello Duncan
thanks for the tip …
now the question …
vCD 5.1 ….
vShield manager runs one for every vCenter ….
but you can have more than one datacenter inside a vCenter and then … more than one Nexus 1000v inside the same vCenter …. ( I know is not very common …. but I already checked with Cisco )
in that case ….
what if a vOrg is present …. “elastically” maybe …. in two different Datacenters …. ?!?!?
will vCD be smart enough to extend Vlans from vDS1 in Cluster 1/Datacenter 1 to vDS-2 in Cluster 2/Datacenter2 …. inside the same vCenter …..
and….
once step higher …
What will happen when there were 2 separate vCenters …. ( obviolusy with Datacenter A and Cluster A, vDS A )
and some client want to extend its vOrg there ?!?!?!
I see all the downloads but where is the vCloud Director Appliance?
Anyone notice if you want to install the vCenter 5.1 ova via your 5.0 vCenter for testing purposes that it will not accept the OVA?
Get the vDC appliance from the vCloud Evaluation page https://my.vmware.com/web/vmware/evalcenter?p=vcloud-director51&lp=default
It’s not supported for production thus no link on the product downloads.
vCenter 5.1 ova? or vCD 5.1 ova? I know Workstation 9 will take all the 5.1 ovas.
Duncan,
I pray you have an idea on the following issue:
I set up a 5.1 vCloud acc. to available documentation – installed management cluster with mgmt vcenter, resource pool with rp vcenter, vcloud director, vshield manager etc. pp. and I configured everything so I was finally able to set up my first PvDC, OrgvDC, Organization, internal and external networks et al. Until here everything worked as expected.
Then I installed and configured vCenter Chargeback and UsageMeter.
Afterwards I tried to access vCloud Director again to configure another Organization. But when accessing CloudDirector’s website (https://clouddirector.foo.com/cloud/) it didn’t show CloudDirector’s content anymore but the vSphere Web Client interface of the resource pool’s vCenter.
I don’t have any idea of what might have misconfigured Cloud Director or where to look at to fix this issue.
Any chance to fix this without dropping database contents and reinstalling vCD (and maybe running into the same problem again)?
Kind Regards
Bjoern
I have no clue what happened. This is strange, almost sounds like a DNS problem rather than a VCD issue.
Hi,
DNS records are fine, it was the first thing I had checked.
Meanwhile I discovered that the website vCD delivers contains a frame with URL https://vcrp0:9443/vsphere-client/transfer/?appId={B63390FE-5C3B-4403-A14F-1DC90BA3B808}:5
I.e. it uses the short form for the hostname vcrp0 whereas I always use FQDNs.
Digging in the vCD database schema I found the following row in the CONFIG table:
CONFIG_ID = 361
CAT = vcloud
NAME = lookupservice.vspherewebclient.url
VALUE = https://vcrp0:9443/vsphere-client
SORTORDER = 0
It’s the one and only reference to vcrp0:9443.
Actually I saw in vCD configuration (when it wasn’t broken yet) a note saying it hadn’t been registered with the lookup service. I then registered vCD with the lookup service at vcrp0. Now I assume this was the point where vCD configuration got screwed and I’m looking for a way to unregister vCD while not being able to access the regular vCD configuration website.
Solved:
first of all – I did activate Single Sign On after registering with lookup service. SSO is running on the vCenter Server at the moment. (Just for testing purposes.) vCD now embeds a frame into it’s website to let the user get an access token from SSO service. (Just guessed, I don’t have a deep overview over SSO services yet.)
So the frame with a URL pointing to the vcenter server seems to be reasonable in this setup.
The second issue concerns the short hostname used in the URL. I dumped my SSO and vCD databases and found in vCD’s CONFIG table:
“NAME=lookupservice.vspherewebclient.url VALUE=https://vcrp0:9443/vsphere-client”
as well as some similar short form URLs in SSO’s table
LS_SERVICE_ENDPOINT. I updated those values using FQDNs, rebooted all affected VMs and now verything seems to work again.
I wonder why SSO/LookupService configure those short names, I’m sure I always entered FQDNs; my assumption is that the SSO installer is pretty braindead. Apart of not handling Oracle configuration correctly it said it couldn’t resolve the server’s FQDN using nslookup. Calling nslookup by hand shew correct forward and reverse records, so I skipped the warning. I think this resulted in the short names in SSO’s configuration.
This took me about a day to solve, but at least I have a clearer view on some of the services now.