Hosting Service Level Agreement

Hosting Service Level Agreement

This SLA will define the requirements and guidelines to be followed for the CLAS Linux Group to host computer equipment in the 303 MLH data center.

This page is mostly obsolete and here for legacy reasons only.  All new hosting requests are being handled at the ITF data center.


The 303 MLH raised floor data center primarily hosts the infrastructure required by CLAS Linux Group to support the College of Liberal Arts & Sciences. The College of Liberal Arts, the Department of Computer Science and the CLAS Linux Group have all contributed funds to purchase an additional 10-ton chiller and 200 amp electrical  panel.  This investment will allow the CLAS Linux Group to host the departments’ growing computer infrastructure as well as allow some room for expansion.  These changes will allow the CLAS Linux Group to maintain the high level of service and reliability for its users, plus an environment suited for hosting servers with adequate power and cooling. 

Service Level Offerings

The CLAS Linux Group team will offer three service offerings to meet the varied computer hosting needs of the departments we service.  Any other usage of this server room space will be approved by the CLAS Linux Group Director on a case by case basis.

CLAS Linux shared space. Departmental shelf space. (CS, Math and Stats use only).

  1. This is a single shelving unit purchased by the CLAS Linux Group for use by the College of Liberal Arts & Sciences users.
  2. This shelving will utilize a single shared network connection on a switch managed by the CLAS Linux Group, and shared power. 
  3. Due to the shared nature of the network access, security incidents on any equipment in this space will result in an outage to all equipment using the single shared network connection.  Any users with excessive security incidents (determined by the CLAS Linux Group Director) will be required to purchase a dedicated network drop. 
  4. This space is not recommended for critical applications or high traffic applications.
  5. There is one shelf dedicated per department.  Once the shelves are full, or power, or networking, is exhausted, it will be up to the departments to fund expansion of this space.  Alternatively, the DEO will prioritize the computer hosting requests.

CLAS Linux shared rack

  1. The CLAS Linux Group has provided a 42u rack with an old 100Mb/s switch and UPS to house individual servers. The CLAS Linux Group is using the UPS as a PDU and doesn’t support or guarantee UPS functionality since this UPS is off maintenance.
  2. The CLAS Linux Group has purchased a KVM to facilitate management of the servers in this rack.  The KVM requires a dongle to be purchased for each server in this rack.
  3. Each department will be responsible for paying for network access and/or a switch and cables for the rack if required. 
  4. Each department or faculty member will be responsible for paying for additional PDU[s] (power distribution units), power or UPS to the rack if required.
  5. Each researcher or department using this rack will pay a small fee to augment the costs to the CLAS Linux Group for the KVM purchased for this rack.

Researcher dedicated rack

  1. If the researcher has needs that are not met in the above offerings and there is sufficient, space and cooling in the server room, then the researcher is encouraged to work with the CLAS Linux Group Director to procure their own rack.
  2. The researcher will pay for the KVM, networking port/switch, PDU’s, power, cabling, for this rack.
  3. The configuration must be approved by the CLAS Linux Group Director.


Regardless of which service level offering equipment falls under, the following requirements for hosting in the 303 MLH data center must be followed:

  1. The 303 MLH data center is managed by the CLAS Linux Group team and the CLAS Linux Group Director.  Any new computer hosting requests must be approved by the CLAS Linux Group Director in coordination with the DEO of Computer Science before any equipment is moved into 303 MLH.  No reselling or subletting of space in an existing rack is permitted.  Considerations of space, power, cooling and networking requirements will be discussed with the department before the equipment will be granted access to the 303 MLH data center.
  2. Physical access to the equipment will be approved on a case by case basis by the CLAS Linux Group Director via card reader access.  Improper behavior, such as tampering with other equipment in the room, will result in immediate suspension of access to the room.  Those without card access to the 303 Data center must sign in and out with CLAS Linux Group and be accompanied by an authorized individual at all times.
  3. There will be a $50/month charge, billed annually and pro-rated to the month, per rack for space provided in the 303 MLH data center.  The only exception to this billing will be as follows:
    • The following departments will have a set allocation of non billable floor space; CS will have ten floor tiles of space; Stat’s will have six tiles of space; and Math will have four.  Any request for space above and beyond this original agreed upon allocation will result in the fee per rack being charged.
    • The Hygienic lab will be allowed to house one rack of equipment in return for the CLAS Linux Group housing a rack of equipment in their data center for mutual disaster recovery protection.
  4. No Level III sensitive information as defined by​ policy shall be stored on equipment in the 303 Data center due to the shared nature of the data center unless additional checks and reviews by the IT security team are passed.
  5. Compliance with the University’s policy on data retention located at​ will be the responsibility of the department. The CLAS Linux Group may be contracted to provide backup and recovery service.
  6. Any equipment not managed by the CLAS Linux Group is deemed non-critical. The CLAS Linux Group reserves the right to power down any non-critical equipment due to security issues, power or cooling issues, etc. The CLAS Linux Group staff will attempt to notify the rack point of contact before powering down equipment if time allows.
  7. The CLAS Linux Group requests an account with shutdown privileges on all equipment hosted in the data center.  This is not required, but requested so that in the event of a cooling or power emergency, the CLAS Linux Group can attempt to gracefully shutdown non-critical equipment. 
  8. The networking arm of ITS (TNS) will provide the network access where dedicated connections are required. The CLAS Linux Group Director will be the technical contact listed on the blue req. to TNS by the department requesting service.
  9. The department or user requesting service must work with the CLAS Linux Group Director to determine power requirements and pay for power additions/changes.
  10. The department requesting service must label all equipment and cables with the hostnames of the equipment. The CLAS Linux Group has a labeler that can be used.  The rack must also have a contact list for the administrator of the equipment including name, phone number and email address.
  11. The department requesting service will be responsible for registering the equipment with the ITS server registration database. The CLAS Linux Group Director should be listed as a secondary contact when registering in this database.  The co-locator will audit their equipment yearly.
  12. In the event of a hardware failure, the vendor’s hardware repair technicians must be accompanied by a CLAS Linux Group staff member to ensure the right machines are being worked on. CLAS Linux Group staff is available 8-5 Monday-Friday.
  13. Any equipment that is primarily student managed must have a faculty sponsor and contact.

Termination and Renewal

  1. Failure to comply with any and all guidelines in this document may result in the termination of privileges to host equipment in the 303 MLH data center and access.  A 60 day notice will be given to the department to relocate their equipment.  If the equipment is not moved within 60 days, it will be disconnected from the network, powered off and moved out of the data center.
  2. Power drops left behind when equipment leaves the data center will be reused by the CLAS Linux Group and are not a part of the service price. They are not owned by the department who originally used them.
  3. Network drops left behind when the equipment leaves will be terminated if billed monthly by ITS (not on 050 funds) or reused by the CLAS Linux Group and are not a part of the service price.  They are not owned by the department/user who originally used them.