Multiple vCloud Director Severs to one vCenter sever

[aqualityplacem]

We are looking to provide two differently branded vcloud director portals. Ideally we want them both talking to the same vCenter server, using the same cluster resources.

The hope is there is away to give some users access to vcloud.companyA.com and another set of users to vCloud.CompanyB.com

It is important that all the URL's used would be specific to that company

Is this technically possible? or will we need to deploy a vCenter instance and cluster for each company?

[IamTHEvilONE]

It might be technically possible, but there is a lot of logical separation that needs to happen.

1. When installing vCloud, you cannot duplicate the installation 'System Name' or Installation ID across all instances.  the Installation ID is cannot duplicate vCenter's Installation ID as well

2. It would be best to have a unique Distributed Switch per Cluster (per provider to a given vCloud Installation)

3. You'll only need 1 vShield Manager, since it's paired to the vCenter installation ... not the vCloud Installation.

4. Don't overlap other items (IP ranges for public networks, vLANs in use)

5. if there is VXLAN in use, ensure to use different scopes.

This isn't even an exhaustive list.

[aqualityplacem]

Thanks for the reply. I think maybe I am asking for trouble with this. Maybe an alternative would be to look for a third party product that can interface with vCloud Director to allow this to happen. We currently use OnApp which does support VMware and allows us to to this but it only works with vCenter and not vCloud Director. There are all sorts of limitations with their integration, hence looking at using vCloud natively.

[IamTHEvilONE]

why do they specifically need separate sub-domains?

the URLs for an organization are:

vcloudurl.domain.com/cloud/<Org ID>

Most companies I have seen use random alpha numeric values for the Org Name (there is another spot for a friendly name).  So you would get something like this:

vcloudurl.domain.com/cloud/10294424

theoretically, if you use a wildcard certificate you might be able to get away with that ... except that the public addresses part of the vCD installation could be problematic (I would advise against it).

[aqualityplacem]

Basically we do a lot of consultancy for two computer resellers. We are Company A they are Company B and C.

It is important there are no references to any of the other companies when using a specific portal. They don't want their customers to know they are reselling our environment.

Im sure we can do this by building a dedicated portal using the API, but im trying to avoid having to do this off our own back. Not sure if there is already a third party solution for this.

[IamTHEvilONE]

Then why not go full tilt ... two vCenter (one vshield manager each) + 2 vCD environments.

That's pretty much the optimal fashion if you are basically like a CoLo + IT for Company B and C.

All you would have to do is normal network segregation and be done with it.