vcloud director installation need

this post will talk about vloud director 5.1installation needs
 
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
• Red Hat Enterprise Linux 6.3 (64-bit)

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.

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.

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. 

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. 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

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.

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.

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.

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