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 (www.yellow-bricks.com) 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 😉

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 192.168.0.31/24 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 172.24.0.1/16)
  • 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 172.24.0.1/16
  • 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 😉

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:

vCloud

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 😉