Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Installing vCloud Director 5.1.x best practices (2034092)

Purpose

VMware vCloud combines a vCloud Director server group with the vSphere platform. You create a vCloud Director server group by installing vCloud Director software on one or more servers, connecting the servers to a shared database, and integrating the vCloud Director server group with vSphere.

VMware vCloud Director builds on the VMware vSphere foundation and exposes virtualized shared infrastructure as multitenant virtual datacenters that are decoupled from the underlying hardware and isolated from one another. You can expose virtual datacenters to users through a Web-based portal and define and expose a catalog of services that you can deploy within the virtual datacenter.

This article outlines the basic configurations that are necessary to get started with vCloud Director 5.1.

Note: For more information, see the vCloud Director Installation and Upgrade Guide. The guide contains definitive information. If there is a discrepancy between the guide and this article, assume that the guide is correct.

Resolution

The initial configuration of vCloud Director, including database and network connection details, is established during installation. When you upgrade an existing installation to a new version of vCloud Director, you update the vCloud Director software and database schema, leaving the existing relationships between servers, the database, and vSphere in place.

Configuration planning

provides storage, compute, and networking capacity to vCloud Director. Before you begin installation, consider how much vSphere and vCloud Director capacity you need, and plan a configuration that can support it.

Configuration requirements depend on many factors, including the number of organizations in the cloud, the number of users in each organization, and the activity level of those users. These guidelines can serve as a starting point for most configurations:
  • Allocate one vCloud Director server (cell) for each vCenter server that you want to make accessible in your cloud.
  • Be sure that all vCloud Director servers meet at least the minimum requirements for memory, CPU, and storage detailed in vCloud Director Hardware and Software Requirements.

vCloud Director hardware and software requirements

Each server in a vCloud Director server group must meet certain hardware and software requirements. In addition, a supported database must be accessible to all members of the group. Each server group requires access to a vCenter Server, a vShield Manager server, and one or more ESXi/ESX hosts.

For information on the supported vCenter Server, ESXi/ESX, and vShield Manager versions, see the VMware Product Interoperability Matrixes.

vSphere configuration requirements

vCenter Servers and ESXi/ESX hosts intended for use with vCloud Director must meet specific configuration requirements. The requirements include:
  • vCenter Server networks intended for use as vCloud Director external networks or network pools must be available to all hosts in any cluster intended for vCloud Director to use. Making these networks available to all hosts in a datacenter simplifies the task of adding new vCenter Servers to vCloud Director.
  • DVS must be used for cross-host fencing and network pool allocation.
  • vCenter Server clusters used with vCloud Director must be configured to use automated DRS. Automated DRS requires shared storage attached to all hosts in a DRS cluster.
  • vCenter Servers must trust their ESXi/ESX hosts. All hosts in all clusters managed by vCloud Director must be configured to require verified host certificates. In particular, you must determine, compare, and select matching thumbprints for all hosts. For more information, see Configure SSL Settings in the vCenter Server and Host Management Guide.

vSphere licensing requirements

vCloud Director requires these vSphere licenses:
  • VMware DRS, licensed by vSphere Enterprise and Enterprise Plus.
  • VMware Distributed Switch and dvFilter, licensed by vSphere Enterprise Plus. This license enables creation and use of vCloud Director isolated networks.

Supported vCloud Director operating systems

The supported operating systems that can be installed for vCloud include:
  • Red Hat Enterprise Linux 5 (64-bit), Update 4
  • Red Hat Enterprise Linux 5 (64-bit), Update 5
  • Red Hat Enterprise Linux 5 (64-bit), Update 6
  • Red Hat Enterprise Linux 5 (64-bit), Update 8
  • Red Hat Enterprise Linux 6 (64-bit), Update 1
  • Red Hat Enterprise Linux 6 (64-bit), Update 2
  • Red Hat Enterprise Linux 6 (64-bit), Update 3

Disk Space Requirements Each vCloud Director server requires approximately 950 MB of free space for the installation and log files.
Memory Requirements Each vCloud Director server must be provisioned with at least 1 GB of memory. 2 GB is recommended.
Linux Software Packages Each vCloud Director server must include installations of several common Linux software packages. These packages are typically installed by default with the operating system software. If any are missing, the installer fails with a diagnostic message.

Required software packages:

Package name Package name Package name
alsa-lib libICE module-init-tools
bash libSM net-tools
chkconfig libstdc pciutils
coreutils libX11 procps
findutils libXau redhat-lsb
glibc libXdmcp sed
grep libXext tar
initscripts libXi which
krb5-libs libXt
libgcc libXtst

Supported vCloud Director databases

vCloud Director supports Oracle and Microsoft SQL Server databases. The most current information about supported databases is available from the VMware Product Interoperability Matrixes.

For information on how to configure your database, see Installing and configuring a vCloud Director 5.1 database (2034540).

Supported LDAP servers

These LDAP platforms are supported:

Platform LDAP server Authentication methods
Windows Server 2003 Active Directory Simple, Simple SSL, Kerberos, Kerberos SSL
Windows Server 2008 Active Directory Simple
Windows 7 (2008 R2) Active Directory Simple, Simple SSL, Kerberos, Kerberos SSL
Linux OpenLDAP Simple, Simple SSL

Supported guest operating systems

vCloud Director 5.1 supports a wide variety of operating systems. For more information on support and customization, see Supported Guest Operating Systems in vCloud Director 5.1 (2034491).

Creating SSL certificates for vCloud Director

vCloud Director requires SSL to secure communications between clients and servers. Before you install and configure a vCloud Director server group, you must create two certificates for each member of the group and import the certificates into host keystores.

Each vCloud Director server that you intend to use in a vCloud Director cluster requires two SSL certificates, one for each of its IP addresses.

Note: All directories in the pathname to the SSL certificates must be readable by the user vcloud.vcloud. This user is created by the vCloud Director installer.
  1. List the IP addresses for this server. Use a command such as ifconfig to discover this server's IP addresses.
  2. For each IP address, run this command to retrieve the fully qualified domain name to which the IP address is bound:

    nslookup ip-address

  3. Make a note of each IP address, the fully qualified domain name associated with it, and whether vCloud Director should use the address for the HTTP service or the console proxy service. You need the fully qualified domain names when you create the certificates, and the IP addresses when you configure network and database connections.
  4. Create the certificates. You can use certificates signed by a trusted certification authority, or self-signed certificates. Signed certificates provide the highest level of trust. A 2,048-bit key length provides a high level of security. For more information, see Generating SSL certificates for VMware vCloud Director (1026309).

Installing and configuring vShield

vCloud Director depends on vShield to provide network services to the cloud. Install and configure vShield before you begin installing vCloud Director.

You must associate each vCenter Server that you add to vCloud Director with a unique instance of vShield. For information about the network requirements and supported versions of vShield, see Installing vCloud Networking and Security 5.1.x best practices (2034173).

This procedure applies only to new installations of vCloud Director. If you are upgrading an existing installation of vCloud Director, you can optionally upgrade its associated vShield installation. A new release of vShield cannot work with an existing release of vCloud Director. For more information, see Upgrading to vCloud Networking and Security 5.1.1 best practices (2034699).

Installing and configuring an AMQP broker

AMQP, the Advanced Message Queuing Protocol, is an open standard for message queuing that supports flexible messaging for enterprise systems. vCloud Director includes an AMQP service that you can configure to work with an AMQP broker, such as RabbitMQ, to provide cloud operators with a stream of notifications about events in the cloud. If you want to use this service, you must install and configure an AMQP broker.

  1. Download the RabbitMQ Server from the VMware RabbitMQ page.
  2. Follow the RabbitMQ installation instructions to install RabbitMQ on any convenient host. The RabbitMQ server host must be reachable on the network by each vCloud Director cell.
  3. During the RabbitMQ installation, make a note of the values that you need to supply when configuring vCloud Director to work with this RabbitMQ installation:

    • The fully-qualified domain name of the RabbitMQ server host. For example, amqp.example.com.
    • A username and password that are valid for authenticating with RabbitMQ.
    • The port at which the broker listens for messages. The default is 5672.
    • The RabbitMQ virtual host. The default is /.

Download and install the VMware public key

The installation file is digitally signed. To verify the signature, you must download and install the VMware public key. You can use the Linux rpm tool and the VMware public key to verify the digital signature of the vCloud Director installation file, or any other signed downloaded file from VMware.com.

If you install the public key on the computer where you plan to install vCloud Director, the verification happens as part of the installation or upgrade. You can also manually verify the signature before you begin the installation or upgrade procedure, then use the verified file for all installations or upgrades. For more information on this procedure, see Downloading and installing the VMware Public Key to validate a vCloud Director installation (2005832).

Creating a vCloud Director server group

A vCloud Director server group consists of one or more vCloud Director servers. Each server in the group runs a collection of services called a vCloud Director cell. To create a server group, you install vCloud Director software on each server, configure its network and database connections, and start its vCloud Director services. For more information, see the vCloud Installation and Upgrade Guide.

Note: This procedure is for new installations only. If you are upgrading an existing vCloud Director installation, see Upgrading to vCloud Director 5.1.x best practices (2034980).

See Also

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 15 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 15 Ratings
Actions
KB: