Timeline The Day 1 of the timeline starts when we have a fully operational web server in the machine room. Hence the Day -6 to Day 1 prep work for that state. [Name] identifies the person responsible for the task. Items done are prefixed with DONE: Day -6 to Day 1 =============== - DONE: Obtain machine from Galen [Eric, Scott] - DONE: Locate space in machine room [Mike] - DONE: Get Network connection [Mike] - DONE: Get IP address [Mike] - DONE: Configure Legato server for backups [Paul 5/11] - DONE: Move machine to machine room [Jacques, Scott] + Configure new web server [Scott] - DONE: Partition disks [Scott] - DONE: Flashed bios of the RAID controller [Scott] - DONE: Checked that motherboard BIOS is up to date [Scott] - DONE: Install Windows NT server 4. [Scott] - DONE: Install SP3 [Scott] - DONE: Install post-SP3 Hotfixes [Scott] - DONE: Install IIS 4.0 from the latest MS NT Option Pack with 'minimal' install [Scott] - DONE: Install Legato software for backups [Scott] - DONE: Download and install latest drivers for NIC-Intel EtherExpress [Scott] - DONE: Download and install latest drivers for ATI Mach 64 graphics adapter [Scott] - DONE: Install ftpd [Scott] - Order MKS toolkit [Eric] - Install MKS toolkit (includes Perl) [Scott] - Install swish-e [Jacques] - Install weblog [Jacques] + Configure a test machine in parallel with the new web server [Jacques] - DONE: Partition disks [Jacques] - DONE: Install Windows NT server 4. [Jacques] - DONE: Install SP3 [Jacques] - DONE: Install post-SP3 Hotfixes [Jacques] - DONE: Install IIS 4.0 from the latest MS NT Option Pack with 'minimal' install [Jacques] - DONE: Install ftpd [Jacques] - DONE: Install MKS toolkit (includes Perl) [Jacques] - Install swish-e [Jacques] - Install weblog [Jacques] - Port CGI-BIN scripts - webreport [Jacques] - DONE: mailform [Jacques] - Counter [Jacques] + Administrative procedures: - Setup account procedures - Decide who has system privileges - Document the procedure to give someone an account on this server. + Install CGI-BIN scripts: - webreport [Jacques] - mailform [Jacques] - Counter [Jacques] Day 1-7 ======= - DONE: Compile a list of all web directories that need to be moved along with their owners, e.g.: /extra/www/ucsc/pio owned by Jim Burns (x2495, burns@ua) [Library]. - A message telling web directory owners of the pending move, and requesting that they need to apply for an account. Needed by Day 1. - Notify all web directory owners on bob of the plan to move their web directories to the new server. Basically they need to request an account on the new server using a web form that CATS will create [CATS]. Day 8-14 ======== - As the requests come in, create the accounts, and web directories. Add the new directories to the indexing software configuration file [CATS]. Day 14 ====== - Create the remaining accounts if any. If a web directory owner didn't answer, assign the directory to the appropriate computing coordinator, and notify the computing coordinator. Add the new directories to the indexing software configuration file. [CATS] Day 15 ====== - Freeze the contents of the web directories (on bob) to be copied by changing their ownerships and permissions (except for files owned by "nobody" which are likely to be used by cgi-bin scripts) [Library]. - Copy the contents of the web directories into the appropriate directories on the new server [CATS]. - Message telling web authors the differences between bob and the new server. Also to tell them how to check for broken links and syntax errors. Day 16-30 ========= - During this period, web authors are advised to check their newly relocated pages on the new server for broken links and any syntax problems, and to verify that their cgi-bin scripts (if any) still work as expected [Web authors with help from CATS]. - Authors relying heavily on UNIX-based cgi-bin scripts may need to be moved to www2 instead. Day 31 ====== - Install the redirection mechanism for UCSC home pages (oncampus vs. public) on the new server [CATS]. - Install redirections on the new server for all the units that have moved [CATS]. - Generate new index [CATS]. - Generate new unit web page listing [CATS]. - Select some new name(s) for the web server on bob (e.g. www.lib.ucsc.edu?) [Library]. - Make the new cname entries for bob and modify www.ucsc.edu so that it now points to the new server [CATS]. Day 32 ====== - After a final backup on bob, remove the web directories on bob [Library]. After Day 32 ============ - Set up weekly indexing updates [CATS]. - Review log files for errors [CATS]. - Revise server usage summaries [CATS]. ======== Potential issues - Authors with web directories larger than the given quota. - When checking their links web authors MUST use relative links, so that the items are picked up on the current server without mentionning it by name (since the new server will be renamed 2 weeks later as www). - During the two week period when the pages are frozen, browsers will pick up the pages on bob. People will not be able to update the information on the pages during that time. - PIO will need to put a message on UCSC internal and external pages about the server change, and warn browsers that many of their bookmarks may now be incorrect. - I believe a quick transition (i.e. 2 weeks) is more effective than a slow transition (e.g. 6 months) because the links on www are too intertwined and the URL of many pages will be changing. An important issue that this timeline doesn't tackle is whether all units currently on bob should be moved to the new server or to www2. Once we have AFS running on the new server, the location of the files will matter less, since any units could be made available from both www (if desired) and www2. Future development ================== - Install AFS client on web server [Scott] - Install AFS client on test server [Jacques]