Changes between Version 55 and Version 56 of Documentation/CGettingStarted
- Timestamp:
- Jan 15, 2013, 1:08:12 AM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Documentation/CGettingStarted
v55 v56 29 29 30 30 31 For example, to access the sandbox 2,31 For example, to access the sandbox1, 32 32 {{{ 33 yourhost>ssh username@console.sb 2.orbit-lab.org33 yourhost>ssh username@console.sb1.orbit-lab.org 34 34 }}} 35 35 36 36 When you have successfully logged in, you can start an experiment using the [wiki:/Software/bAM#AggregateManagers Orbit Management Framework (OMF)]. First time users are '''highly''' encouraged to reserve time on a sandbox instead of the main grid, and start with the built-in [wiki:/Tutorials/HelloWorld Hello World] experiment. 37 37 1. Before we begin using the nodes, it's a good idea to check their status first. This is done with the omf stat command. This will typically produce a result like: 38 38 39 [[Image(newhowto1.jpg)]] 40 39 41 Individual nodes are identified by their fully qualified domain name (FQDN). This establishes their "coordinates" and the "domain" to which they belong. Nodes in different domains can NOT see each other. 40 1. The node can be in 1 of 3 states: 42 2. The node can be in 1 of 3 states: 43 41 44 || POWEROFF || Node is Available for use but turned off || 42 45 || POWERON || Node is Available and is on || 43 46 || NODE NOT AVAILABLE || Node is not Available for use|| 44 1. It is recommended that the node be in the POWEROFF state prior to any experiment process. If the node is in the POWERON state you can use the omf tell command 47 48 3. It is recommended that the node be in the POWEROFF state prior to any experiment process. If the node is in the POWERON state you can use the omf tell command 45 49 to get the node into the off state. 46 50 {{{ 47 username@console.sb 2:~$ omf tell -a offh -t TOPOLOGY51 username@console.sb1:~$ omf tell -a offh -t TOPOLOGY 48 52 }}} 49 The TOPOLOGYcan take on many forms, the simplest being a comma separated list of FQDN's. There are special predefined topologies like: all, system:topo:circle, ... For more details see [wiki:/Software/bAM#AggregateManagers OMF documentation]53 The ''TOPOLOGY'' can take on many forms, the simplest being a comma separated list of FQDN's. There are special predefined topologies like: all, system:topo:circle, ... For more details see [wiki:/Software/bAM#AggregateManagers OMF documentation] 50 54 If the node is in the NODE NOT AVAILABLE state, you may need to wait for it to recover the POWEROFF state (it some times requires a few moments for the service to sync up). If 51 55 the node never comes out of the NODE NOT AVAILABLE state please contact an administrator. 52 1. Prior to the experiment, users need to install an image on the hard disks of the nodes. If you have not created a custom image use the default starting image: '''baseline.ndz'''. This image is built off ubuntu 12.04, and is pre-configured with the proper modules and start up scripts to take advantage of the rest of the Orbit Services. This is done with the omf load command 56 57 4. Prior to the experiment, users need to install an image on the hard disks of the nodes. If you have not created a custom image use the default starting image: '''baseline.ndz'''. This image is built on top of ubuntu 12.04, and is pre-configured with the proper modules and start up scripts to take advantage of the rest of the Orbit services. Loading an image is done with the omf load command 53 58 {{{ 54 username@console.sb 2:~$ omf load Topology ImageName59 username@console.sb1:~$ omf load -t TOPOLOGY -i IMAGENAME 55 60 }}} 56 Where Topology specifies the set of nodes you wish to image, and !ImageNameis the name of the image you with to load. The most common sandbox starting image command would look like61 Where ''TOPOLOGY'' is the set of nodes you wish to image , and !IMAGENAME is the name of the image you with to load. The most common sandbox starting image command would look like 57 62 {{{ 58 username@console.sb 2:~$ omf load allbaseline.ndz63 username@console.sb1:~$ omf load -t all -i baseline.ndz 59 64 }}} 60 which will load all the nodes of sandbox 2 (toatling 2) with the [wiki:Documentation/SupportedImages baseline] image.61 1. The process start should look like:65 which will load all the nodes of sandbox 1 (totaling 1) with the [wiki:Documentation/SupportedImages baseline] image. 66 5. The process start should look like: 62 67 63 68 [[Image(newhowto2.jpg)]] 64 1. A key line to look for is ''INFO whenAll: *: 'status[@value='UP']' fires''. This line indicates that all the nodes have come up and imaging has begun:69 6. A key line to look for is ''INFO whenAll: *: 'status[@value='UP']' fires''. This line indicates that all the nodes have come up and imaging has begun: 65 70 66 71 [[Image(newhowto3.jpg)]] 67 72 68 1. The final result should look like:73 7. The final result should look like: 69 74 70 75 [[Image(newhowto4.jpg)]] 71 76 72 1. At this point the nodes are imaged with the ''basline'' image and need to be turned back on before proceeding.77 8. At this point the nodes are imaged with the ''basline'' image and need to be turned back on before proceeding. 73 78 {{{ 74 79 username@console.sb2:~$ omf-5.2 tell on all … … 79 84 }}} 80 85 81 1. By default the driver modules for the wireless interfaces are disabled. It is up to the experimenter to decide which interface to use. For this tutorial experiment the ath_pci module will be used. So before running the tutorial experiment ssh into each node (ie. node1-1 & node 1-2) and load the driver modules.86 9. By default the driver modules for the wireless interfaces are disabled. It is up to the experimenter to decide which interface to use. For this tutorial experiment the ath_pci module will be used. So before running the tutorial experiment ssh into each node (ie. node1-1 & node 1-2) and load the driver modules. 82 87 {{{ 83 88 username@console.sb2:~$ ssh root@node1-1 … … 95 100 96 101 Now ssh into ''node1-2'' and do the same. 97 1 . To run a tutorial experiment that involves one UDP traffic sender and one receiver, run the following command at the console.102 10. To run a tutorial experiment that involves one UDP traffic sender and one receiver, run the following command at the console. 98 103 {{{ 99 104 username@console.sb2:~$ omf-5.2 exec --tutorial -- --tutorialName tutorial-1a … … 104 109 105 110 106 1 . Both, sender and receiver, report measurements to a database, using the OML measurement framework. The file is saved as a sqlite3 file; the file name for the experiment is shown in the last line of the tutorial's output and saved in the console under /var/lib/oml2111 11. Both, sender and receiver, report measurements to a database, using the OML measurement framework. The file is saved as a sqlite3 file; the file name for the experiment is shown in the last line of the tutorial's output and saved in the console under /var/lib/oml2 107 112 108 113 To dump the database file for this experiment:
