Before you start deploying and configuring VMware Cloud Director Availability, verify that the service users meet the following requirements.
Cloud Service Users Requirements
The Cloud Service makes a difference between admin users and regular users. To start a session with administrator privileges, the credentials you enter for both of the VMware Cloud Director™ sites must belong to the ADMINISTRATORS or VRADMINISTRATORS group. For example, the Administrator@vsphere.local single sign-on user you enter when logging into the management portal, is a member of the ADMINISTRATORS group.
VMware Cloud Director Availability User Sessions Requirements
Each VMware Cloud Director Availability user session is guaranteed to have a VMware Cloud Director user and VMware Cloud Director organization associated with the session.
To manage VMware Cloud Director Availability workloads and the local Cloud Service appliance as a service provider, you start a user session as a VMware Cloud Directorsystem administrator by using VMware Cloud Director user name and password. System administrator users can manage any local and monitor any remote VMware Cloud Director Availability inventory workload. To manage VMware Cloud Director Availability workloads in the remote sites, you must authenticate as a system administrator to the remote site.
For disaster recovery workflows and managing local VMware Cloud Director Availability workloads as a tenant user, you start a user session as a VMware Cloud Director organization administrator by using VMware Cloud Director credentials. As an organization administrator, for disaster recovery workflows in the local site, you can manage any local VMware Cloud Director Availability workload, and can monitor any remote VMware Cloud Director Availability workload that belongs to the respective VMware Cloud Director organization. To manage remote VMware Cloud Director Availability workloads, you must authenticate to the corresponding remote organization.
The following table lists Cloud Service disaster recovery operations that require sessions on either of the sites, or both.
| Operation | Incoming Replication | Outgoing Replication | ||
|---|---|---|---|---|
| Required Session on Source Site | Required Session on Destination Site | Required Session on Source Site | Required Session on Destination Site | |
| start | Yes | Yes | Yes | Yes |
| stop | No | Yes | Yes | Yes |
| reconfigure | No | Yes | Yes | Yes |
| failover | No | Yes | Yes | Yes |
| migrate | Yes | Yes | Yes | Yes |
| sync | No | Yes | Yes | Yes |
| pause | No | Yes | Yes | Yes |
| resume | No | Yes | Yes | Yes |
| reverse | Yes | Yes | Yes | Yes |
| failover test | No | Yes | Yes | Yes |
| failover test cleanup | No | Yes | Yes | Yes |
For more information about authenticating to remote sites, see Authenticating to Remote Sites in the User Guide.
