Differences

This shows you the differences between two versions of the page.

--- techstaff:phd_orientation_2017 [2017/09/19 11:11] – [Interactive login servers] kauffman
+++ techstaff:introduction [2017/09/22 12:20] – [Quotas] kauffman
@@ Line 53: / Line 53: @@
 ======Instructional servers======
 =====Linux.cs.uchicago.edu=====
-Previously described in the [[techstaff:phd_orientation_2017#interactive_login_servers|Interactive login server]] section.  These larger systems are configured to support instructional computing, though they are also general use.  Their main purposes include:
+Previously described in the [[techstaff:introduction#interactive_login_servers|Interactive login server]] section.  These larger systems are configured to support instructional computing, though they are also general use.  Their main purposes include:
   * a place for students to work on assignments outside of the lab
   * a place for TA’s to test course assignments and grade assignments
   * a place for general computing that will not compromise the performance of the lab machines
 The systems support many users and should be respected. Please follow the following guidelines:
-Resource intensive activities (utilize large amounts of RAM, excessive disk I/O, multiple CPUs, or long execution times) should be directed to your desktop or elsewhere (see [[techstaff:slurm|SLURM]] for internal options, or RCC (https://rcc.uchicago.edu/) for external options)
+Resource intensive activities (utilize large amounts of RAM, excessive disk I/O, multiple CPUs, or long execution times) should be directed to your desktop or elsewhere (see [[techstaff:slurm|SLURM]] for internal options, or [[https://rcc.uchicago.edu|RCC]] for external options).
 Programs requiring significant disk I/O should not use your home directory as a data repository.  The home directory is convenient but it is slow.  Please create a directory in the /local directory and use that directory for your data source.  /local is a local disk and is orders of magnitude faster than NFS.
@@ Line 64: / Line 64: @@
 =====Course specific=====
-Some courses have course specific machines.  These may be bare metal or virtual.  For certain courses, we have reconfigured a server to support the course exclusively.  This is rare.  A number of courses have moved to virtual machines.  There are two types – personal and server-based.  The personal ones are VirtualBox images that are originally configured by Techstaff for general use by courses.  They are a baseline systems with a minimal software install to keep the size small for distribution.  These systems are further configured with software for the course and are distributed to students for installation on personal systems.  The other type of virtual system is a customized VM that is running on one of Techstaff’s hypervisors and is managed by Techstaff.  It is configured explicitly for a particular course, but provides services (database, web, etc.) required by the course.
+Some courses have course specific machines.  These may be bare metal or virtual.  For certain courses, we have reconfigured a server to support the course exclusively.  This is rare.  A number of courses have moved to virtual machines.  There are two types – personal and server-based.
-(Information is available at https://howto.cs.uchicago.edu/vm:index.)
+The [[vm:index|personal ones]] are VirtualBox images that are originally configured by Techstaff for general use by courses.  They are a baseline systems with a minimal software install to keep the size small for distribution.  These systems are further configured with software for the course and are distributed to students for installation on personal systems.
+The other type of virtual system is a customized VM that is running on one of Techstaff’s hypervisors and is managed by Techstaff.  It is configured explicitly for a particular course, but provides services (database, web, etc.) required by the course.
 =====SLURM=====
-The SLURM cluster was originally constructed to support Hank Hoffmann’s OS course.  SLURM is a job scheduling system that allows users to submit requests for resources and allows them to execute jobs using those reserved resources.  (Information about SLURM and its use is available at https://howto.cs.uchicago.edu/techstaff:slurm.)
+The [[techstaff:slurm|SLURM cluster]] was originally constructed to support Hank Hoffmann’s OS course.  SLURM is a job scheduling system that allows users to submit requests for resources and allows them to execute jobs using those reserved resources.
-The cluster can also be rather than linux.cs.uchicago.edu for larger jobs.  Additionally, we have a couple of GPUs that can be utilized on the cluster.
+The cluster should be used for larger jobs, rather than than linux.cs.uchicago.edu. Additionally, we have a couple of GPUs that can be utilized on the cluster.
 =====Hadoop=====
-We are experimenting with an Apache Hadoop cluster for use by several big data courses.  Contact us directly for additional information. (Information is available at https://howto.cs.uchicago.edu/bigdataetc.)
+We are experimenting with an [[bigdataetc|Apache Hadoop cluster]] for use by several big data courses.  Contact us directly for additional information.
 ======Labs======
 The department supports two computer labs.
 =====CSIL=====
-CSIL is located in Crerar Library and is composed of 4 pods of computers along with additional Macs external to the pods and a staff of student aids known as “tutors”. The pods have collapsing walls that allow them to be reconfigured into larger spaces.  Two of the pods each contain Linux boxes that are configured and managed by Techstaff.  They are configured using a template similar to  linux.cs.uchicago.edu or student desktops. The linux systems are rebooted each morning at 4:00 AM in order to clean up processes and to make them less desirable platforms for long term execution which would impact performance for the seated user. The other two pods each contain 20 Macs which are configured and maintained by CSIL tutors.
+[[http://csil.cs.uchicago.edu|CSIL]] is located in Crerar Library and is composed of 4 pods of computers along with additional Macs external to the pods and a staff of student aids known as “tutors”. The pods have collapsing walls that allow them to be reconfigured into larger spaces.
-These pods are reserved for a number of courses for labs, class, or TA sessions. The software on both architectures supports the needs of many courses allowing students to have access to reliable systems that will work consistently for course assignments. (Information at http://csil.cs.uchicago.edu.)
+Two of the pods each contain Linux boxes that are configured and managed by Techstaff. They are configured using a template similar to  linux.cs.uchicago.edu or student desktops. The linux systems are rebooted each morning at 4:00 AM in order to clean up processes and to make them less desirable platforms for long term execution which would impact performance for the seated user. The other two pods each contain 20 Macs which are configured and maintained by [[http://csil.cs.uchicago.edu|CSIL]] tutors.
+These pods are reserved for a number of courses for labs, class, or TA sessions. The software on both architectures supports the needs of many courses allowing students to have access to reliable systems that will work consistently for course assignments.
 =====MPCS=====
@@ Line 113: / Line 117: @@
 =====Quotas=====
-We place quotas on the home directory.  The starting quota is 2.5GB.  Most users do not exceed this limit and it is mostly in place to prevent runaway log files or similar inadvertently large files.  We will increase it upon reasonable request.
+We place quotas on the home directory.  The starting quota is 5GB.  Most users do not exceed this limit and it is mostly in place to prevent runaway log files or similar inadvertently large files.  We will increase it upon reasonable request.
 =====Self Management=====