The VCP5-IaaS documents

The VCP5-IaaS documents

Yesterday I started a series of blogs about the new VMware VCP5-IAAS certification. To get you started I wanted to provide you the resources needed and create a quick download page for all VMware PDF’s mentioned in the blueprint.

vmware vcloud director

In my first post, you can find a couple of blogs that are a great resouces for this study as well as the link to the training page for the vCloud Install and Configure training, so if you need those click here

I do want to share another resource with you of which I heard it is a a good training to get you started. I can’t tell by own experience, but from what I’ve seen from some other training material done by Trainsignal (and David Davis in special) on VMware topics, this must be great. And as said judging some of my twitter and facebook friends it is a great training. So I just wanted to point you to the Trainsignal vCloud Director Essential training.



The exam blueprint provided by the VMware education services is devided in 5 sections which on their turn are devided into sub sections. The 5 sections are:

  • Setion 1: The exam
  • Section 2: Intended Audiance
  • Section 3: Objectives covered in the VCPVCD510 Exam
  • Section 4: VCP-IaaS Paths and Course Requirement Options
  • Section 5: Additional Resources

Section 1, 2, 4 and 5 are informative sections which you should read. Make sure you know the information included in these sections before taking the exam.

Within section 3 you will find all Sections and objectives needed to be able to nail the VCP5-IaaS certificate. I’ll cover these in later posts, but when looking through the blueprint I noticed a lot of guides are named a couple of times thoughout the blueprint. I thought it would be great to have a source where all these guides are named once so you can download them all from 1 place. So here are the direct links to the guides:

Read More
Virtacore introduces vCloud Express

Virtacore introduces vCloud Express

Yesterday Virtacore introduced their vCloud Express public Cloud product. They’ve been working months on this and the final product looks very good.

They use a different type in approaching the Cloud industry, by using the full scope that is supplied through VMware vCloud Director 1.0+. VMware High Availability (HA), Distributed Resource Scheduler (DRS), vApps and vShield Edge are just a few of the VMware Features available….


If you want to try a different type of cloud please check out vCloud Express and let us know what you think, use the promo code “VCXBlog11” for a $50 credit which is equal two approx. months of service depending on your plan size.

Be sure to follow us on Twitter @Virtacore and our VMware friends @VMware and @vCloud for industry news and updates.

Source: Introducing vCloud Express by Virtacore

Read More
Part 4: Installing vShield manager and vCloud Director

Part 4: Installing vShield manager and vCloud Director

This will be the last of 4 parts. In Part 1, Part 2 and Part 3 we’ve installed all stuff needed to get the vCloud director up and running. That’s all except one…. vShield. So let’s get that up and running first:

As with the installation of the vyatta router, the vShield manager software comes as a ova file intended for a ESX environment. So we need to use the OVFtool again to get a format suitable for VMware workstation. Because i’m using a Windows 7 machine this will doen through the command prompt:

Make sure you’ll start a CMD with administrative rights and go to the which contains the ovftool. Once there execute the following line: ovftool.exe “path_to_the_OVF_file” “path_to_folder_for_vShield_files”


The files will be extracted and placed in the folder you’ve provided in the cmd line. Go to that folder\VSM and doubleclick on the vmx file


The Files will be imported into the workstation environment, creating a new VM. Go to the newly created VM and click Power on this VM (check if all devices are correct) 5

The VM will fire up and come to an hold at the following line: Localhost login: Type admin and press enter. Supply the password (the password is default)


At the manager> line enter enable and press enter. You’ll have to provide the password again (default) and at the manager# line enter setup and press enter. After this you’ll have to provide a couple of settings (IP Address, Subnet Mask, Default Gateway, Primairy DNS, Secondary DNS, DNS domain searc list) click Y to save the config.


exit out of the manager, and the installation of vShield is done. Let’s check if all is working well. Open a webbrowser and surf to log in with admin and the default password.


We should now add the vCenter server (add the administrator account and password) and click save


Your vCenter server will become visible and your done with the installation of vShield (I wil’l not be discussing the different settings of vShield in this post. Maybe in a later post ;-))

Installing vCloud Director

The last thing we need to install is the vCloud Director software which we’ll do on the already installed CentOS system.


Copy the vmware-cloud-director-1.0.1-356485.bin file to a folder in the CentOS VM (I copied it to my Desktop)


Open a terminal and make sure you’ve got root privilege. Navigate to the folder which contains the vmware-cloud-director-1.0.1-256485.bin file and execute the following line: chmod +x vmware-cloud-director-1.0.1-356485.bin


After you did the chmod, we’ll have to execute the bin file. This can be done by entering the following line ./vmware-cloud-director-1.0.1-256485.bin and press enter. When asked type y and press enter.


The installation of the vCloud Director will start and after a while asks if you would like to run the script now? Enter n and press enter


We now first need to create self signed certificates, in the terminal window navigate to /etc and type the following line:

/opt/vmware/cloud-director/jre/bin/keytool -keystore certificates.ks -storetype JCEKS -storepass password -genkey -keyalg RSA -alias http

answer the questions and answer yes after the is …. correct? then provide a Password (twice) and do the same process with the following line:

/opt/vmware/cloud-director/jre/bin/keytool -keystore certificates.ks -storetype JCEKS -storepass password -genkey -keyalg RSA -alias consoleproxy


Do an ls commando in the etc folder and check if certificates.ks is created.


After we’ve created the certificates.ks we can continue with the installation of the vCloud Director. Type the following:

/opt/vmware/cloud-director/bin/configure and press enter

Select the number that indicates the IP address of your internal network (1 in my case) and press enter


Press enter for the ip address for the remote console proxy


Enter the path to the keystore (/etc/certificates.ks) and enter the keystore password (this is the storepass setting which was password) and press enter


Enter the private key passwords and press enter press enter when asked about the syslog host name (or provide the FQDN/IP when you have one) and provide the IP address of the host (can be press enter for the default 1521 port, and xe for the databse service name. Provide your databse username and password and the installation will continue


when asked to start the vCloud Director now? enter y and press enter. In my case I needed to reboot the Vm to get the service up and running….


Open a browser and browse to https://IP-address/FQDN_of_the_vCloud_director_server the VMware Cloud Director setup will launch > click next at the welcome screen


Select Yes, I accept the terms in the license agreement and click next


Enter the license key which VMware provided with the trial download


Enter a Sytem name and installation ID (keep the default) and click Next


Check all settings and press Finish


Login the account just created


Click attach a vCenter


Provide the FQDN/IP address, Port Number, User name, and vCenter name and click Next


Provide the FQDN/IP address for the vShield manager (make sure that vShield is added to your DNS, as well as vCloud Director) add the username (admin) and password (default) and press Next, and then click Finish


Congratulations 😉 you’ve just created your first vCD Cell.

Be sure to look at these site for more information:


Duncan’s blog:

Chris Colotti’s blog:

Thanks for the visit! And all comments are welcome!

Read More

Part 3: Installing CentOS and the Oracle 10g Express database

To get the vCloud Director up and running you’ll need to use an oracle database. While not supported by VMware, the Oracle 10g Express database can be used to get vCloud up and running. Because we have to use the oracle database anyways, i decided to use it for my vCenter server as well.

There is a great post by Duncan Epping ( about what steps need to performed to get the vCloud Director installed within CentOS. Most of the steps done in this post come from this post. So let’s start with the installation of CentOS 5.5.

I already installed a router (see this post) and installed a AD/DNS environment. I will not cover the installation of the AD/DNS environment or the install of Windows Server. I also installed Windows Server 2008 R2 and vCenter. In vCenter I created a datacenter and added the ESXi hosts.

For the installation of the VMware vCloud Director we need a installation of CentOS 5.5 and Oracle 10g Express:

  1. The CentOS 5.5 install iso. Download here (be sure to download the full installation files. NOT the liveCD…)
  2. The Oracle 10g Express rpm. Download here

The following pdf files are step by step installation guides for installing the CentOS VM and oracle 10g Express

Step-by-Step installation of CentOS 5.5 in Workstation 7.1

Step-by-Step installation of the Oracle 10g Express database

When you’ve performed this steps, all systems are ready….. For vShield and vCloud Director installation.

See you at Part 4 😉

Read More
Part 2: Getting Vyatta Core Router up and running

Part 2: Getting Vyatta Core Router up and running

To create a datacenter environment, i decided to use Vyatta as a router between my home network and the vCloud “datacenter”.

To do this, first thing we need to do is to download the Vyatta software which can be done here.

Because I’ll be using Vyatta within a VMware workstation environment, I downloaded the ESX 4.1 virtual appliance. To get that up and running within workstation you must do the following steps:

  • Download VMware’s OVF tool here and install it on your PC.
  • Open a Command Prompt as an administrator (Start –> All Programs –> Accessoires –> Right click CMD and open as Administrator)
  • Go to the folder in which you’ve installed the OVF tool
  • Check the path to where the downloaded Vyatta appliance can be found (D:\vCloud installation\Vyatta in my case)
  • In the CMD promt type the following: ovftool.exe “D:\vCloud installation\Vyatta\vyatta-vmware-esx4_VC6.2-2011.02.09_i386.ovf” “D:\vCloud installation\Vyatta\” and press enter.
  • It should look like this:Vyatta
  • When this is done go to the folder in which you’ve just saved the new files and doubleclick the *.vmx file.
  • VMware workstation will start and show the following:
  • Vyatta1
  • Click on edit virtual machine settings and in the next screen select the Network adapter 2.
  • Vyatta2
  • Make sure this will use it’s own physical NIC. and click OK. You’ll be back in the workstation startscreen, click in Power in this virtual machine
  • Vyatta3
  • After booting the following screen will display:
  • Vyatta4
  • Login with the default name: vyatta and password: vyatta
  • Vyatta5
  • We will now get the router up and running for our homelab:
  • To do this we’ll need to be in the configure mode. So type configure and press enter.
  • Vyatta6
  • Notice how the command prompt changes to mark the move from operational mode
    (“:~$”) and configuration mode (“#”).
  • We’ll change the sytem host name for a more “vCloud” name….
  • At the command prompt type the following: set system host-name <your hostname> and press enter
  • After this type commit and press enter. Then type exit and press enter and log back in to vyatta it should look something like this:
  • Vyatta7
  • After this we must specify the system’s domain name. In my case this will be vdicloud.local
  • To set the domain name we must use the set system domain-name command. Enter set system domain-name <DOMAINNAME> and press enter and do a commit.
  • Vyatta8
  • After this we should set the IP address for the external network (192.168.0.x in my case) by using the set interfaces ethernet eth0 address command
  • followed by commit again. You can see what you’ve done using show interfaces ethernet eth0
  • Vyatta9
  • We’ll repeat this for our inside address (in my case
  • After this is done, do a show interfaces, and the outcome should look like this:
  • Vyatta10
  • To make sure the internal network can use the internet we’ll have to setup NAT. This can be achieved like this:
  • First we need to make sure the default gateway is set with the set system gateway-address command, and a commit:
  • Vyatta11
  • After this we have to make sure all trafic from the internal LAN will be routed through the eth0 interface.
  • We’ll do this by making a NAT rule. The command for this is set service nat rule 1 source address
  • the second command is set service nat rule 1 outbound-interface eth0
  • and the last set service nat rule 1 type masquerade and a commit
  • Vyatta12
  • A quick check (with a CentOS liveCD and a static IP address) shows the routing is going perfect:
  • Vyatta13
  • This should do for the next face of installing a vCloud homelab.

See you in part 3 😉

Read More
Part 1: VMware vCloud Director in my homelab

Part 1: VMware vCloud Director in my homelab

In this first part I want to show you the resources needed for installing a vCloud director homelab. There are a couple of things that are not supported by VMware. So installing it this way is not supported and you should not use in a production environment, this should be only installed i a homelab environment.

For installing i used the following websites:

Duncan Epping (@DuncanYB) post: Creating a vCD Lab on your Mac/Laptop

Chris Colottis’s (@CColotti) post: VMware-vCloud-in-a-box-for-your-home-lab

VMware vCloud director (@VMware): vCloud Director overview

VMware vCloud Installation and Configuration Guide: PDF

VMware vCloud Director Evaluator’s Guide: PDF

Hardware used:

In my homelab I’ll use the following hardware:

1 x Homebrew workstation Windows 7 64-bit installed with workstation 7.1 12 GB Memory and 3 Network cards

2 x Homebrew ESXi 4.1 servers with 8 GB RAM 4 Nics and a Intel Q6700 processor

1 x Homebrew ESXi 4.1 server with 16 GB RAM 4 Nics and a Intel Xeon 3440 processor

Software used:

VMware ESXi 4.1, VMware vCenter server 4.1 VMware vShield and VMware vCloud Director: download here

Microsoft Windows 2008 32-bit as a AD/DNS server: download a trial here

Microsoft Windows 2008 R2 64-bit for vCenter server: download a trial here

CentOS 5.5 DVD install: download here

Oracle 10g Express 32-bit for linux: download here

Vyatta Core Routing: download here

Installation plan:

I made a simple visio drawing of what my lab will look like after I installed my vCloud environment:


There are a couple of Pre-requisites of which I presume they are already in place, they are:

  • the windows machine with workstation 7.1
  • The 3 ESXi servers
  • A NAS/SAN (for a excellent Openfiler guide go to this blogpost made by Simon Seagrave @kiwi_si)
  • The Windows server 2008 (R2) AD/DNS installation

As said I presume they are already installed and as so, I will not handle those. There are plenty guide online for these installations.

My vCenter server will use the database server provided by the VMware software. I will do a seperate post on installing CentOS with the installation of the Oracle 10g Express database for the vCloud Director software.

I will devide all this into 4 parts:

  1. Part 1: VMware vCloud director in my homelab
  2. Part 2: Getting Vyatta Core Router up and running
  3. Part 3: Installing CEntOS and getting Oracle 10g Express
  4. Part 4: Installing vShield manager and vCloud Director

Hope to see you on Part 2 😉

Read More