Thursday, October 28, 2010

Setup private cloud computing on Cent OS Eucalyptus 2.0

Eucalyptus is software that implements scalable IaaS-style private and
hybrid clouds. The Eucalyptus architecture is highly modular with
internal components consisting of Web services, which make them easy to
replace and expand. Eucalyptus' flexibility enables it to export a
variety of APIs towards users via client tools. Currently Eucalyptus
implements the Amazon Web Service (AWS) API, which allows
interoperability with existing AWS-compatible services and tools. This
also allows Eucalyptus users to group resources drawn both from an
internal private cloud and external public clouds to form a hybrid
cloud.

At this point you should be ready to go through the first-time
configuration.

Point your browser to,
https://front-end-ip:8443
Since Eucalyptus is using a self-signed certificate, your browser
is likely to prompt you to accept the certificate. On some machines
it may take few minutes after the starting of the Cloud Controller
for the URL to be responsive the first time you run Eucalyptus. You
will be prompted for a user and password both of which are set to
admin initially.
Upon logging in the first time you will be asked to

change the admin password,

set the admin's email address, and

confirm the IP of the Cloud Controller host.

#mkdir $HOME/.euca

#unzip euca2-admin-x509.zip -d $HOME/.euca

#. $HOME/.euca/eucarc

Adding Images

To enable a VM image as an executable entity, a user/admin must add a
root disk image, a kernel/ramdisk pair (ramdisk may be optional) to
Walrus and register the uploaded data with Eucalyptus. Each is added to
Walrus and registered with Eucalyptus separately, using three EC2
commands. The following example uses the test image that we provide.
Unpack it to any directory:
#wget http://open.eucalyptus.com/sites/all/modules/pubdlcnt/pubdlcnt.php?file=http://eucalyptussoftware.com/downloads/releases/euca2ools-1.2-centos-i386.tar.gz&nid=3088
#cd euca-centos-5.3-i386

Next, add the root filesystem image to Walrus:
#euca-bundle-image -i
#euca-upload-bundle -b -m /tmp/.manifest.xml
#euca-register /.manifest.xml
Our test kernel does not require a ramdisk to boot. If the
administrator would like to upload/register a kernel/ramdisk pair, the
procedure is similar to the above:
#euca-bundle-image -i --ramdisk true
#euca-upload-bundle -b -m /tmp/.manifest.xml
#euca-register /.manifest.xml