Subject: Your splice.org.uk virtual machine is ready!

Dear $user,

I am delighted to inform you that your splice.org.uk virtual machine is now
available for use.

I'll tell you the details to allow you to connect to it in just a moment, but
meanwhile, please read the following highly important blather:

- Reminder of takedown policy: ""
  I have mobile phone numbers for you all now, so just let me know if yours
  changes in future.

- Shared VM: This will be called rope.splice.org.uk, and we should have it
  ready for general use within seven days or so. Services shortlisted for it
  so far, in order of priority, are: spam scanning of incoming email, DNS
  (bytemark supply this, so you'll just need to edit files on rope to set
  records on their servers - details will be on the wiki), jabber, iodine
  (packeds over DNS), a VPN, SSH on port 443, ... (only the first two are
  likely to be up within 7 days, the rest as+when, depending on demand)

- Once the shared VM is up, I will fix up a wiki on it which will contain all
  the technical information about our setup. Meanwhile, if you want to know
  something, drop me/Michael an email or find us on IRC (#masterplan on OxIRC)

- Monitoring: I will be texted by Bytemark if the base machine goes down. As
  regards VM/service level monitoring, michael and I will cook something up
  at a (not too) later date.

- Xen-shell: thanks to the magic of Xen-shell, you can reboot, connect to the
  console of, and even reimage your VM without my intervention. This is also
  the place to set reverse DNS for your IPs and check your bandwidth usage.
  To connect to xen-shell, you should ssh to $username.console.splice.org.uk
  as user $username, using the private key attached for authentication.
  The ssh key fingerprints of the machine running xen-shell, which you should
  check when you first connect, are:
    $tape_fingerprints

Your machine's primary IP address is: $ip

You also have the next three IPs after that one, making four in all - please
bear this in mind when configuring services (which tend to listen on all IPs
unless you tell 'em not to) and especially when setting up your firewall (you
could do worse than start here: 
http://www.larted.org.uk/~dom/computing/code/iptfirewall)

The SSH key fingerprints of your machine (please check 'em on first connect)
are:
    $machine_fingerprints

You can log in as root with password: $root_password

Please change the root password at once.

Finally, huge thanks to Michael for his assistance to me during setup - without
which, things would have taken considerably longer!

Cheers,
David