Changes between Version 33 and Version 34 of Tutorials/a0Basic/Tutorial2


Ignore:
Timestamp:
Feb 13, 2013, 5:05:48 AM (11 years ago)
Author:
ssugrim
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Tutorials/a0Basic/Tutorial2

    v33 v34  
    173173Before being able to run this experiment, you should:
    174174
    175  * [http://www.orbit-lab.org/register Register] for an account (if you have not done so yet)
    176  * [https://www.orbit-lab.org/schedule/ Make a reservation] on the Scheduler for a time slot on one of the sandbox testbed
    177  * Log into the console machine corresponding to this testbed. To control the Node Handler, your experiment, and the nodes on the testbed(s), you will use the generic '''orbit''' command and its options.
     175 * Make sure you have followed the getting started procedure [wiki:Documentation/GettingStarted getting started]
     176 * Once you have proper reservation, login to the console.
     177 * Install a disk image which includes ''Ex'' on the nodes of this testbed. For example, you can use the latest ''baseline.ndz'' disk image. This disk image installation is done using the ''omf load'' command above. Detailed instructions on how to perform such disk image installation on the nodes on a testbed can be found [wiki:Tutorials/HowToImage here].
    178178 {{{
    179   # User Bob reserved a time slot on the sandbox1 testbed.
    180   # He then can access the sandbox1 console using the command:
    181  
    182   ssh bob@console.sb1.orbit-lab.org
    183 
    184   # To see a list of commands available through the orbit command:
    185   orbit help
    186 
    187   # which will give the following output
    188   Run a command on the testbed(s)
    189 
    190   Usage: orbit [COMMAND] [ARGUMENT]...
    191 
    192   Available COMMANDs:
    193 
    194     help   Print this help message or a specif command usage
    195     exec   Execute an experiment script
    196     load   Load a disk image on a given set of nodes
    197     save   Save a disk image from a given node into a file
    198     tell   Switch a given set of nodes ON/OFF
    199     stat   Returns the status of a given set of nodes
    200 
    201   To get more help on individual commands: 'omf help [COMMAND]'
    202   Examples:
    203             orbit help exec   Return usage/help for the 'exec' command
    204             orbit help load   Return usage/help for the 'load' command
     179ssugrim@console.grid:/usr/bin$ omf help exec
     180
     181OMF Experiment Controller 5.4 (git c005675)
     182
     183Execute an experiment script
     184
     185Usage:  exec [OPTIONS] ExperimentName [-- EXP_OPTIONS]
     186
     187        ExperimentName is the filename of the experiment script
     188        [EXP_OPTIONS] are any options defined in the experiment script
     189        [OPTIONS] are any of the following:
     190
     191    -a, --allow-missing              Continue experiment even if some nodes did not check in
     192    -c, --config NAME                Configuration section from the config file ('default' if omitted)
     193    -C, --configfile FILE            File containing local configuration parameters
     194    -d, --debug                      Operate in debug mode
     195    -i, --interactive                Run the experiment controller in interactive mode
     196    -l, --libraries LIST             Comma separated list of libraries to load (defaults to [system:exp:stdlib,system:exp:eventlib,system:exp:winlib])
     197        --log FILE                   File containing logging configuration information
     198    -m, --message MESSAGE            Message to add to experiment trace
     199    -n, --just-print                 Print the commands that would be executed, but do not execute them
     200    -N, --no-am                      Don't use the Aggregate Manager (AM)
     201    -p, --print URI                  Print the contents of the experiment script
     202    -o, --output-result FILE         File to write final state information to
     203    -e, --experiment-id EXPID        Set the ID for this experiment, instead of the default standard ID
     204    -O, --output-app                 Display STDOUT & STDERR output from the executed applications
     205    -r, --reset                      If set, then reset (reboot) the nodes before the experiment
     206    -s, --shutdown                   If set, then shut down resources at the end of an experiment
     207    -S, --slice NAME                 Name of the Slice where this EC should operate
     208    -t, --tags TAGS                  Comma separated list of tags to add to experiment trace
     209        --oml-uri URI                The URI to the OML server for this experiment
     210    -x, --extra-libs LIST            Comma separated list of libraries to load in addition to [system:exp:stdlib,system:exp:eventlib,system:exp:winlib]
     211        --slave-mode EXPID           Run in slave mode in disconnected experiment, EXPID is the exp. ID
     212        --slave-mode-resource NAME   When in slave mode, NAME is the HRN of the resource for this EC
     213    -h, --help                       Show this message
     214    -v, --version                    Show the version
    205215
    206216 }}}
    207217
    208  * Install a disk image which includes ''nodeAgent4'' on the nodes of this testbed. For example, you can use the latest ''baseline.ndz'' disk image. This disk image installation is done using the ''omf load'' command above. Detailed instructions on how to perform such disk image installation on the nodes on a testbed can be found [wiki:Tutorials/HowToImage here].
     218
    209219
    210220
     
    212222
    213223{{{
    214 omf exec --tutorial
    215 }}}
    216 Normally an experiment is described in a script file, e.g. "my_experiment.rb", which is run by using the command "omf exec my_experiment". However in this particular case, the tutorial script is already stored in a repository known by the ''omf exec'' application. Thus the "--tutorial" option instructs the ''omf exec'' application to fetch that script and execute it.
     224omf exec test:exp:tutorial:hello-world-wireless.rb
     225}}}
     226Normally an experiment is described in a script file, e.g. "my_experiment.rb", which is run by using the command "omf exec my_experiment". However in this particular case, the tutorial script is already stored in a repository known by the ''omf exec'' application. Thus the "test:exp:tutorial:hello-world-wireless.rb" option instructs the ''omf exec'' application to fetch that script and execute it.
    217227
    218228After running the above command, your console output should look like this:
    219229
    220230{{{
    221 console.sb1:~# omf exec --tutorial
    222 DEBUG Experiment: Domain: sb1
    223  INFO init: NodeHandler Version 4.2.0 (1272)
    224  INFO init: Experiment ID: sb1_2007_11_19_19_15_19
    225  INFO Experiment: load system:exp:stdlib
    226  INFO prop.resetDelay: resetDelay = 210:Fixnum
    227  INFO prop.resetTries: resetTries = 1:Fixnum
    228  INFO Experiment: load test:exp:tutorial-1a
    229  INFO stdlib: Waiting for nodes (Up/Down/Total): 0/2/2 - (still down: n_1_2,n_1_1)
    230  INFO stdlib: Waiting for nodes (Up/Down/Total): 0/2/2 - (still down: n_1_2,n_1_1)
    231  INFO stdlib: Waiting for nodes (Up/Down/Total): 0/2/2 - (still down: n_1_2,n_1_1)
    232  INFO stdlib: Waiting for nodes (Up/Down/Total): 0/2/2 - (still down: n_1_2,n_1_1)
    233  INFO stdlib: Waiting for nodes (Up/Down/Total): 0/2/2 - (still down: n_1_2,n_1_1)
    234  INFO stdlib: Waiting for nodes (Up/Down/Total): 0/2/2 - (still down: n_1_2,n_1_1)
    235  INFO n_1_1: Device 'net/w0' reported Not-Associated
    236  INFO stdlib: Waiting for nodes (Up/Down/Total): 1/1/2 - (still down: n_1_2)
    237  INFO whenAll: *: 'apps/app/status[@value='INSTALLED.OK']' fires
    238  INFO n_1_1: Device 'net/w0' reported 00:60:B3:25:BF:F5
    239  INFO n_1_2: Device 'net/w0' reported 00:60:B3:25:BF:F5
    240  INFO OML: Started: {"port"=>"7600", "iface"=>"eth2", "addr"=>"224.0.0.6"}
    241  INFO Experiment: DONE!
    242  INFO ExecApp: Application 'commServer' finished
    243  INFO run: Experiment sb1_2007_11_19_19_15_19 finished after 3:41
    244 console.sb1:~#                                         
     231Test results go here:   
    245232}}}
    246233