Accommodate more than 20 vCenter on a single vRO instance

[sandy_1234]

Hi All,

As per the vRO documentation the number of vCenter that can be added to a Single vRO instance is 20. Given this fact in our cloud environment we have 50 vCenter (ie one vCenter per customer).  We were thinking on a solution to overcome this problem statement. (Listed below)

1. Removing a vCenter instance post execution of the workflow. But we couldn't find an API in swagger UI that tags/relates the workflow execution status with vCenter.

2. Assume the scenario we have added 20 vCentrer, if we have to take out vCenter which is not being used or currently having any workflow execution, how can we identify those programmatically? Any pointers or Alternate thoughts  guys ???

Thanks

Sandeep

[iiliev · Accepted solution]

Hi,

The number of vCenter servers managed by a single vRO doesn't have a hard-coded upper limit. If you already have 20 vCenters registered in vRO and then you try to add one more, the workflow won't fail with an error that no more vCenters can be added. It all depends on the load, like the number of workflows executed concurrently, what exactly these workflows do, etc. So it is possible that in your case a single vRO instance can deal just fine with 50 vCenters, although some parts like vRO UI client inventory can become slower when there are many severs/objects in the inventory.

Another option to consider is to somehow 'clusterize' your vCenters by some criteria, eg. by geographic region/country, and use a separate vRO instance for each zone.

Constantly removing/adding vCenters depending on their usage is probably doable but seems not desirable to me. You can easily lose track which workflow is executed where, and you put some limitations on the workflows being executed, like they should not be very long running (otherwise the vCenter they use will be marked as used for a long time), etc. Sounds complicated to me.