Quantcast
Channel: VMware Communities : Discussion List - vRealize Orchestrator
Viewing all articles
Browse latest Browse all 6251

run VM workflow against single vcenter sdk connection

$
0
0

Hi everyone,

 

I'm running vCO 5.5.1 appliance, connected to 13 vCenters spread around the world. Yea I know, probably not the best idea, but it does seem to work fine. We aren't really in a position to re-architect to take advantage of cluster mode at the moment...

 

Anyway, with that many vCenter connections to vCO, even simple VM operations are taking quite a long time. This is due mostly to the fact that even simple workflows that start/stop VMs seem to rely on querying ALL the SDK connections in vCO. We provide a VM name (or UUID) as input, and vCO then queries all our vCenters until it can return a VC:VirtualMachine object, which is then used as the real input parameter to execute the VM-related workflows in question.

 

Does anyone know of a more effective/efficient way to have vCO retrieve the VC:VirtualMachine object, instead of iterating over all the SDK connections?


Viewing all articles
Browse latest Browse all 6251

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>