memorandum
To: Katalin
Voros, Operations Manager
From: Todd Merport, Computer Systems
Manager
Subject: 2006 Year-End Report
Date: 16 January 2007
The Microfabrication Laboratory Computer Systems Group
provides a variety of services for members and staff. These services range from
Windows workstation installation to database programming. In all, the computer
systems group is responsible for lab management software and hardware
components that are an integral part of 24/7 Microlab operations.
Microlab computing systems operate within the EECS and
department network infrastructure. We are required to maintain minimum security
standards for all networked devices. This insures data integrity, system
reliability, and a high level of overall robustness of all systems. The campus
and department must maintain a high level of vigilance to insure bad actors do
not compromise data or campus resources and are not used to attack other
computers. The oversight by the
department and campus is an important service although we are totally
responsible to insure the security of our networked devices. If the campus and
department personnel feel a device is not meeting the security requirements,
they have the responsibility to pull the device off the network (if we don’t
take care of it first). Our job is to
be very vocal regarding security requirements and work hard to insure our
systems are properly up-to-date. Table
1 shows a breakdown of system types and functions.
I supervise 3 Programmer/Analysts. We strive to be
diverse in our skills and available to help Microlab members. The
responsibilities of computer group
staff are listed below:
Changrui Yin
Olek
Proskurowski
Eniko Seen
Todd
Merport
With special thanks to Madeleine Leullier who assists
members with computer problems and helps manage computer resources.
A major
feat this year has been the retirement of the old SunOS system argon
(along with lead). Argon hosted the Microlab database and an older version
of INGRES. All applications, both database and BCIMS (the wand), are now
running on a Solaris 10 system (silicon2). We are keeping silicon as the master password database and
incoming mail server. Part of the
migration process required consolidating our web server on silicon2 to host
static Microlab web pages and database driven pages such as reservations and
qualifications. See figures 1 and 2 for
a view of our new configurations. Olek took the lead on this migration; the
project entailed creating a build system, porting code, and insuring every
“wand” and database application ran properly.
My role on the project has been fixing small problems, testing, and
coordination of the change-over.
Members will see much faster web pages for qualifications and
reservations. Also using the new secure server, members only need to login once
to access all reservation pages.
Home and project directories have been moved off
silicon to a Sun V240 server running Solaris 10 (the hostname is
mercury). This server has
redundant disk drives and power supplies, dual CPUs, and 8GB of memory. It also hosts INGRES databases and the MERCURY project server. Migrating home directories off silicon
required setting up RAID on mercury, creating scripts to modify password
databases, and setup Windows compatible file sharing.
I
developed the server side schema for the pumps database. The schema uses
database procedures and triggers to track the status of specific pumps and
provide historical information based on a model, equipment, or pump. By using
database procedures and triggers, we have a great deal of versatility with the
user interface. Changrui Yin designed a MS Access user interface that generates
forms and reports. .
Changrui
did a hardware/software upgrade on our Windows file, sql, and web server
microlab2. The benefit for this upgrade includes hardware RAID level 1 (mirror),
increased disk space, more memory, and a faster CPU. The OS has been updated
from Windows 2000 Server to Windows 2003 Server. The old microlab2 hardware has been updated to Windows 2003
Server and is used as a general purpose terminal server for Microlab staff.
Changrui
installed 22 new computers over the last year that are used for servers, staff
workstations, or equipment.
I added a
network accelerator card on cape that offloads network based processing.
This takes some of the burden off the microprocessors. A new network switch was
added to cape to further improve the network pipeline.
Eniko has completed the equipment page of the Mercury
project. This includes activities members and staff do in the lab such as
enabling/disabling, filing a problem/clearing
reports, equipment comments, super user login, and details of costs for
activites. Olek modified the database
tables for equipment problems and wrote a script to upload and re-associate
equipment problems/symptoms with a set from a common pool. I created a history
mechanism that permits logging before/after values, date, and member from any
data record in the database. This will be especially useful for the accounting
group. Olek and Eniko will elaborate in
their “Comments” section.
The autoprobe station with the EGLAS software set was
replaced with a Solaris 10 system. The memscope was rebuilt (LINUX) and further
updated to a PC with an EPIX image card.
Artwork conversion software was upgraded; Microlab scripts were modified
to affect this change. silicon was
compromised and off-line for a day. CUSG quickly responded to rebuild the
system. Several lab equipment computers
were rebuilt or cloned.
Since joining in June I have
worked virtually with every system in Microlab. I developed code for both Wand
and Mercury system, performed system administration tasks on existing systems
and even replaced network terminal in the lab.
Wand
Mercury
System Administration
Misc.
Development
continues on all aspects of the Mercury project. Accomplishments:
·
to continue with the Java/SWING/XML or
·
to use WEB (AJAX or JavaServer Faces).
We are
leaning towards Web based implementation. Tools offered for WEB implementation to
be considered:
In 2006, I
have taken care of the following tasks:
Window Servers Maintenance
New Servers
Workstation and Printer Support
UNIX System Administration
Pump Management System
Future Plan and Projects
Tools to generate web-based forms and reports are being
evaluated. This will allow rapid
development for parts of MERCURY that do not need to have real-time
functionality and fast response. Examples include membership forms, accounting
reports, and purchase orders. The
architecture of the MERCURY keeps the client lightweight (business rules are in
the database server) permitting accessing and modifying data from many
different technologies.
A new server will be ordered to replace the NIS
database and mail server, silicon (circa 1999). The hardware/software
should be setup and deployed by mid-year.
Cape will be given a hardware/software replacement as well.
Cape. is well overburdened due to the high use of the internet in the lab
(circa 2000).
Microlab computer systems are on a solid footing this
year. It is always challenging and rewarding keeping the varied systems working
together - intimidating even the most technically savvy. Although the MERCURY project has not been
released, some of the work has been incorporated into current systems. And even though MERCURY is the most visible
project for the computer group, many other tasks have been completed in 2006.
Function |
Platform |
Operating
System |
Count |
Desktop |
X86 Dell (Mostly) |
Windows XP |
42 |
Web, FileSystem, Database, Mail,
Applications |
UltraSparc |
Solaris 2.6-10 |
3 |
Web, LabView |
X86 Dell |
Windows 2000 Server |
1 |
Terminal Services |
X86 Dell |
Windows 2000 Server |
1 |
FileSystem, Web, Database,
Anti-Virus |
X86 Dell |
Windows 2003 Server |
4 |
Cad Workstation, EGLAS |
UltraSparc |
Solaris 7,9,10 |
4 |
Cad Workstation |
X86 Dell |
Windows XP |
1 |
Thin Clients |
Neoware |
Windows CE |
16 |
Interlock Controllers |
X86 |
LINUX |
3 |
TOTAL |
|
|
75 |
Table 1
- Microlab Systems Summary (not including equipment)
Figure 1
- Microlab Computer Infrastructure
Figure 2 - Web Server Infrastructure