It was causing 500 internal server errors because after
sanitization it would be set to null but a valid value would be
needed for a couple of actions on the website, like assigning
students to programs and assigning students to courses.

Truncating a hash function is kind of terrible, but this gives us a
unique 30 character string and should avoid conflicts.

! should be understood by django to mean "no password set".  It's handled
better in newer versions, but even in 1.4 it doesn't cause the "login
hangs" errors on stage like '' does.

This setting gets propogated to the launch configuration and is currently
causing unexpected behaviour.

Sometimes we get an instance id back from the creation call but then
get an exception saying the ID was not found when we do a get_all_instances.

Set params on BlockDeviceType instead of BlockDeviceMapping.

Use SSD backed EBS instead of standard.
Delete the volume upon abbey termination.

Only updating python-mysql if we aren't on jenkins

At 30 minutes we still hit it sometimes when building from a bare ubuntu box.

Defaulting it to hammer for now.