Frigg - libcloud-based script to create a VPS and install Aegir in one hit

I've been playing with Libcloud out of interest, and as a method of learning its ins and outs, I've written a script called 'Frigg'.

Frigg is named after a Norse goddess (uh oh, here it comes..) and is designed to spin up a brand new server in the cloud, and then install Aegir on it.

All you have to is run 'python frigg' from a machine somewhere after configuring the frigg.ini file with the usual Aegir parameters (use '0.4-beta1' for version, for example) and your VPS provider and api key info, and you'll get the 'Welcome' one-time Login url e-mail for your new Aegir installation on your new server just a couple of minutes later. That's it!

You can get Frigg via github by running git clone git://github.com/mig5/frigg.git.

To run it, you'll need python, python-paramiko and libcloud. To get libcloud, I simply did a git clone git://github.com/apache/libcloud.git and ran python setup.py install . You can also use my fork at git://github.com/mig5/libcloud.git, which has someone's patch to allow the root user's password to be caught when using deploy_node (it normally only does so for create_node)

Currently the default provider in the frigg.ini is Rackspace. However, I have tried to abstract the provider away in the code, which means any VPS provider supported by libcloud should be supported, so long as that provider implementation supports the deploy_node method. I am not sure that they all do.

I am assuming the MySQL host is localhost (the default in Aegir 0.4-beta1) and I am not yet commenting out the bind-address directive in the mysql my.cnf. So it's probably not 'remote server' friendly if you want your remote web servers to talk back to the main server for database communication. I might add that later.

A random MySQL root user password is generated. It is printed to stdout on completion, and you'll be able to retrieve this from the /var/aegir/.drush/server_localhost.drushrc.php alias file.

You'll need an SSH private/public keypair in the .ssh directory of the user you're executing frigg as, because the public key will be copied up to the new VPS so that you can login without requiring a password.

Also, the code is completely hardcoded to deploy a Debian based system (a lot of apt-get etc). I won't apologise for that, too bad :)

It's just for fun at this stage and it needs some sanity checking etc of the inputs, but you're welcome to try it and improve on it if you like :)