Changes between Version 2 and Version 3 of Internal/NodeHandler/New


Ignore:
Timestamp:
Sep 27, 2006, 4:10:31 PM (18 years ago)
Author:
anonymous
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Internal/NodeHandler/New

    v2 v3  
    55 * '''Imaging 400 nodes'''
    66
    7   1) After starting nodehandler (both imaging and experimentation), start communication layer process (ind1)
    8   2) 4 communication groups created for imaging all nodes. Each group is responsible for prespecified nodes. (Could be moved to a config file)
    9   3) Communication layer has to be started manually, but it will be terminated automatically by nodehandler at the end of the experiment
     7  1. After starting nodehandler (both imaging and experimentation), start communication layer process (ind1)
     8  2. 4 communication groups created for imaging all nodes. Each group is responsible for prespecified nodes. (Could be moved to a config file)
     9  3. Communication layer has to be started manually, but it will be terminated automatically by nodehandler at the end of the experiment
    1010
    1111 * Main steps
    12  1) 80 is the magic number for the group size.
    13  2) Switch on nodes in groups of 80.
    14  3) Retry upto three times..
    15  4) Give up for those nodes that do not boot into pxe
    16  5) Then switch on the next group of 80... and so on..
    17  6) Until whenAll, then start frisbee process
    18  7) Switch off nodes in the order of completion..
     12  1. 80 is the magic number for the group size.
     13  2. Switch on nodes in groups of 80.
     14  3. Retry upto three times..
     15  4. Give up for those nodes that do not boot into pxe
     16  5. Then switch on the next group of 80... and so on..
     17  6. Until whenAll, then start frisbee process
     18  7. Switch off nodes in the order of completion..
    1919
    2020Frisbee time is fairly constant, main problem is with initial booting into pxe image