The following are recommendations, rather than fixed requirements. However, our experience in developing this documentation indicated the following suggestions.

Front End

Use the following table for a system that will run one or more of:

• the cloud controller (clc)
• the cluster controller (cc)
• walrus (the S3-like storage service)
• the storage controller (sc)

Node(s)

The other system(s) are nodes, which will run:

• the node controller (nc)

These systems will actually run the instances. You will need one or more systems with:

After installing and booting the Cloud Controller, users of the cloud will need to retrieve their credentials. This can be done either through a web browser, or at the command line.

From a Web Browser

1. From your web browser (either remotely or on your Ubuntu server) access the following URL:

   https://<cloud-controller-ip-address>:8443/

   Important! You must use a secure connection, so make sure you use "https" not "http" in your URL. You will get a security certificate warning. You will have to add an exception to view the page. If you do not accept it you will not be able to view the Eucalyptus configuration page.

2. Use username 'admin' and password 'admin' for the first time login (you will be prompted to change your password).
3. Then follow the on-screen instructions to update the admin password and email address.

4. Once the first time configuration process is completed, click the 'credentials' tab located in the top-left portion of the screen.
   

5. Click the 'Download Credentials' button to get your certificates

6. Save them to ~/.euca

7. Unzip the downloaded zipfile into a safe location (~/.euca)

   unzip -d ~/.euca mycreds.zip

From a Command Line

1. Alternatively, if you are on the command line of the Cloud Controller, you can run:

   mkdir -p ~/.euca
   chmod 700 ~/.euca
   cd ~/.euca
   sudo euca_conf --get-credentials mycreds.zip
   unzip mycreds.zip
   ln -s ~/.euca/eucarc ~/.eucarc
   cd -

Extracting and Using Your Credentials

Now you will need to setup EC2 API and AMI tools on your server using X.509 certificates.

1. Install the required cloud user tools:

   sudo apt-get install euca2ools

2. To validate that everything is working correctly, get the local cluster availability details:

   . ~/.euca/eucarc
   euca-describe-availability-zones verbose
   AVAILABILITYZONE   myowncloud                 192.168.1.1
   AVAILABILITYZONE   |- vm types                free / max   cpu   ram  disk
   AVAILABILITYZONE   |- m1.small                0004 / 0004   1    192     2
   AVAILABILITYZONE   |- c1.medium               0004 / 0004   1    256     5
   AVAILABILITYZONE   |- m1.large                0002 / 0002   2    512    10
   AVAILABILITYZONE   |- m1.xlarge               0002 / 0002   2   1024    20
   AVAILABILITYZONE   |- c1.xlarge               0001 / 0001   4   2048    20

Using UEC consists of creating and registering images with the Cloud Controller.

This page describes the process for Ubuntu 10.04 LTS.

There is more than one way to obtain a virtual image:

• Download an image from the network, bundle and upload it
• Create a custom image using VMBuilder
• Use the Image store to download and install and image

Here we will describe the process of downloading one of the daily builds that are built and published automatically. The process is similar for Official Released Images

1. Download the UEC image for the architecture you want. You can do it from your browser or from the command line:

   TIMESTAMP=$(date +%Y%m%d%H%M%S)
   RELEASE=lucid
   ARCH=amd64    # Or this might be i386
   [ $ARCH = "amd64" ] && IARCH=x86_64 || IARCH=i386
   UEC_IMG=$RELEASE-server-uec-$ARCH
   URL=http://uec-images.ubuntu.com/$RELEASE/current/
   [ ! -e $UEC_IMG.tar.gz ] &&  wget $URL/$UEC_IMG.tar.gz
   uec-publish-tarball $UEC_IMG.tar.gz $RELEASE-$TIMESTAMP

2. Now, your kernel and image will have been uploaded into Eucalyptus and should be ready to run. To confirm, run the following command:

   euca-describe-images
   EMI=$(euca-describe-images | grep emi- | head -n1 | awk '{print $2}')

   You should see a registered kernel and image and they should be marked as 'available'.

There are multiple ways to instantiate an image in UEC:

• Use the command line
• Use one of the UEC compatible management tools such as Landscape

• Use the ElasticFox extension to Firefox

Here we will describe the process from the command line:

1. Before running an instance of your image, you should first create a keypair (ssh key) that you can use to log into your instance as root, once it boots. The key is stored, so you will only have to do this once. Run the following command:

   if [ ! -e ~/.euca/mykey.priv ]; then
       mkdir -p -m 700 ~/.euca
       touch ~/.euca/mykey.priv
       chmod 0600 ~/.euca/mykey.priv
       euca-add-keypair mykey > ~/.euca/mykey.priv
   fi

   Note: You can call your key whatever you like (in this example, the key is called 'mykey'), but remember what it is called. If you forget, you can always run euca-describe-keypairs to get a list of created keys stored in the system.

2. You must make sure to source ~/.euca/eucarc before you run any of the eucatools. It is probably best to add this to the bottom of your .bashrc script.
3. You must also allow access to port 22 in your instances:

   euca-authorize default -P tcp -p 22 -s 0.0.0.0/0

4. Next, you can create instances of your registered image:

   euca-run-instances $EMI -k mykey -t m1.small

   Note: If you receive an error regarding image_id, you may find it by viewing Images page or click "How to Run" on the Store page to see the sample command.

5. The first time you run an instance, the system will be setting up caches for the image from which it will be created. This can often take some time the first time an instance is run given that VM images are usually quite large. To monitor the state of your instance, run:

   watch -n5 euca-describe-instances

   In the output, you should see information about the instance, including its state. While first-time caching is being performed, the instance's state will be 'pending'.
6. When the instance is fully started, the above state will become 'running'. Look at the IP address assigned to your instance in the output, then connect to it:

   IPADDR=$(euca-describe-instances | grep $EMI | grep running | tail -n1 | awk '{print $4}')
   ssh -i ~/.euca/mykey.priv ubuntu@$IPADDR

7. And when you are done with this instance, exit your SSH connection, then terminate your instance:

   INSTANCEID=$(euca-describe-instances | grep $EMI | grep running | tail -n1 | awk '{print $2}')
   euca-terminate-instances $INSTANCEID