%archive_title% | VDICloud

Part 4: Installing vShield manager and vCloud Director

by Arjan | Mar 22, 2011 | vCloud, 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)

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 https://172.24.0.14 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 127.0.0.1) 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:

VMware: http://www.vmware.com/solutions/cloud-computing/private-cloud/products.html

Duncan’s blog: http://www.yellow-bricks.com

Chris Colotti’s blog: http://www.chriscolotti.us

Thanks for the visit! And all comments are welcome!

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

by Arjan | Mar 20, 2011 | vCloud, vCloud Director

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:

The CentOS 5.5 install iso. Download here (be sure to download the full installation files. NOT the liveCD…)
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

by Arjan | Mar 18, 2011 | vCloud, vCloud Director

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:
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:
Click on edit virtual machine settings and in the next screen select the Network adapter 2.
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
After booting the following screen will display:
Login with the default name: vyatta and password: vyatta
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.
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:
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.
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
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:
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:
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
A quick check (with a CentOS liveCD and a static IP address) shows the routing is going perfect:
This should do for the next face of installing a vCloud homelab.