Installation & Configuration 11

2.2.3 Install CC”s ssh public key to NC

• On the Node Controller, temporarily set a password for the “euca-
lyptus” user:

uecadmin@server2:˜$sudo passwd eucalyptus

• On the Cluster Controller:

uecadmin@server2:˜$sudo −u eucalyptus ssh−copy−id −i

˜eucalyptus/.ssh/id_rsa.pub [email protected]

• You can now remove the password of the “eucalyptus” account on the
Node:

uecadmin@server2:˜$sudo passwd −d eucalyptus

2.3 Client1
The purpose of Client1 machine is to interact with the cloud setup, for
bundling and registering new Eucalyptus Machine Images (EMI)

2.3.1 Installation
• Boot the Desktop off the Ubuntu Desktop 10.04 CD and install. The
Desktop will be on the enterprise network and will obtain an IP ad-
dress through DHCP.
• Install KVM to help us install images on KVM platform and bundle
them:

uecadmin@client1:˜$apt−get install qemu−kvm

2.3.2 Post Install Configuration

• Install euca2ools to be able to manage the cloud from it:

uecadmin@client1:˜$sudo apt−get install euca2ools

Eucalyptus Beginner’s Guide: UEC Edition

12 Installation & Configuration

• Login to the web interface of CLC by using the following link

https://192.168.10.121:8443. The default username is “admin” and
the default password is “admin”.
• Note that the installation of UEC installs a self signed certificate for
the web server. The browser will warn you about the certificate not
having been signed by a trusted certifying authority. You can autho-
rize the browser to access the server with the self signed certificate.
Instruction on how to install a valid certificate signed by a trusted
certifying authority is beyond the scope of this guide.
• When you login for the first time, the web interface prompts you to
change the password and provide the email ID of the admin. Af-
ter completing this mandatory step, download the credentials archive
from https://192.168.10.121:8443/#credentials and save it in the
˜/.euca directory.
• Extract the credentials archive:

$ cd .euca
$ unzip mycreds.zip

• Source eucarc script to make sure that the environmental variables

used by euca2ools are set properly.
• To verify that euca2ools are able to communicate with the UEC, try
fetching the local cluster availability details:

$ . ˜/.euca/eucarc
$ euca−describe−availability−zones verbose

You should see something like the following if it works properly:

$ euca−describe−availability−zones verbose
AVAILABILITYZONE myueccluster 192.168.10.121
AVAILABILITYZONE |− vm types free / max cpu ram disk
AVAILABILITYZONE |− m1.small 0016 / 0016 1 128 2
AVAILABILITYZONE |− c1.medium 0014 / 0014 1 256 5
AVAILABILITYZONE |− m1.large 0007 / 0007 2 512 10
AVAILABILITYZONE |− m1.xlarge 0003 / 0003 2 1024 20
AVAILABILITYZONE |− c1.xlarge 0001 / 0001 4 2048 20

• If you see the free/max VCPUs as 0 in the above list, it means the
node did not get registered automatically. Please use the following
on Server1 and approve when prompted to add 192.168.20.2 as the
Node Controller:

Eucalyptus Beginner’s Guide: UEC Edition

Installation & Configuration 13

uecadmin@client1:˜$sudo euca_conf −−discover−nodes

Eucalyptus Beginner’s Guide: UEC Edition

Chapter 3

Web interface

Ubuntu Enterprise Cloud provides a minimal web interface to manage user

credentials, manage images, administer user accounts, etc.
In our sample setup, the web interface is accessible at:

https://192.168.10.121:8443/

You have already finished setting up the password for the admin user of
the web interface while working on Desktop1 in the chapter “Installation
& Configuration”.
A user trying to access the interface for the first time, will need to sign up
and would be able to use the interface after the account is approved by the
administrator. The approval of the account by the administrator results in
an email to the user.

3.1 Using the Web Interface

After logging into the web interface, you will see seven tabs as given below:

1. Credentials
2. Images
3. Store
4. Users
5. Configuration
Web interface 15

6. Services
7. Extras

3.2 Credentials

Figure 3.1: Web UI Tabs

You can change your account password, download the credentials (to be
used while bringing up instances etc.) and view the query interface creden-
tials (to be used with tools like euca2ools to query CC for information like
getting the list of images, instances etc.) here. Later chapters have more
detailed discussion about use of these credentials.

3.3 Images
You can see here a list of images that have been uploaded to the CLC. Each
entry contains information about the image such as its ID, meta information
like the Ids of associated kernel and ramdisk images etc. This information
comes in handy when you try to bring up instances using these images.
This is mostly a read-only listing, except that you can disable/enable each
of the images.

3.4 Store
The store tab lists new images available on the UEC image store of Canon-
ical. These are provided by Canonical and third-party providers such as
M/Gateway. You can install any of these images. Installation here refers
to the task of downloading and making it available for use on the local in-
stallation of UEC. After installation, the image should now show up under
the Images tab along with its kernel and ramdisk images.

3.5 Users
As an administrator, you can create as well as view and manage user ac-
counts here including enabling/disabling accounts and changing the pass-
words.

Eucalyptus Beginner’s Guide: UEC Edition

16 Web interface

Figure 3.2: Image Store

3.6 Configuration
You can view and manage information related to various components of
your UEC setup, such as CLC, CC, Walrus etc. You can also specify the
resource limits for different VM types such as m1.small, c1.medium etc.
More on this the chapter on “Instance management”

3.7 Services
A few pieces of commercial information about services from Canonical and
their partners for UEC.

3.8 Extras
You can find a list of Eucalyptus-certified Images and Eucalyptus-
compatible Tools like euca2ools.

Eucalyptus Beginner’s Guide: UEC Edition

Chapter 4

Image management

4.1 Eucalyptus Machine Image (EMI)

A Eucalyptus Machine Image (EMI) is a combination of a virtual disk im-
age(s), kernel and ramdisk images as well as an xml file containing metadata
about the image. These images reside on WS3 and are used as templates
for creating instances on UEC. Each Linux EMI is a combination of the
following:

• An XML file with a name like “jaunty.img.manifest.xml” with infor-

mation about one or more hard disk images, a kernel image and a
ramdisk image (id – emi-65440E7E)
• An XML file with a name like “vmlinuz-2.6.28-11-
server.manifest.xml” with information about the corresponding
kernel image (id – eki-39FC1244)
• An XML file with a name like “initrd.img-2.6.28-11-
server.manifest.xml” with information about the corresponding
ramdisk image (id – eri-71ED1322)

Each of these images has its own ID that can be used while running the
instances. More on this in the chapter on “Managing Instances”
From the web interface of Eucalyptus, you can view a list of EMIs in the
“Store” tab of the web UI. These are the EMIs listed from Canonical or
partners. You can choose to download and install any of these images
directly from Canonical’s site.
Since most enterprise/individual users of Eucalyptus have a need for bring-
ing up instances based on custom images, image management plays a key
18 Image management

role in Eucalyptus administration. Such images could be based on a pre-

ferred version/variant of a preferred OS distribution with a set of required
applications pre-installed.
Bundling an EMI is a multi-step process involving the following:

• creating a virtual disk image

• installing the OS
• installing required applications
• making the OS ready to run under UEC
• registering the images with UEC
• testing the image etc.

Bundling process differs between Linux and Windows images and we will
discuss the process in both cases in some detail below.

4.2 Bundling Linux Image

We will use Client1 for the purpose of working on creation of the image.
Please note that we had installed KVM on Client1.

4.2.1 Creating a new disk Image

This will represent the main HDD of the virtual machine, so make sure to
give it as much space as you will need. Since we are building a KVM image,
we can use a qcow2 format for disk images. Qcow2 is an expandable image
format, so it will only occupy as much storage space as is actually filled by
the data within the image:

uecadmin@client1:˜$ kvm−img create −f qcow2 image.img 5G

4.2.2 OS Installation
Download the iso file of the Linux distribution you want installed in the
image. The example below refers to creating a Jaunty Jackalope 64-bit
server image:

uecadmin@client1:˜$ wget
http://releases.ubuntu.com/karmic/ubuntu−9.04−server−amd64.iso

Eucalyptus Beginner’s Guide: UEC Edition

Image management 19

And start the installation process:

uecadmin@client1:˜$ sudo kvm −m 256 −cdrom ubuntu−9.04−server−amd64.iso

−drive file=image.img,if=scsi,index=0 −boot d −net nic −net user
−nographic −vnc :0

If your installation process requires more than 256MB of RAM change the
-m option, and if you need more processors available, you can use the “-c”
option.
The command above will boot a new KVM instance, with the disk image
you’ve created as the primary HDD and the iso as the first bootable device.
Also the “-nographic” option will not display any graphical output. You
can connect to the instance through VNC (use display number :0) and finish
the installation. For example:

vncviewer A.B.C.D :0, where A.B.C.D is the IP address of the Client1.

After finishing the installation, relaunch the VM by executing the following

command:

uecadmin@client1:˜$ sudo kvm −m 256 −drive

file=image.img,if=scsi,index=0,boot=on −boot c −net nic −net user
−nographic −vnc :0

At this point you can add all the packages you want to have installed,
update the installation, add users and any settings that need to be present
in your new UEC instances.

$ sudo apt−get update

$ sudo apt−get upgrade
$ sudo apt−get install mediawiki

4.2.3 Integrating with Eucalyptus

An instance running under Eucalyptus needs to know what IP it has
and also, it needs to have the public key of the user allowed to do a
passwordless access through SSH. This is accomplished by using a rest-
ful interface provided by the cloud. The interface is available under this
URL: http://169.254.169.254/latest/meta-data and is accessible from
within the instance.
Eucalyptus node controller is set up to prevent automatic key injection if
the system is in MANAGED or MANAGED-NOVLAN mode. Instead, it

Eucalyptus Beginner’s Guide: UEC Edition

20 Image management

is assumed that the instance will use the above metadata service to retrieve
the public keys when running in these modes. You will need to facilitate
this by installing curl and adding a script that will run on each boot.
Install curl on the VM:

$ sudo apt−get install curl

Now add the following lines to /etc/rc.local of the image:

depmod −a
modprobe acpiphp
# simple attempt to get the user ssh key using the meta−data service
# assuming ?user? is the username of an account that has been created
mkdir −p /home/user/.ssh
echo >> /home/user/.ssh/authorized_keys
curl −m 10 −s
http://169.254.169.254/latest/meta−data/public−keys/0/openssh−key |
grep 'ssh−rsa' >> \
/home/user/.ssh/authorized_keys
echo ”AUTHORIZED_KEYS:”
echo ”∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗”
cat /home/user/.ssh/authorized_keys
echo ”∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗”

Add the above lines before the “exit 0” in /etc/rc.local

Also remove the network persistent rules from /etc/udev/rules.d, so that
the instance always comes up with eth0 as the interface name as expected
by Eucalyptus:

$ sudo rm −rf /etc/udev/rules.d/70−persistent−net.rules

This completes the process of customizing the OS installed as a reference

image.

4.2.4 Registering with Eucalyptus

The last step is to upload the images to Eucalyptus. The files that need
to be uploaded for the above sample setup are: vmlinuz-2.6.28-11-server,
initrd.img-2.6.28-11-server, image.img.
Copy the kernel and the initrd image from the VM image to some place
outside. These will be used later for creating and uploading a complete
virtual image to Eucalyptus:

$ scp /boot/initrd.img−2.6.28−11−server [email protected]:

$ scp /boot/vmlinuz−2.6.28−11−server [email protected]:

Eucalyptus Beginner’s Guide: UEC Edition