Roles and Responsibilities

From CSLabsWiki
Jump to: navigation, search

The Roles and Responsibilities were written so that more people can get actively and productively involved in the labs. Since the individuals who are responsible for each role are listed as well, it should be more clear who to talk to when different questions arise.

Lab Directors

Currently: Abigail Matthews & Hunter Bashaw & Hunter Quant

Credits: 1 for MP*51/MP*52

Responsibilities:

  • Work with faculty adviser to propose, maintain, and update list of ongoing projects on web site
  • Help to match students to projects and mentors
  • Produce end of semester report on status of projects/accomplishments etc
  • Presentation at Open House
  • Run COSI meetings, send announcement for meetings, set agendas, take attendance
  • Take detailed notes on meetings/ideas
  • Maintain continuity binder (digitally)

Linux Build Maintainer(s)

ITL HDD: xperia64

COSI: xperia64

VR Lab: xperia64

Credits: 1-2 for MP*51

Responsibilities:

  • Maintain a list of software installed on the Linux build in the ITL/VR labs on web site
    • Solicit input on this list and present it to the CSLAB-ADMIN board for approval
  • Distribute a new build to the computers in the lab as needed
  • Maintain a document on procedures for distributing new builds, train others in this process
    • Maintain a best practices guide for producing the build (security practices, patching software etc)
    • First point of contact for reports of problems with software or requests for new software
  • First point of contact for reports of problems with software or requests for new software

Windows Build Maintainer(s)

ITL: xperia64

VR: Core Maintainers

Credits: 1-2 for MP*52

Responsibilities:

  • Maintain a list of software installed on the Windows builds on web site
    • Solicit input on this list and present it to the CSLAB-ADMIN board for approval
  • Distribute a new build to the computers in the lab as needed
  • Maintain a document on procedures for distributing new builds, train others in this process
    • Maintain a best practices guide for producing the build (security practices, patching software etc)
    • First point of contact for reports of problems with software or requests for new software
  • Assemble and maintain information on any licenses for software - how many, where obtained, etc.

Network Administrator(s)

Currently: Graham, Jared, xperia64

Credits: 1-2 for MP*52

Responsibilities:

  • At least once a semester do a site survey (e.g. nmap) of the IP addresses and open ports in the lab and present to CSLAB-ADMIN board
  • Maintain a list of all machines connected to the lab subnet (ideally web accessible but password protected)
  • Maintain list of static IP addresses
  • Maintain wireless access points
  • Produce and maintain a network diagram showing all switches, routers, wireless access points etc
  • Produce and maintain a guide to administering our routers and switches and wireless access points, how to configure, etc
  • First point of contact for reports of problems with network connectivity, reports of network attacks
  • This need not include maintaining configuration guides to non-production routers but could

Services Maintainer(s)

Currently: Individual system maintainers

Credits: 1-2 for MP*51 or MP*52

Responsibilities:

  • For each service, produce and maintain a document describing how the services are configured/started/shutdown, what version/type of server software is being run, requirements for running each service
  • First point of contact for problems with that service
  • Keep server software well patched
  • Produce some usage statistics on each service ( bytes downloaded from mirror, connections to www, etc.) where possible and present to CSLAB-ADMIN board once per semester
  • For more information, see Maintaining a Service.

Server Setup Administrator(s)

Currently: Looking for a maintainer

Credits: 1-2 for MP*51 or MP*52

Responsibilities:

  • Produce and maintain a list of available services maintained by the labs (website)
  • Produce and maintain a physical inventory of all our equipment including model numbers, serial numbers, where/when purchased, where located, etc (focus on equipment inside the server room)
  • Produce and maintain a map of what software is being run on each machine and for what purpose
  • Produce and maintain a list of procedures for power down and up all the servers.

Storage Administrator(s)

Currently: Baha

Credits: 1-2 for MP*51

Responsibilities:

  • Maintain the storage array in the server room.
  • Document the RAID configuration.
  • Maintain interfaces to this storage (distributed file servers etc).
  • Produce and maintain a document describing the details of how this service is configured.
  • Produce and maintain a document that describes the policy for requesting/using storage space ( how much, will it be backed up, on what schedule). Present this document to the Admin board for discussion/approval.
  • Handle requests for storage space according to this policy.
  • Once per semester produce a report on how much storage is used, how much is free, how it is configured and roughly how the storage is being used.

Physical Infrastructure

Currently: Core Maintainers

Credits: 1-2 for MP*51 or MP*52

Responsibilities:

  • Produce and maintain a physical inventory of all our equipment including model numbers, serial numbers, where/when purchased, where located, etc (focus on equipment outside the server room)
  • Organize and maintain library of manuals, receipts, etc.
  • Monitor the output of temperature monitoring system – produce a report of the temperature stability across the semester for the CSLAB-ADMIN board
  • First point of contact for interacting with facilities on issues such as power, cooling, windows, lab cleanliness, etc.
  • Work with the lab build maintainers to assure that printers are accessible
  • Monitor stocks of paper/printer cartridges

Web Page Designer(s)/Maintainer(s)

Currently: Benjamin Lannon

Credits: 1-2 for MP*51 or MP*52

Responsibilities:

  • Maintain and propose changes to the overall design, layout and content on the lab web pages
  • Proactively look for news to post from events, accomplishments, status given at meetings
  • Maintain a list of bug/known issues for lab infrastructure ( basically maintain the facility that all other lab members can use for this purpose)