I'm having a problem with my vCloud Director plug-in.
The installation of the plug-in appears to have been OK, no issues.
When I try to configure a new vCloud Director connection with the "Session per user" setting it saves the information OK, but in the Orchestrator client I'm unable to browse any of my vCloud objects.
When I try to configure a new vCloud Director connection with the "Share a unique session" setting it fails when I apply the changes.
Does anyone have any suggestions as to what I can try to fix either of these issus?
Did you verify that you have imported the SSL certificate for the vCloud Director instance that you want to connect to, from the Network view in the Orchestrator configuration interface?
For more info: http://pubs.vmware.com/orchestrator-plugins/topic/com.vmware.using.vcloud_director.plugin.doc_15/GUI...
First you need to understand that when you use "Session per user" vCO will try to log in your system organization with the credentials you used in vCO so these must be matching (i.e. if you used the vCO appliance default vcoadmin / vcoadmin you must have such an user / password in the System org.
For the shared session do you really have an administrator account in the System organization ? When you log in vCD do you log in a particular organization or can you access them all. People are often confused between being the admin of an org and the System admin. Either you are really administrator of the system org an there is a problem with the password or you are admin of a given org and you should specify this one in the configuration.
Also please check that you have imported the vCD host certificate in the network tab of the vCO configuration.
I added the SSL before I tried creating the new connection. I've even removed and re-added the SSL information.
My vCloud instance has 2 cells that sit behind an F5 load balancer. I got the cert by pointing to the F5, and not a specific cell.
Is the vCloud API URL configured in the cell matching the one configured in the plug-in ?
Yep, I understand the difference between the 2 session settings. I would prefer to use the "share a unique session".
I do have matching username and passwords in both the vCenter server and vCloud instance. The username and passwords are AD domain accounts and are at the system level and not at an organization. So I login to the Orchestrator client with the same username and password that is setup as an administrator in the vCenter and vCloud.
I do have another account that I've created for regular use, butI'm trying all the accounts, including the administrator account. Same results.
SSL Cert ... I installed that before trying to make the new connection. I mentioned it to Igor as well, but my configuration has 2 cells behind an F5 load balancer. Would that mess up anything? I've tried pointing directly to each of the cells with the same results.
Good question ... I'm not sure, how can I tell that?
In vCD the public REST API base url is https://host.domain.name.com/cloud/api
When I click the "Test Link" I get to a page that hase the vCD logo and grey backgroud but it says Page Not Found.
This should be the url of the load balancer and you need to make sure the plug-in is configured to get to the load balancer.
You can enable debug for the vCloud Director plug-in by adding the following to the log4j file. (typically after the same section for the vc plug-in):
<category additivity="true" name="com.vmware.vmo.plugin.vcloud">
It was the API URL that was set wrong in vCloud director. With a quick change I'm now able to browse the objects with using the per user session.
Thank you for the help!