Changes between Version 4 and Version 5 of ClassResourceLimits

Timestamp:

Mar 15, 2013 12:33:29 AM (12 years ago)

Author:

sklower

Comment:

Implies that there is a preset default value and was not accurate; we no longer use the google doc

ClassResourceLimits

@@ -12 +12 @@
 == Maximum Node Usage ==
 
-Each class is limited to a portion of its max required nodes for the duration of an assignment. This portion is around 1/4-1/3 for large classes and around 1/2 for small ones. It is somewhat subjectively set by DETERLab ops team but it can be changed by instructors by modifying the "limit" row for their class in the GoogleDoc spreadsheet.
+Each class is limited to a portion of its max required nodes for the duration of an assignment. This portion should be around 1/4-1/3 for large classes and around 1/2 for small ones. Instructors are asked to set this limit by clicking on the "Teaching" tab of their "My DETERlab" page, and then clicking in the "Input Schedule" box under "Class Projects".
 
-Collectively all classes will be limited to 2/3 of the maximum capacity of the testbed at all times (which is to say: 265 nodes).
+Collectively all classes will be limited to 2/3 of the maximum capacity of the testbed at all times (which is to say: 330 nodes).
 
 == Rationale ==
 
-DETERlab has 400 nodes (physical PCs) split between ISI in Marina del Rey and UC Berkeley. They are our most scarce resource.
+DETERlab has 500 nodes (physical PCs) split between ISI in Marina del Rey and UC Berkeley. They are our most scarce resource.
 
 In order to provide fair access to nodes to all users of the testbed (researchers and classes alike), we impose limits on the maximum number of nodes available to classes.