hwscan3: TCC processor inventory report |  |
hwscan3: TCC processor inventory report | |
The start page for the generated report will reside at
http://www.nmt.edu/tcc/hw/index.html. We'll try to keep this page fairly short,
moving bulky sections to separate pages.
There are three main categories of machines to be displayed:
Linux servers for remote login. This category includes only servers in the server room, not Linux-only clients, so it's a pretty short list.
Open labs. At this writing we have only five lab rooms.
Classrooms. Currently we maintain around twenty classrooms.
To keep the start page from getting too large, it will be structured like this.
A table labeled “Linux servers for remote login.” See Section 6.1, “Format of the server table”.
A bullet list entitled “Open labs”.
Within this list, each bullet is a link to a room page containing a table of the
clients in that lab. For the layout of this table, see
Section 6.2, “Room page layout”. Room page names will be
the same as the room prefix; for example, the room page
for Speare 5 will be named “speare5.html”.
A table entitled “Classrooms”. On the start page, we'll display a table with one row per classroom. Within this table, the room name will be a link to the room page displaying the clients in that room. For the format of the room page, see Section 6.2, “Room page layout”.
It's important to distinguish between two types of classroom: those with an instructor system only, and those that have a workstation at every seat. Consequently, rather than presenting the classrooms as a simple bullet list with one bullet per room, we will display a table with one row for each room, and these columns:
Name of the room, e.g., “cramer101”.
We derive the room name from the machine name by
discarding everything from the client name starting
at the first hyphen, if any. So, for example,
client speare5-1-11 is considered to
be in room speare5.
Number of workstations (other than the instructor machine).
Number of instructor machines—0 or 1. This will almost always be 1, so we display this information in the last column.
There is one case where the count of instructor
machines will be zero for a classroom. Speare 4 is
currently divided into three
“rooms.” The instructor machine is
speare4-inst, but the names of all
the client machines in that room start with either
“speare4a” or
“speare4b”. Thus,
room speare4 has one instructor
machine and zero clients, while rooms speare4a and speare4b have
zero instructor machines and many clients.
Because these systems are in the server room and not user-accessible, we won't need to present information on peripherals. Here are the columns in this table, in order.
Server name, e.g., “login”.
Number of CPUs.
Processor speed in MHz.
Architecture, typically “i686”.
Memory size in MB.
For each open lab or classroom, there will be a room page displaying the information on the clients in that room as a table.
Client name, e.g., speare5-1-6.
Number of CPUs.
Processor speed in MHz.
Architecture, e.g., “i686”.
Memory size in MB.
Operating system: one of “Linux/Windows”, “Linux-only”, or “Mac OS
X”.
List of peripherals of interest to users. Because there are several types, we won't put each type in a separate column; that would make the table much too wide.
Instead, there will be one column labeled “Peripherals”, with vertically stacked blocks for each peripheral.
Each block will start with a label such as “Video:”, “Monitor:”, “Optical:”, or “Scanner:”, followed by the description of that peripheral.
These blocks will use a hanging indent, so that if the entry for one peripheral does not fit within the width of a cell, continuation lines will be indented further.