Install A Private Cloud In One HourJohnmwillis.com@botchagalupe

Build a Private Cloud

Ubuntu Enterprise Cloud (UEC) is a private cloud that embeds Eucalyptus cloud on Ubuntu server. Thecurrent release of UEC runs on Ubuntu 9.04 Server running Eucalyptus 1.5. There is a latter version of Eucalyptus (i.e., 1.5.2); however, I didn't try that for this blog post. In this blog example I installed allof the UEC cloud components on a single system. Typically you would not want to do this; however,this works well as a demo system.

Quick UEC Overview

UEC is made up of three components: Cloud Controller (eucalyptus-cloud), Cluster Controller (eucalyptus-cc), and one or more Node Controllers (eucalyptus-nc). The Cloud Controller is the Web-services interface and the WEBUI server. The Cloud Controller also provides resource scheduling andS3 and EBS computable storage interfaces. A cluster in UEC is synonymous with an availability zonein AWS. In this release of UEC the Cluster Controller has to run on the same machine as the CloudController. The Cluster Controller provides network control for the defined cluster and managesresources within the cluster (i.e., resources on the node). The Cloud Controller and the Cluster Controller are sometimes referred to as the Front End. Typically the Node Controller runs on a separate box from the Front End box. In a production environment there will be multiple Node Controllersmaking up a larger cluster (i.e., your cloud). Each Node Controller runs as a KVM hypervisor and allthe Node Controllers in the cluster make up the cloud environment. In the current release, runningmultiple clusters is really not supported. In future releases of UEC, you will be able to run multipleclusters in one environment. Each cluster acts like an availability zone in the UEC environment. As Inoted earlier, in this blog example, I am putting everything on the same box (my laptop). I will pointout areas where the configuration would be different in a normal installation of UEC. The followingdiagram shows an example of an UEC environment.

The following list are the steps I followed to install a UEC environment: .1)Download

Ubuntu 9.04 Server (the latest version):

1.http://www.ubuntu.com/getubuntu/download-server 2)Create an ISO image (I created a CD) 3)Install the ISO1.I took all the defaults during the install4)Install some pre-reqs for UEC1.sudo apt-get install openssh2.sudo apt-get install unzip3.sudo apt-get install ssh4.sudo apt-get install bridge-utils5.sudo apt get install libopenssl-ruby curl ruby5)Install the Cloud Manager (Front End)1.sudo apt-get install eucalyptus-cloud (Cloud Manager)2.sudo apt-get install eucalyptus-cc (Cluster Controller)6)Create a cloud cluster 1.euca-conf -addcluster <clustername> localhost7)Verify the Front End instal1.https://<ip_address_of_the_FE>:84432.Default usr/pswd = admin/admin3.You will be promoted to change the default admin password4.You will be promoted to add an email account5.In the configuration tab of the WEBUI you should change the localtion of Walrus froman IP address to "localhost". Walrus is the S3 emulation component.6.Note: Sometimes I would have to invoke the first-time-in dialog a few times to get it towork. If at first you don't succeed .8)All Node Controllers run as KVM hypervisors and must have a virtualization extension (Intel-VT or AMD-V) chip.9)Configure a bridge on the Node Controller 1.In this example, this is the same machine as the Front End1.sudo /etc/init.d/networking stop2.vi /etc/network/interfaces -- as follows:

# This file describes the network interfaces available on your system# and how to activate them. For more information, see interfaces(5).# The loopback network interfaceauto loiface lo inet loopback # The primary network interfaceauto eth0iface eth0 inet manualauto br0iface br0 inet dhcp bridge_ports eth03.Note: bridge_ports eth0 (there should be a tab on this line)4.sudo /etc/init.d/networking start5.Note: This would only be done on the NC if the NC was on a separate machine.10)Install Node Controller 1.sudo apt-get install eucalyptus-nc11)Configure /etc/eucalyptus/eucalyptus.conf on the Node Controller 1.Configure /etc/eucalyptus/eucalyptus.conf on the Node Controller 1.VNET_INTERFACE=br02.VNET_BRIDGE=br03.Note: When the Node Controller is on a separate box from the Front End theVNET_INTERFACE would be left as the default (VNET_INTERFACE=eth0). TheFront End interface definitions do not have to be changed..4.Restart the Node Controller 5.sudo service eucalyptus-nc restart##### there are the options for the network ##### VNET_INTERFACE specifies the local physical ethernet interface that# eucalyptus should use to manage the VM network. On the front-end,# this should be set to the device that is attached to the same# ethernet network as your nodes. On the nodes, this should be set to# either the name of the bridge that has been set up by Xen (xenbr0,# eth0, etc), or the physical ethernet device that is attached to the# xen bridge (peth0, peth1, etc), depending on your xen configuration.VNET_INTERFACE="br0"