About VMware Cloud Director Service

VMware Cloud Director™ service is a cloud-service delivery application that uses an underlying infrastructure provided by VMware Cloud on AWS, Google Cloud VMware Engine, on-premises vSphere environments, or Azure VMware Solution. By using the VMware Cloud Director service, service providers can deliver virtual infrastructure resources in a multitenant cloud environment.

With VMware Cloud Director service, service providers can provision VMware Cloud Director instances in a SaaS model. By leveraging VMware Cloud Director's multisite feature, providers can pair a VMware Cloud Director service instance with an on-premises VMware Cloud Director instance and expand their environments.

What's New August 2022

  • Initial Availability of Support for Azure VMware Solution Infrastructure Environment

    You can now associate VMware Cloud Director instances with SDDCs backed by Azure VMware Solution infrastructure environment. For more information, see How Do I Configure VMware Cloud Director service on Microsoft Azure VMware Solution. As a service provider or enterprise customer, you can use VMware Cloud Director service as a single pane of glass from which to manage Azure VMware Solution, VMware Cloud on AWS, Google Cloud VMware Engine, and on-premises vSphere resources.

  • API Support for Migration From On-premises VMware Cloud Director to VMware Cloud Director Service

    You can use the VMware Cloud Director API to migrate your on-premises VMware Cloud Director installation that is using on-premises vSphere resources to VMware Cloud Director service. For detailed instructions, see How Do I Migrate from On-premises VMware Cloud Director to VMware Cloud Director service.

What's New July 2022

What's New June 2022

  • VMware Cloud Director 10.3.3.1 Support

    VMware Cloud Director service supports VMware Cloud Director 10.3.3.1 for new deployments and for upgrades. For more information, see VMware Cloud Director 10.3.3.1 Release Notes.

What's New May 2022

  • Global Availability of Support for Google Cloud VMware Engine and On-Premises Infrastructure Environments

    You can now associate VMware Cloud Director instances with SDDCs backed by either Google Cloud VMware Engine or on-premises vSphere environments. As a service provider, you can use VMware Cloud Director service as a single pane of glass from which to manage VMware Cloud on AWS, Google Cloud VMware Engine, and on-premises vSphere resources. See How Do I Associate a VMware Cloud Director Instance with an SDDC via VMware Reverse Proxy.

What's New February 2022

  • Support for Integration with VMware Cloud on AWS or VMware Cloud Services Platform

    You can create a trusted connection between VMware Cloud Director service and other solutions, such as VMware Cloud on AWS or VMware Cloud Services Platform.

  • Retrieve Public IP Addresses Used by a VMware Cloud Director Instance 

    You can retrieve the public IP addresses that your VMware Cloud Director instance uses to establish connections to external services. See How Do I Retrieve the Public IP Addresses for My VMware Cloud Director Instance.

  • In-product Feedback

    When a pop-up feedback request appears, you can use the form in the VMware Cloud Director service UI to provide direct feedback about your experience and to reach out about any product-related questions that you have.

What's New January 2022

  • Support for Multiple Subscriptions

    As a provider, you can create and manage multiple subscriptions through the Subscriptions tab on the left of the VMware Cloud Director service page in VMware Cloud Partner Navigator. You can configure each subscription with a separate start and end date, with a 1-year or a 3-year term, and with separate payment options.

What's New December 2021

  • Support for Adding Contact Data During Organization Creation

    As a provider, you can add organization contact data, such as an address, zip code, city, and country, when you create an organization.

What's New November 2021

  • Automatic AWS Certification

    You no longer have to manually add AWS S3 certifications to your vCenter Server instance. AWS S3 certifications are automatically added during association.

  • Support Level Control

    You can now set the support level for each VMware Cloud Director instance in your environment upon its creation or modify it later, depending on your needs. When you create a VMware Cloud Director instance, the default support level for this instance is level 3, which means that VMware technical support personnel can access the instance to provide support and maintenance. If the support level of an instance is set higher than level 1, error logs from VMware Cloud Director are automatically sent to VMware vRealize Log Insight Cloud and reviewed by customer support to improve performance.

What's New October 2021

  • VMware Cloud Director 10.3.1 Support

    VMware Cloud Director service supports VMware Cloud Director 10.3.1 for all new deployments. For more information, see VMware Cloud Director 10.3.1 Release Notes.

  • Upgrade Notifications

    VMware Cloud Director service now notifies you when new major versions of VMware Cloud Director become available and when scheduled minor upgrades are coming. You can view and manage the upgrade of your VMware Cloud Director instances by navigating to the Maintenance panel in each VMware Cloud Director instance details. See How VMware Cloud Director Instance Upgrade Works.

  • Auto Scale in Extensions UI

    VMware Cloud Director service can now automate the enablement of the Auto Scale Group feature, which tenants can use to auto scale applications. To activate the feature, navigate to the Extensions panel in the VMware Cloud Director instance details.

What's New September 2021

  • Subscription Management UI Framework

    With the Subscription Management framework, you can manage 1-year and 3-year subscriptions of VMware Cloud Director instances within VMware Cloud Director service. On the Subscriptions tab on the left of the VMware Cloud Director service, you can view your current subscriptions and create new ones.

What's New August 2021

  • VMware Cloud Director 10.3 Support

    VMware Cloud Director instance deployments now support deploying VMware Cloud Director 10.3.

  • UI for Deployment Instance Errors

    Deployment instance errors now appear in an alert banner on the instance card. The banner has a brief description and a link to "details" where the user can click to open a modal that displays the full error message.

What's New July 2021

  • Support for associated instances in the VMware Cloud Director service UI

    The VMware Cloud Director service UI displays a tab called ‘Associated Instances’ next to the ‘Deployed Instances’ tab on the VMware Cloud Director instances page. The 'Associated Instances' tab lists all the on-prem VMware Cloud Director instances that are associated with VMware Cloud Director service instances through multisite association within your VMware Cloud organization.

  • Support for IPsec policy-based VPN for NSX-T Data Center edge gateways

    The IPsec policy-based VPN for NSX-T edge gateways feature is available upon request. To request this feature, you must open a VMware Cloud Director service support ticket.

What's New June 2021

  • Upgrade Notifications

    Cloud providers are notified of upcoming VMware Cloud Director instance upgrades through the VMware Cloud Director service UI and in the VMware Cloud Director instance itself.

  • API enhancement

    Added API support to retrieve SSL thumbprints for VMware Cloud Director instances in the VMware Cloud Director service.

What's New May 2021

  • Service Reliability: Improved security for VMware Cloud Director instances databases

What's New April 2021

  • Automatic cleanup of inactive cells

    VMware Cloud Director service now automatically removes inactive cells that are the result of VMware Cloud Director running in a containerized environment.

  • VMware Cloud Director instance recovery

    You can recover a VMware Cloud Director instance within 7 days after you deleted it.

  • Improved support for OVF packages upload

What's New March 2021

  • Support for VMware Cloud services provider environment in Sydney, Australia

    You can now use Sydney, Australia, as a VMware Cloud services provider environment in which to deploy VMware Cloud Director instances.

  • OAuth configuration flow improvements

  • VMware Cloud Director 10.2.1 support

    Upgrades of deployed VMware Cloud Director instances to version 10.2.1 are now supported.

What's New February 2021

  • Added API support for certificate thumbnail retrieval for VMware Cloud Director instances

    When you run a GET call to retrieve information about a specific VMware Cloud Director instance, the response retrieves the thumbprints for the public certificates that are associated with the instance.

  • Added API support for retrieving the most recent VMware Cloud Director session

    You can use the /latestSessionEvent environment API endpoint to retrieve information about the most recent user to log into a VMware Cloud Director instance and the time of the login.

  • OAuth support

    You can establish a trust relationship between VMware Cloud Services and VMware Cloud Director service, and you can configure VMware Cloud Services as an identity provider for VMware Cloud Director.

  • Added API support for listing configuration issues

    You can use the /configIssues API endpoint to retrieve a list of configuration issues.

  • Added API support for retrieving information about associated on-premises VMware Cloud Director instances

    You can use the /associatedInstances environment API endpoint to retrieve information about associated on-premises VMware Cloud Director instances within your VMware Cloud organization, including information on SDDCs, provider VDCs, VDCs, organizations, and reachability of a specific on-prem instance.

What's New November 2020

  • Global availability of the VMware Cloud Director service

    You can deploy VMware Cloud Director instances in US West, Frankfurt, and Tokyo, and make them available to any SDDC within 150ms of latency. This means that you can deploy VMware Cloud on AWS SDDCs in most North America, EU, and APJ availability zones for use with VMware Cloud Director service.

Compatibility

The products and services with which VMware Cloud Director is compatible are listed in the VMware Product Interoperability Matrices.

Caveats and Limitations

There are some caveats and limitations to consider when using VMware Cloud Director service.

  • VMware Cloud Director service does not provide RabbitMQ. If you plan to use API extensions, blocking tasks, extension services, object extensions, and notifications, you will need to deploy a RabbitMQ server on your own.
  • All VMware Cloud Director service components are deployed with self-signed certificates. As certificates that are signed by a trusted certification authority (CA) provide the highest level of trust, you can replace the self-signed certificates with CA-signed certificates.
  • VMware Cloud Director service supports two-cell deployments and the ability to increase the number of cells in your environment.
  • VMware Cloud Director service does not support the CPOM extension plug-in.
  • VMware Cloud Director service does not support using VMware® vRealize Orchestrator plug-in.
  • VMware Cloud Director expects the VMware Cloud on AWS SDDC to be a brand new deployment for the initial association. SDDCs that already have services configured, such as HCX, are not supported.

Resolved Issues

  • Deploying VMs from the same catalog template results in duplicate UUIDs

    When a tenant deploys more than one VM from the same catalog template, the UUID of the resulting VMs are the same.

Known Issues

  • Some operations in VMware Cloud Director fail after a restart of the reverse proxy appliance

    If you are using a reverse proxy service to connect VMware Cloud Director to your infrastructure resources, the reverse proxy appliance periodically restarts, which might cause some operations in VMware Cloud Director to fail.

    Restart manually the operations that are failing.

  • Attempting to associate a VMware Cloud Director Instance with a VMware Cloud on AWS SDDC via proxy fails

    Attempting to associate a VMware Cloud Director Instance with a VMware Cloud on AWS SDDC fails with the following exception: Update session callback failed. This happens because the vCenter Server instance does not accept the certificate provided by the AWS CloudFront service.

    Workaround:

    1. From a system with internet connectivity that has access to CloudFront, run the command to download the certificate chain.
      openssl s_client -showcerts -verify 5 -connect dx3g6q79ni7gl.cloudfront.net:443 < /dev/null | awk '/BEGIN/,/END/{ if(/BEGIN/){a++}; out="cert"a".pem"; print >out}'; for cert in *.pem; do newname=$(openssl x509 -noout -subject -in $cert | sed -nE 's/.*CN ?= ?(.*)/\1/; s/[ ,.*]/_/g; s/__/_/g; s/_-_/-/; s/^_//g;p' | tr '[:upper:]' '[:lower:]').pem; echo "${newname}"; mv "${cert}" "${newname}"; done
    2. Upload the certificates to the vCenter Server instance with which you want to associate the VMware Cloud Director instance.

      3.1. Log in to vCenter Server as administrator.

      3.2. Select Administration.

      3.3. Under Certificates, click Certificate Management and then click Add.

      3.4. Browse to the certificate chain and upload it.

    3. Retry the association.

  • Attempting to create a VM, to add a VM hard disk, to upload a template, or to upload a media file to an organization VDC catalog fails

    When a tenant attempts to create a VM, or add a VM hard disk, or upload a media file or a template to an organization VDC catalog, the operation fails with the following error.

     {vim.fault.NoPermission) { faultCause = null, faultMessage = null, object = ManagedObjectReference: type = Datastore, value = datastore-17, serverGuid = null, privilegeId = Datastore.AllocateSpace } - Permission to perform this operation was denied.

    This issue occurs when the service provider has added an unusable storage profile to the provider VDC in which your organization VDC was created.

    Workaround: In the VMware Cloud Director Service Provider Admin Portal, verify that the WorkloadDatastore is the only datastore enabled for use by the provider VDC.

check-circle-line exclamation-circle-line close-line
Scroll to top icon