From Tardis
Revision as of 17:35, 30 June 2008 by Seth (talk | contribs)
Jump to: navigation, search

The Tardis Project rack will be moving from it's current home in the JCMB to a temporary new home in Forrest Hill on Wednesday 2nd July. This will obviously entail some downtime, and we're using the opportunities to make some changes to our setup. We expect to be shutting down the rack on the evening of Tuesday July 1st, and do not expect to be running again until some time on Thursday July 3rd at the earliest

Machine changes

Shell Host (Gallifrey), our main shell host ( is being decommissioned, to be replaced by Vortis (, a virtual host on a much faster machine (WOTAN). Vortis is currently accessible via the alias, but after the move, will be changed to point to this machine. This will involve changing the ssh host-key, so expect warnings when you try to connect for the first time. We believe we've cloned the required parts of the software setup from Gallifrey onto Vortis, but if you find any packages you need are not installed then please contact Tardis support.

Mail Host (Mccoy), our mail host, is also being decommissioned and replaced by a virtual host, The mail setup from mccoy has been replicated as closely as possible on the new host, bar an upgrade to Debian Etch, and the new host is already handling our incoming mail.

During the downtime, any incoming mail will be queued offsite and delivered when we are back up.

POP3 Users

If you have configured your mail client to use the correct host aliases ( instead of explicitly specifying Mccoy then you shouldn't require any configuration changes for the new setup.

IMAP Users

Similarly to POP3, please ensure you have specified the correct host alias ( in your mail client configuration. We have switched from Courier to Dovecot to handle our IMAP service - this may mean there will be changes in your visible folder layout and any client-side mail filtering rules may need updated.

Web Server (Davros), our user webserver is being decommissioned, and user web pages will now be served by Mara. This change should not be user visible.

Database Server (Peri), our MySQL and PostgreSQL server is being decommissioned and replaced by a virtual host Again, this change should not be user visible if you have used the host alias when specifying your database connections. If your database connections point explicitly at Peri, they will need to be changed.

Questions for the admins...

  • Are we going to make the old host names aliases for the new ones, or drop them altogether to catch any misconfigurations?