In case you missed the announcement, the barrier to entry for vCenter Orchestrator was just lowered significantly with VMwareâ€™s release of the vCO 4.2 vApp. Here, weâ€™ll talk about installing it.
Installing the vCO vApp
Basically, Iâ€™m assuming that you have an edition of vSphere that is licensed for vCenter and have downloaded both the OVF and VMDK files from the VMware download page:
Once you have the bits, do the following:
- Fire up the vSphere client, login.
- File > Deploy OVF Templateâ€¦
- Aim the wizard where you put the files:
- Accept the EULA
- Give it a Name & Location
- Pick your host/cluster
- Disk (itâ€™s all greyed out)
- Properties (This is where you set your static IPs):
Even though most of the vApp comes configured out of the box, there are still some additional steps you need to do once the VM has been deployed:
- Select the VM in the client, locate the IP:
- Point your web browser at that IP:
- Now, pick â€œAppliance Configurationâ€. You will be prompted to change the default password:
- On the next page, log in as root, and youâ€™ll be presented with the following:
- You will need to do the same password change for the vCO configuration page. This time log in with the default of vmware / vmware
- Start on the default page for the vCO Appliance:
- Start Orchestrator Client (The client is in Java, and will launch the Java Web Start bits):
- Log in with vcoadmin/vcoadmin
- Accept the SSL cert.
Long blog post is long. To put it in perspective however, it took me 8 minutes from start to operations not including the download. For more info on Orchestrator, check out my past posts here. You should also pre-order the vCO Book here. If you have any questions or comments, feel free to drop a line.