VMware Cloud Community
FGShepherdP10
Enthusiast
Enthusiast
‎05-31-2013 06:31 AM
Jump to solution

vCD (5.1) Objects Missing under VCO (5.1)

We are connecting our vCD to VCO successfully (at least there are no errors), but the objects under vCD never show up, so all workflows that depend on them fail.  The only question for me is what "Organization" to use when registeirng vCD with VCO.  I used "System" and I think that's worked for us in the past.

0 Kudos
1 Solution

Accepted Solutions
FGShepherdP10
Enthusiast
Enthusiast
‎06-03-2013 05:42 AM
Jump to solution

Turns out that there were a couple of mis-configurations on my part:
I used a domain service account to register the plug-in, and when I looked more closely at the vCloud Director plugin under "Administer" in VCO, it was registered to "[serviceAccount]@[domain]@system".  So...not a good start.

Once we created a Local vCloud Director account and registered the plugin with that, it looked more like "[LocalVCDOrchestratorAccount]@sytem" and the underlying objects appeared as expected in VCO.  (When registering, I did not include an "@sytem" in the user name.)

Some other information that we used during registration of the plugin: "Basic Authentication" and "Shared session" (in addition to using "system" as the Organization).

Everything is working as expected again.

Thanks to both of you for the input.  Definitely tracking right along with what ultimately solved the issue.

View solution in original post

0 Kudos
3 Replies
cdecanini_
VMware Employee
VMware Employee
‎05-31-2013 06:37 AM
Jump to solution

Use system / admin account to start with.

Do you use a load balancer ? if so make sure the plug-in url matches the public API one

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vCenter Orchestrator tips and tutorials - @vCOTeam on Twitter
Burke-
VMware Employee
VMware Employee
‎05-31-2013 06:39 AM
Jump to solution

What builds are you using?

vCO:

vCloud Director:

vCloud Director plug-in for vCO:

When configuring the plug-in, use SYSTEM and an appropriate SYSTEM level administrator (with shared session) if you wish to have full access to the vCD environment - common where you are running a private cloud. If you are simply a tenant of a cloud, then you would enter your organization name and provide an appropriate Org level user if using shared session.

I've not run into issues using vCO 5.1 with the GA'd vCloud Director plug-in (5.1 build 538) connecting to vCloud Director 5.1, 5.1.1, and 5.1.2 as a SYSTEM level administrator.

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you!

Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator
for vRealize Orchestrator tips and tutorials - @TechnicalValues on Twitter
FGShepherdP10
Enthusiast
Enthusiast
‎06-03-2013 05:42 AM
Jump to solution

Turns out that there were a couple of mis-configurations on my part:
I used a domain service account to register the plug-in, and when I looked more closely at the vCloud Director plugin under "Administer" in VCO, it was registered to "[serviceAccount]@[domain]@system".  So...not a good start.

Once we created a Local vCloud Director account and registered the plugin with that, it looked more like "[LocalVCDOrchestratorAccount]@sytem" and the underlying objects appeared as expected in VCO.  (When registering, I did not include an "@sytem" in the user name.)

Some other information that we used during registration of the plugin: "Basic Authentication" and "Shared session" (in addition to using "system" as the Organization).

Everything is working as expected again.

Thanks to both of you for the input.  Definitely tracking right along with what ultimately solved the issue.

0 Kudos