blue.unix Cluster

Historical Archive: Migration Timetable

[Nov 23, 2009 14:09] Web access to Microsoft Live@edu accounts now works.

This document has been retained for historical reasons. It contains the timetable for UVa's move from single, stand-alone UNIX machines to a cluster of computers managed by the Network Appliance.

The following schedule was in place when ITC was moving from a computing environment with multiple RS/6000s to a clustered system in which the individual nodes were not generally used for login.

  • March 15, 1998: The CLAS RS/6000s faraday, fermi and darwin were disabled.
  • May 19, 1998: Watt accounts created on cluster, home directories copied to the Network Appliance and mailboxes copied to unix.mail.
  • July 14, 1998: Poe accounts created on cluster, home directories copied to the Network Appliance and mailboxes copied to unix.mail.
  • October 18, 1998: Palladio, Hobbes and Curry accounts created on cluster, home directories copied to the Network Appliance and mailboxes copied to unix.mail.
  • October 21, 1998: The SEAS RS/6000s watt, kelvin and fulton were disabled.
  • November 4, 1998: Poe was disabled.
  • November 29, 1998: Avery accounts created on cluster, home directories copied to the Network Appliance and mailboxes copied to unix.mail.
  • February 23, 1999: Hobbes and Palladio will be disabled. Curry will become a Web server only.
  • January 28, 1999: Assess feedback from Avery users on cluster.
  • March 30, 1999: Avery to become a Web server only.

© 2009 by the Rector and Visitors of the University of Virginia.

The information contained on the University of Virginia’s Department of Information Technology and Communication (ITC) website is provided as a public service with the understanding that ITC makes no representations or warranties, either expressed or implied, concerning the accuracy, completeness, reliability or suitability of the information, including warrantees of title, non-infringement of copyright or patent rights of others. These pages are expected to represent the University of Virginia community and the State of Virginia in a professional manner in accordance with the University of Virginia’s Computing Policies.