11. GENERAL ARCHITECTURE

11.1. Implement full redundancy and failover for authentication, database, and web services.
- Snavely completed tuning and testing on the new Linux-based Oracle server, developed a transition plan for activating a near-real-time Oracle replication setup, and activated replication with the existing Oracle server in a two-hour window with only minimal interruption of service. Snavely put in place a redundant secure web server for Library Authentication and activated the load-balancing DNS infrastructure for this service to begin dynamically sharing load between the two redundant servers. Library Authentication, redundant at the web and database server levels, now serves as a working model for implementing geographically disparate, redundant web/database systems.
11.2. Explore storage options and propose an approach for future scalability.
- Marsh investigated features and prices of several network-attached storage systems and presented the information to Snavely to serve as a starting point for discussion over the coming year.
11.3. Explore options for harmonizing (or fully isolating) source code repositories on different development servers.
- Snavely put in place a networked CVS model on SPO's new development server, and Marsh released the server to SPO staff. The networked CVS arrangement is a working model for future development servers.
11.4. Critical enhancements to authentication system
- As a part of the work for DLXS release, Snavely reconfigured the authentication system build process to use current Kerberos libraries, addressing a known security vulnerability.
11.5. Release authentication system via DLXS
- Snavely added support for Linux to the DLPS Authentication and Authorization system, prepared implentor documentation, and released the system via DLXS.
11.6. Coordinate with others to explore and implement infrastructure for ongoing metadata developments, including mechanisms for metadata capture in production and ID-to-object mapping in retrieval.
- No activity this period.
11.7. Housekeeping and minor development (see goals for initial list).
- Marsh prepared and submitted the final purchases, including upgrades for mail, backups, and two production servers, for this fiscal year.
- Marsh installed a used rack that had been in storage in our central campus server environment and configured it with new UPSes. The rack will be used for new equipment as well as repurposed equipment that will be made available from this year's server upgrades and reorganization for better space usage.
- Marsh repuposed a replaced workstation as a Linux-based release-testing server for DLXS developers to use during the release process.
- Marsh installed and secured the server for the WebCheckout media booking system in coordination with the software vendor.
- Marsh purchased and installed a memory upgrade in the library web services development server to support additional users and load.
- Marsh upgraded Perl on all development and production servers with no interruption of service, and put documentation and mechanisms in place for simpler Perl module management.
- Marsh upgraded ssh (twice!) on all development and Linux production version servers to address security vulnerabilities with no interruption of service.
- Marsh supported Plantinga in completing the setup of the new InfoShare server.

14. MISCELLANEOUS

System Performance
- North Campus server environment
  All services hosted at our server environment on north campus may have been unreachable on Monday, April 8 from 5:20pm to 750pm due to a problem with network connectivity.
  - dlps1.umdl (non-public collections): No down time
  - dlps2.umdl (Oracle server for access control and usage statistics): Service limited (new account setup for library authentication was deliberately disabled) on Monday, April 1 from 7:15am to 7:34am during the second (and this time, successful) attempt to transition library authentication to a new server; taken offline after several weeks of testing
  - dlps3.umdl (Image Services): No down time
  - dlps4.umdl (primary web server for DLPS and public collections): Down on Monday, June 24 from 3:00pm to 4:40pm due to a problem with power; down again from 6:24pm to 8:40pm and from 9:45pm until 11:10pm due to storage problems caused by the earlier power outage.
  - dlps5.umdl (library proxy server): No down time
  - dlps6.umdl (new Oracle server for access control and usage statistics): Service limited (new account setup for library authentication was deliberately disabled) on Tuesday, April 16 from 7:15am to 9:40am as a redundant database server (coffee.umdl) was brought online; down on Wednesday, June 12 from 8:41am to 9:00am due to a bug in the web server software.
  - dlps7.umdl (Numeric Data server): Down from Monday, June 3 at 7:30am to Thursday, June 6 at 10:00am for an operating system version upgrade.
- Central Campus server environment
  All services hosted at our server environment on central campus were unreachable from Wednesday, April 10 at 8:00pm to Thursday, April 11 at 10:00am due to a network outage.
  - betty.umdl (MedSearch server): No down time
  - coffee.umdl (new Oracle server for access control): No down time
  - hank.umdl (Library Web Server): Down on Thursday, April 11 from 8:00am to 10:05am due to an improperly configured component of the web server software; down on Tuesday, June 11 from 1:50pm to 3:34pm due to a failed upgrade to a component of the web server software; down on Thursday, June 20 from 12:15pm to 12:20pm due to a bug in the web server software
  - myrna.umdl (MIRLYNWeb server): No down time

DLPS Core Services Monthly Report, April-June 2002

11. GENERAL ARCHITECTURE

14. MISCELLANEOUS