The VMware Cloud Director Multisite feature enables a service provider or a tenant of multiple, geographically distributed VMware Cloud Director installations (server groups) to manage and monitor those installations and their organizations as single entities.

When you associate two VMware Cloud Director sites, you enable administration of the sites as a single entity. You also enable organizations at those sites to form associations with each other. When an organization is a member of an association, organization users can use the VMware Cloud Director Tenant Portal to access organization assets at any member site, although each member organization and its assets are local to the site it occupies.

Note:

You must use the VMware Cloud Director API to associate sites. The sites must be with the same VMware Cloud Director API version, or one version apart. For example, you can associate a VMware Cloud Director 10.0 (API version 33.0) site with a VMware Cloud Director site version 9.7, 10.0, or 10.1, respectively API versions 32.0, 33.0, or 34.0.

After you associate two sites, you can use the VMware Cloud Director API or the VMware Cloud Director Tenant Portal to associate organizations that occupy those sites. See the VMware Cloud Director API Programming Guide and the VMware Cloud Director Tenant Portal Guide.

A site or organization can form an unlimited number of associations with a peer, but each association includes exactly two members. Each site or organization must have its own private key. Association members establish a trust relationship by exchanging public keys, which are used to verify signed requests from one member to another.

Each site in an association is defined by the scope of a VMware Cloud Director server group (a group of servers that share a VMware Cloud Director database). Each organization in an association occupies a single site. The organization administrator controls access by organization users and groups to assets at each member site.

Site Objects and Site Associations

The installation or upgrade process creates a Site object that represents the local VMware Cloud Director server group. A system administrator whose authority extends to more than one VMware Cloud Director server group can configure those server groups as an association of VMware Cloud Director sites.

Associations of Organizations

After site association is complete, organization administrators at any member site can begin associating their organizations.
Note: You cannot associate a System organization with a tenant organization. The System organization at any site can be associated only with the System organization at another site.

User and Group Identities

Associations of sites and organizations must agree to use the same identity provider (IDP). User and group identities for all organizations in the association must be managed through this IDP.

Except for the System organization, which must use the VMware Cloud Director integrated IDP, associations are free to choose the IDP that works best for them.

Site Access Control for Organization Users and Groups

Organization administrators can configure their IDP to generate user or group access tokens that are valid at all member sites, or valid at only a subset of member sites. While user and group identities must be the same in all member organizations, user and group rights are constrained by the roles those users and groups are assigned in each member organization. Assignment of a role to a user or group is local to a member organization, as are any custom roles you create.

Load Balancer Requirements

Effective implementation of a Multisite deployment requires you to configure a load balancer that distributes requests arriving at an institutional endpoint such as https://vcloud.example.com to the endpoints for each member of the site association (for example, https://us.vcloud.example.com and https://uk.vcloud.example.com). If a site has more than one cell, you must also configure a load balancer that distributes incoming requests across all its cells, so that a request to https://us.vcloud.example.com can be handled by https://cell1.us.vcloud.example.com , https://cell2.us.vcloud.example.com, and so on.

Association Member Status

After you have created an association of sites or organizations, the local system periodically retrieves the status of each remote association member and updates that status in the local site's VMware Cloud Director database. Member status is visible in the Status element of an SiteAssociationMember or OrgAssociationMember. This element can have one of three values:
ACTIVE
The association has been established by both parties, and communication with the remote party was successful.
ASYMMETRIC
The association has been established at the local site, but the remote site has not yet reciprocated.
UNREACHABLE
An association has been created by both parties, but the remote site is not currently reachable on the network.

The member status "heartbeat" process runs with the identity of the Multisite system user, a local VMware Cloud Director user account created in the System organization during VMware Cloud Director installation. Although this account is a member of the System organization, it does not have system administrator rights. It has only a single right, Multisite: System Operations, which gives it permission to make a VMware Cloud Director API request that retrieves the status of the remote member of a site association.