Guys, I'm happy to announce that the devcloud-kvm is open for business :-) I just ran through the doc at https://cwiki.apache.org/confluence/display/CLOUDSTACK/devcloud-kvm and everything worked. I'll see if I can clean up my notes and perhaps have someone else go through them to find out where things aren't obvious, because I'm sure someone will want to roll an Ubuntu one.
The advanced deployment works (thanks to Prasanna for the help with marvin), and I was able to create/test VPCs as well in devcloud-kvm. There is also now a version of the normal Xen devcloud that will run under KVM hypervisor instead of VirtualBox. See notes below. *Some notes:* I created a small CentOS template to replace tinylinux for devcloud-kvm, because the one in devcloud is set up specifically with the xen pv modules, and I didn't have time to muck around with figuring out how to build a new ttylinux kernel with virtio. I got one to work with IDE, but that doesn't allow us to dynamically add volumes and we'll fail things like volume integration tests. So instead we use a minimal CentOS, download size is ~180M and I increased the RAM for the tiny offering from 100M to 128M. I also have a version of the Xen devcloud that runs on a linux host in KVM. This is required if you're running linux because you can't use both KVM and VirtualBox at the same time, which means you can't run devcloud and devcloud-kvm on the same machine unless you use this. It behaves similarly to the standard devcloud (it's the same image, just converted), and most of that wiki applies except for getting the VM installed. I've updated the devcloud wiki to reflect this. *xen devcloud changes:* * * No changes to the existing stuff that's already working, aside from being able to run it in KVM now. However, I did I create some modified marvin configs that can be used to deploy an advanced zone. If you have visited the wiki page you might have noticed the new documentation. They are based on my devcloud-kvm setup for advanced networking. I've tested the tools/devcloud/devcloud-advanced_internal-mgt.cfg config, which is meant for running everything in devcloud, but not the tools/devcloud/devcloud-advanced.cfg. The main difference between these is where the management server runs. It largely works the same as the advanced zone in devcloud-kvm, with the one caveat that the console proxy doesn't work on VirtualBox. This is due to the way VirtualBox NAT networking works; the host OS doesn't have access inside the NAT network, even though hosts in the NAT can get out. Virtualbox handles the NAT, not the OS like you'd expect. So because you get a url that points you to that NAT network when you try to launch console in the web UI (which is the 'public' in cloudstack), you cannot reach it from the host. If you need to connect though you can still connect directly to the devcloud's VNC ports, you just have to know which one the vm you want is on. You could also swap the physical networks/ips in the config, I've considered this and there are advantages to having it both ways, just depends on what you're developing and testing.
