Move to DMZ script
Move to DMZ script
Remove the packaging stuff from the upstream branch. It should never have been there. Added in dd67085cd1555338c7d09809dcdf43e822819d17 by mistake
Updated script shebang line to use /usr/bin/env rather than direct interpreter reference.
Merge branch 'NewerFeature' of puppy19.dtg.cl.cam.ac.uk:infrastructure/husky-scripts into upstream
Delete me
Merge branch 'upstream' of puppy19.dtg.cl.cam.ac.uk:infrastructure/husky-scripts into upstream
Added documentation to the prepare_vm method
added missing fullstops to comments
Removed the default name of "" from new_vm, and the test for this value being "".

This makes sense. I now use argparse to ensure that the user enters a
name. Having the option to have a blank VM name, and creating a
template is a bad idea - we can then only do this once a day. Instead,
we should force the user to name their VM.
Merge branch 'remove_default_vm_name' of puppy19.dtg.cl.cam.ac.uk:infrastructure/husky-scripts into upstream
Run the vm-boot script after changing the hostname. This will fix
/etc/hosts
Merge branch 'upstream' of puppy19.dtg.cl.cam.ac.uk:infrastructure/husky-scripts into upstream
Reduced the value of {static,dynamic} minimum memory to be 256MiB.

Previously both max and min were set to 512MiB, because the freebie
version of XS doesn't support ballooning. Now we have the licensed
version, we can take RAM from machines if need be.

Now, normally this won't happen, and the machines will get all the RAM
that they have requested, and this patch won't make any difference to
the running on the VM.

However, there are 2 advantages of doing this
0) If we don't do it when we create the VM, it is hard to change these
settings when the VM is running. It involves shutting the VM down,
and fiddling in XenCentaur. We have been unable to do this for some VMs
we currently have.
1) By making VMs able to scale to very low (256MiB) amounts of memory,
it should be possible for us to run a complete (but reduced-performance)
service on single husky. Without this, we can only run on husky0, and
husky1. Given that we have hit plenty of issues where migrations, and
pools have not worked as expected, this may come in handy.
Merge branch 'auto-balloon-VMs' of puppy19.dtg.cl.cam.ac.uk:infrastructure/husky-scripts into upstream
Merge branch 'upstream'

Conflicts:
	debian/changelog
Changelog for v0.0.11
Merge branch 'packaging'
Merge branch 'master' of svr-acr31-code:husky/scripts
Redirected the output of the puppet configuration to /vat/log/puppet/installlog