Installing vCloud Director 5.1.x best practices (2034092)
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.
- 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 Server clusters used with vCloud Director must not enable storage DRS.
- vCenter Servers must trust their ESX/ESXi 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. See Configure SSL Settings in the vCenter Server and Host Management documentation.
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.
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
Disk Space Requirements
Each vCloud Director server requires approximately 950MB of free space for the installation and log files.
Each vCloud Director server must be provisioned with at least 1GB of memory. 2GB 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
|Package Name||Package Name||Package Name|
|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|
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).
- List the IP addresses for this server. Use a command like ifconfig to discover this server's IP addresses.
- For each IP address, run the following command to retrieve the fully qualified domain name to which the IP address is bound:
- 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.
- 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 vShield 5.1 best practices (2034173).
Download the RabbitMQ Server from http://info.vmware.com/content/12834_rabbitmq.
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.
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 /.
- Generating SSL certificates for VMware vCloud Director
- Downloading and installing the VMware Public Key to validate a vCloud Director installation
- Installing vCloud Networking and Security 5.1.x best practices
- Supported guest operating systems in vCloud Director 5.1
- Installing and configuring a vCloud Director 5.1 database
- Upgrading to vCloud Networking and Security 5.1.x best practices
- Upgrading to vCloud Director 5.1 best practices