Changes between Version 2 and Version 3 of ClassResourceLimits

Timestamp:

Oct 7, 2010 2:32:10 PM (14 years ago)

Author:

mikeryan

Comment:

reorganize, give better explanation

ClassResourceLimits

@@ -1 @@
-DETERlab has 400 PCs (hereafter: nodes) split between ISI in Marina del Rey and UC Berkeley. They are our most scarce resource.
+== What are resource limits? ==
 
-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. We also reserve nodes for classes on days leading up to deadlines.
+If you are a class user, your class only have access to a limited number of nodes. You can see how many nodes are available for your class on your My DETERlab page.
+
+== What error message will I receive if there are no nodes left for my project? ==
+
+Something like this:
+{{{
+Admission Control: $project/$experiment has too many nodes allocated!
+}}}
 
 == Maximum Node Usage ==
@@ -9 +16 @@
 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).
 
-== Reserved Nodes ==
+== Rationale ==
 
-We reserve 1/4 of a class's max required nodes for three days leading up to a deadline.
+DETERlab has 400 nodes (physical PCs) split between ISI in Marina del Rey and UC Berkeley. They are our most scarce resource.
 
-== What error message will I receive if there are no nodes left for my project? ==
-Something like this:
-{{{
-Admission Control: $project/$experiment has too many nodes allocated!
-}}}
+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.