Changes between Version 2 and Version 3 of ClassResourceLimits


Ignore:
Timestamp:
Oct 7, 2010 2:32:10 PM (13 years ago)
Author:
mikeryan
Comment:

reorganize, give better explanation

Legend:

Unmodified
Added
Removed
Modified
  • ClassResourceLimits

    v2 v3  
    1 DETERlab has 400 PCs (hereafter: nodes) split between ISI in Marina del Rey and UC Berkeley. They are our most scarce resource.
     1== What are resource limits? ==
    22
    3 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.
     3If 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.
     4
     5== What error message will I receive if there are no nodes left for my project? ==
     6
     7Something like this:
     8{{{
     9Admission Control: $project/$experiment has too many nodes allocated!
     10}}}
    411
    512== Maximum Node Usage ==
     
    916Collectively all classes will be limited to 2/3 of the maximum capacity of the testbed at all times (which is to say: 265 nodes).
    1017
    11 == Reserved Nodes ==
     18== Rationale ==
    1219
    13 We reserve 1/4 of a class's max required nodes for three days leading up to a deadline.
     20DETERlab has 400 nodes (physical PCs) split between ISI in Marina del Rey and UC Berkeley. They are our most scarce resource.
    1421
    15 == What error message will I receive if there are no nodes left for my project? ==
    16 Something like this:
    17 {{{
    18 Admission Control: $project/$experiment has too many nodes allocated!
    19 }}}
     22In 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.