Last weekend (on the 15th January) I delivered a talk on Aegir at DrupalDownUnder 2012. I tried to do something we've not done before in Aegir demos: demonstrate basic usage along with more advanced, automated use of Aegir.
Overall I was happy with my talk - I ran out of time, as I was a bit too ambitious, but I really wanted to show the advanced stuff without alienating the newbies.
I've recently been working on a project for a client that required Solr 3.4 (which we implemented using these packages for Ubuntu 10.04)
Additionally, in production we've implemented two solr servers in replication (one master, one slave).
Having never done this before, I followed the example in the solrconfig.xml that was commented out, as well as this documentation.
I've been having weird, inconsistent bugs occur when running Puppet especially on new systems (where it's more obvious).
Specifically: I've seen cases where a manifest Notifies the apt-get update Exec to refresh the apt database, and suddenly the next series of package installs have failed with 'could not find package'.
Drupal has a big following in Australia, but it's somewhat overlooked due to the size of the country and the fact that the focus is spread out over such a large area. On top of that, the remote nature of this part of the world sees us even combine events with other nations such as New Zealand and various Asian countries.
During a rather boring conference a few weeks back, I decided to convert my own infrastructure from 'standalone puppet' (that is, a set of standalone puppet manifests that were executed by a basic shell script on each server I managed) to the 'client -> server' or 'puppetmaster' model (whereby a central puppet daemon controls the manifests, and servers connect to it for updates as 'clients'.)
You can read more about the different models here.
I've recently been doing some very innovative work for the very clever gents at Code Enigma, where I've been working on some interesting projects:
1. an automated 'zero-touch' dev/stage/live deployment system for their enterprise Drupal applications (developers no longer need to ssh in to servers to do deployments)
2. automatic 'one-touch' provisioning and configuration of new hosting cloud services.
(More on the dev/stage/live zero-touch deployment soon :) )