Subject:
top 10
From:
Ted Soldan <tjsold@mtu.edu>
Date:
Wed, 17 Sep 2003 19:36:09 -0400 (EDT)
To:
<mtusysadm-info-l@mtu.edu>

Here is the completed top 10 list to be discussed at tomorrow's
meeting:

> > 1.  Digital Library of Thesis/Dissertation (Williams)

Provide a database of thesis and dissertations in a standard format,
accessible to MTU students, faculty, staff, prospective students, and
alumni.  The upload and download interface should be provided in a web
page format and should be easy to follow and use. I would suggest that
this process of digital submission of MTU graduate students work be
required. I think the library, graduate school, and intellectual
properties should be involved in this process.

> > 2.  Common Authorization/Authentication (REL)

        What are the options for providing a common authentication
        mechanism in a campus environment?  What modifications and
        expections would exist at the department level?


3.  Replication Auth/Authen at Department Level (Myles)

   Design a method for replicating part of or the entire authorization and
   authentication directory at a department level, on a department-
   controlled server. This would allow the department to function if the
   main directory cluster is unavailable, as well as allow custom fields
   (such as Samba and accounting data) to be added to the directory. The
   replicated data would not necessarily be two-way (updates would be made
   to the main cluster, not to the replica), and the custom data would not
   be added to the main cluster.

> > 4.  Charter Peering (REL)

        What is the status of this?  We have been hearing peering
        is in the future.


6.  Better method for DNS requests (Myles)

   Design a new method for making DNS changes, replacing the "email to
   dns-request@mtu.edu" method. This would reduce the amount of maual data
   entry by Telcom staff, and would be more predictable (in timing of DNS
   changes, etc.). An SQL-type or command-line interface would be
preferred,
   though a web form could work as well.

> >8.  Centralized HPC expertise (Moore)

I would like to see a person(s) available to all of campus who could
assist/train sys/admins and users in applying High-Performance Computing
to
research problems.  I realize there are researchers doing this sort of
thing at MTU but their time is already spoken-for, as it were;  we need
somebody who is generally available.

> >9.  SunRay labs on dedicated (non-public) switch (Moore)

There is no reason for SunRays in a lab to not be on a dedicated network
switch, i.e., the SunRays is directly wired to a switch which is directly
wired to the SunRay server - no physical connection to the MTU public
network at all.  Using the MTU network is inefficient both in terms of
bandwidth and student funds.

> >10.  Building cell phone repeaters (Moore)

Large common areas, atria, lecture halls, etc., where events are held,
should have maximum cellphone signal strength.  This would be very useful
to our corporate visitors, in particular, as they try to stay in touch
with
their office while attending conferences here.  Maximum connectivity is a
strong need in the business world.

> >11.  Wireless networking in public areas - not Rovernet (Moore)

Same rationale as my cell phone repeater proposal.  In the SFRES case,
this
would be particularly useful as nobody bothered to put network jacks in
our
new atrium.

> > 12.  Departmental natting (REL)

        There are certain instruments in departments that have
        networked PCs that control them.  Many times the software/OS
        cannot be modified without violation of warranty agreements.
        These machines are networked because of an occasional need
        to transfer files.  A department should be able to register
        a NAT device like any other network device.

> > 13.  Define services IT will provide in NOC (REL)

        Talk has existed of file service, rack space, and other
        services.  A list of current and planned services should
        be provided so proper planning can be done if departments
        should desire to take advantage of them.

> > 14.  Campus VPN server (REL)

        What would be involved in providing a VPN server at the campus
        level?  Are there central issues if a department want to run
        their own VPN server?


15.  Cell phone integration in paging system (Myles)

   Generate a standard method for integrating cellular phones into the MTU
   paging system, using standard paging protocols. Work with MTU Cellular
to
   figure out which features are required in the service plan, and
integrate
   phones with the paging gateway and paging lists (such as mtusysadm).

> >16.  Central management of site licenses (Moore)

The amount of time that Sys/Admins spend on managing CAMPUS site licenses
is ridiculous.  This was once centralized and should be again for greater
efficiency.

> > 17.  Extension of campus network (REL)

        With IT getting into wireless WAN, what are the possibilies
        to extend some sort of WiFi (or other technology) to staff/faculty
        in the community?