This article will describe the steps necessary to install and configure VMware vCenter Orchestrator (VCO). Parts of the configuration are often a challenge even for experienced administrators. My goal here is to help you get a functional VCO server up and running.
I've even put together a step-by-step video on How to Install vCenter Orchestrator here on vCOTeam.info ! Take a look & tell your colleagues!
Updated comments for vCO 4.1 and newer
This section updated Feburary, 2011 to note differences in vCO 4.1 and newer
The article below was written for vCenter Orchestrator 4.0. As such, the requirements listed are applicable to versions of vCO lower than the currently available release.
vCO 4.1.x Deployment Best Practices
vCenter Orchestrator can be a powerful tool for your environment provided you follow some simple guidelines to get the best performance possible.
First off, you should make sure that your DNS is current and includes forward/reverse lookup entries for your vCenter Server(s), vCO Server, and any other systems you intend to interact with.
Although vCO supports connecting up to 10 vCenter Servers, it is best to limit this based on your vCenter usage... meaning, if you have maxed the capacity of a vCenter Server you have connected to vCO, then use another vCO server for other vCenter Servers.
It is also a good idea to place a vCO server in each geographic location of your vCenter Servers to minimize WAN traffic and keep API access optimal.
Hardware: (VMware vCenter Orchestrator (vCO) Documentation)
- Dual CPU and 4 GB of memory
- 2 GB drive space
- Virtual or Physical server
- 1 GB NIC
- Windows 2003 - 64-bit
- Windows 2008 - 64-bit (Enterprise, Standard, Datacenter)
- Windows 2008 R2 - 64-bit
DB: (vSphere Compatibility Matrix)
The vCO Database should be on a separate server with at least 10 GB of free space available. The DB server should also be in the same DataCenter as the vCO Server. As of vCO 4.1.1, the following Databases are supported:
- SQL Server 2005 Express
- SQL Server 2005 Standard/Enterprise (SP3) 32 or 64 bit
- SQL Server 2008 Standard/Enterprise (SP1/SP2) 32 or 64 bit
- Oracle 10g Standard/Enterprise (Release 2) 32 or 64 bit
- Oracle 11g Standard/Enterprise (Release 1) 32 0r 64 bit
Getting Started with vCenter Orchestrator 4.0
Things I recommend to get started:
- Domain (Windows 2003/2008)
- SQL Server with DB created
- vSphere vCenter Server
- 1 or more ESX/ESXi hosts
- License !!!
- Windows 2003/2008 Server (can be 32-bit or 64-bit for vCO 4.0 and under, 64-bit is required as of vCO 4.1)
You'll need to start off by preparing the following:
- Prepare a Database
- Download Installation media
- Prepare a Server for the vCO installation
- Install vCO software
- Configure vCO software
Preparing VCO Database
For ease of use and simplicity, this how-to will describe the steps necessary to prepare a Microsoft SQL Server database for use with vCenter Orchestrator. There is no official support for SQL Server Express, and this is certainly NOT recommended or supported in a production environment... but, for a POC/Learning/Demo environment, you should be okay with using SQL Express 2005 or 2008. My personal recommendation for a test environment would be SQL Server 2008 Express edition with advanced tools (Includes SQL Server Management Studio).
Officially, you should use SQL Server 2005 or Oracle 10.
When using SQL Server, the following points should be observed:
- Ensure that you ENABLE TCP
- Confirm the Port is set to 1433 (you may have to make a note of the dynamic port if you have troubles)
- Create a database (I suggest "VCO") and grant appropriate rights to a service account to be used by vCO
- Make note of the DB Server machine name and the domain it belongs to (if applicable)
We'll go into more detail in the Configure vCO software section.
Download Installation Media
vCenter Orchestrator is shipped with vCenter Server for vSphere. So you'll need a valid license (or trial license) in order to obtain the software. I should note that Essential and Essential Plus are not sufficient if you wish to create your own workflows. You should have a Standard license as a minimum.
Visit the VMware website to access your downloads.
Download the appropriate files to a place that will be easily accessible to your vCO server.
Prepare a Server for the vCO installation
I do recommend a Windows 2008 64-bit server for the vCenter Orchestrator server even though a 32-bit server is acceptable for vCO 4.0.1 (build 4502)... Ideally, this server should be a member server in your domain and you should have administrative rights to it. The server should meet the following minimum requirements (either Physical or Virtual, but Virtual is recommended):
- 2 GB of Memory ( vCO 4.0 and under, 4GB for vCO 4.1 and newer)
- 2 CPU/vCPU
- 10+ GB free disk space
- Minimum of 1 NIC
It is critical that you not skimp on memory for your vCO server - especially if you're in a demo/dev environment where you've decided to run vCO on the same server as vCenter and your DB !!! - if this is the case, it may be advisable to bump up the memory to 4GB. Please note that this configuration is NOT RECOMMENDED for production use!
Copy/upload the vCenter Orchestrator installer file to your vCO server or map a drive to the share that holds the files.
Install vCO Software
Login to your vCO server via Remote Desktop or using the Console (via vSphere vCenter Server if VM).
Execute the installer file: vCenterOrchestrator_4_0_1_4502.exe
Review and accept the License, Click Next
Set the installation path and Click Next
Choose Client - Server and then Click Next
Specify where you want the icons created and Click Next
Review the summary and Click Install
That completes the installation of vCenter Orchestrator 4.0.1 (4502)! Congratulations! Now you'll need to configure vCO before you can use it. To see vCenter Orchestrator get installed and configured, follow along in the step-by-step video - the video is more complete than this article!