My First Attempt at an Ensemble Formula

Since every one else is doing it, I thought I’d play with more Ensemble tonight, but instead of firing something up I started working on a formula for summit, the tool we used to schedule UDS.

First Chris Johnston and Michael Hall started an etherpad with the instructions for installing summit (and we’re doing one for the LoCo directory too since we like biting off more than we can chew).

Here’s the first cut of the install script based on those instructions, then I went ahead and ran it in a VM to make sure it worked non-interactively. The documentation recommends that you have a plan before you start. Basically you are scripting an install on a brand new OS installation so you have to think of things you might normally take for granted, like remembering to install bzr or git before you pull something, heh:

When attempting to write a formula, it is beneficial to have a mental plan of what it takes to deploy the software. In our case, you should deploy drupal manually, understand where its configuration information is written, how the first node is deployed, and how further nodes are configured. With respect to this formula, this is the plan.

I did ok until I got to the python manage.py syncdb part of summit, which asked me a question, but not bad for the first shot. 

Of course, had I picked something packaged it wouldn’t be so complicated, my install script would just be an apt-get command but I think it’s useful to be able to just fire off an instance of summit right from trunk. 

The ability to just grab whatever you want right from trunk and fire off an instance is pretty powerful, I’m looking forward to seeing James Page’s etherpad-lite formula be ready so anyone can just fire one up for $your-favorite-conference.