Been slowly working on learning how to build, deploy and manage Eucalyptus clusters. I'm using Ubuntu 9.10 for all the installations since it provided the easiest installation option, which is right at booting from CD.
My first test-bed is a collection of 5 servers: 1 controller and 4 nodes. The controller is running on an Atom 330 2GB 1U server built by Supermicro. The nodes are all Atom D510 4GB 1U systems also built by Supermicro. None of the nodes support the "accelerated virtualization", but again this is for testing purposes. They do however afford me the 64bit architecture option for virtualized OSes (and let me at least squeeze in 4GB of ram on the Atoms). These Atom D510 systems also afford me the luxury of remotely installing them via IPMI 2.0. My goal is to try and come up with a reasonably small power footprint for running cloud-based services. Right now each Node consumes 31w idle, and 33-35w when really using the drive. They are on 80+ PSUs to achieve such a small footprint. Sadly the Controller isn't on 80+ (I ordered wrong chassis and didn't bother returning it) but still only uses around 39w idle.
After creating the Controller and setting the cloud's identification, installing the Nodes was similar and they auto-detected the Controller and have tied themselves in. Right now I do not have the Controller configured to use DHCP for address assignment of either the Nodes or the virtualized OSes that will be hosted, I've been manually assigning. I've also got to look into IPv6 IP assignment and management by the Controller. It might be that I have to create a secondary LAN for these machines, but I don't want the Controller to act as gateway.
As for management tools for the virtual OSes, I was looking at Elasticfox as a FireFox plugin, however 1.7 seems to have broken Eucalyptus compatibility, and I'll have to build my own copy of 1.6 from SVN/CVS (see http://ajmf.wordpress.com/2009/10/05/elasticfox-for-eucalyptus/ for more information regarding this).
Work, friends and a desire to try and sleep once in a while are dominating time right now, but I try and poke around on this once in a while. One of the struggles was working with Supermicro support on problems accessing the IPMI remotely and mounting CD ISOs. They got me an (as-of-this-post) unreleased IPMI firmware for my Atom mainboard (X7SPA-HF came with v1.29, they emailed me v1.30) which resolved the issue when using their Java based IPMIview client software, but not while using the web based interface. I also cannot manually set the IPv6 gateway on the IPMI interface via the webUI (and I'm pretty sure that being able to manually set the IPv6/mask is a hole/bug), so IPMI is only globally reachable over IPv4 unless I start running a DHCP/RA server and let IPMI autoconfigure an IPv6 address (tested, that worked).