We’ve been working on an Ubuntu RightImage for a while now and it just took longer than expected to iron out all the little wrinkles. But now it’s available as `RightImage Ubuntu7.04V1_14_2` with AMI ID ami-f3cc299a and location `rightscale_images/Ubuntu7.04_V1_14_2`.

This is our first Ubuntu public image so we hope we covered all bases, but we’re eager to hear whether everything works as expected. As always the script to create the image is also available.
To run the script, launch an Ubuntu image with working bundling code and run through the steps…

A little background on RightImages for those of you not familiar with what we’re doing: to configure servers we use a base image and install software at boot time using our server templates and RightScripts. This is way more modular and maintainable than baking entire servers into AMIs. Please see our blog post on the rationale behind this. As a result, we produce base images that are small yet have all the software utilities one just needs in EC2 already installed, from the Amazon EC2 tools to traceroute, curl, wget, etc. The second innovation we made with our images is that they are fully scripted and we publish the script. You can launch Amazon’s FC4 or FC6 image (well, for the Ubuntu RightImage you need to start with some Ubuntu instance), run our script, and out pops a clone of our RightImage. So if you want to see what we install or make some changes you can go right ahead.

Archived Comments

James
Hi, I just used your image, made some changes, installed some more packages and bundled it. Somehow after initializing the image I cant connect through SSH. Its weird because yours comes with SSH bundled and started. Why cant I connect to my image then? thanks in advance.

Thorsten
James, I’m pretty sure we tested rebundling the image, but I’ll double-check. Are you sure you have port 22 open and that you’re using the right SSH key? There is a boot script that installs the SSH key, so be sure you didn’t somehow disable that.

James
Hi. I keep stuck in the same issue. Well, I’ll describe my process: I ran your instance, made some package and gem installs, copied my pk and cert to /mnt, issued the following command:
ec2-bundle-vol -d /mnt -k /mnt/pk-2JSD7JYO2MTK3C3H5ATIM356KE4VYKOU.pem -c /mnt/cert-2JSD7JYO2MTK3C3H5ATIM356KE4VYKOU.pem -u 782731552053 -s 1536 -r i386

uploaded it to s3:
ec2-upload-bundle -b ubuntu_final -m /mnt/image.manifest.xml -a -s

registered it:
ec2-register ubuntu_final/image.manifest.xml

run it: ec2-run-instances ami-ccd633a5 -k test-keypair

… and after that the instance is online with their public and internal hostname. I cant ssh to it nor get a ping reply, so I checked with:
ec2-get-console-output i-809662e9

and I got some strange output: http://pastie.caboo.se/121164

Thank you

Thorsten
James, I now get he same error you do. Seems to have something to do with the new AMI tools released by Amazon. Sigh. We hope to have a fix released asap.