Changes between Version 2 and Version 3 of Tutorials/oMF/tut1


Ignore:
Timestamp:
Oct 15, 2014, 7:15:03 AM (8 years ago)
Author:
wontoniii
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Tutorials/oMF/tut1

    v2 v3  
    5151}}}
    5252
    53 
    54 
    55 {{{
    56 #!sh
    57 
    58 omf load -i 'mf-release-latest.ndz' -t system:topo:mf-group1
    59 }}}
    60 
    61 where the above assumes you are attempting to image node1-1 in the 'sb9.orbit-lab.org' domain (Sandbox 9). You could also just use 'node1-1' without the domain part - assumed from the console you issue the command from. So for installing the image across 4 nodes - node1-1, node1-2, node1-3, node1-4 - the following can be used:
    62 
    63 {{{
    64 #!sh
    65 omf load -i 'mf-release-latest.ndz' -t 'node1-1,node1-2,node1-3,node1-4'
    66 }}}
    67 
    68 The imaging should be done for each node to be used in our network deployment, and can be done in a single shot by providing multiple comma separated hostnames within the '-t' topology argument above.
     53From the console we will start by loading the Mobilityfirst image into the four nodes that have been assigned to you:
     54
     55{{{
     56#!sh
     57
     58omf load -i 'mf-release-latest.ndz' -t system:topo:mf-groupX
     59}}}
     60
     61'''system:topo:mf-groupX''' represents the group of 4 nodes and '''mf-groupX''' has to be replaced by the group id assigned to you.
     62
     63For example, '''mf-group1''' will load the image on nodes 'node1-1,node1-2,node2-1,node2-2'
     64
     65If the output of your console looks similar to:
     66
     67{{{
     68#!sh
     69
     70INFO exp:  -----------------------------
     71 INFO exp:  Imaging Process Done
     72 INFO exp:  4 nodes successfully imaged - Topology saved in '/tmp/pxe_slice-2014-10-15t02.10.16.594-04.00-topo-success.rb'
     73 INFO exp:  -----------------------------
     74 INFO EXPERIMENT_DONE: Event triggered. Starting the associated tasks.
     75 INFO NodeHandler:
     76 INFO NodeHandler: Shutting down experiment, please wait...
     77 INFO NodeHandler:
     78 INFO NodeHandler: Shutdown flag is set - Turning Off the resources
     79 INFO run: Experiment pxe_slice-2014-10-15t02.10.16.594-04.00 finished after 1:50
     80}}}
     81
     82your nodes have been imaged correctly.
    6983
    7084=== Deploy Network ===
     
    321335{{{
    322336#!sh
    323 mfping -S <my-GUID>
    324 }}}
     337mfping -s -m 102 -o 101
     338}}}
     339
     340where "-s" specifies that the host is running as server, "-m" specifies the source guid and "-o" the destination one
    325341
    326342To run the mfping 'client'
     
    328344{{{
    329345#!sh
    330 mfping -C <my-GUID> <server-GUID> -i <interval_secs> -c <count>
    331 }}}
    332 
    333 You should see an out at the client similar to below:
    334 
    335 {{{
    336 #!sh
    337 
     346mfping -c -m 101 -o 102 -n 10
     347}}}
     348
     349If successfully executed, the client will display some information similar to the following snippet
     350
     351{{{
     352#!sh
     353
     354root@node1-1:~# mfping -c -m 101 -o 102 -n 10
     35564 bytes received: seq_n=0, time=25.1470 msec
     35664 bytes received: seq_n=1, time=23.7070 msec
     35764 bytes received: seq_n=2, time=20.0559 msec
     35864 bytes received: seq_n=3, time=24.0371 msec
     35964 bytes received: seq_n=4, time=23.1831 msec
     36064 bytes received: seq_n=5, time=20.3069 msec
     36164 bytes received: seq_n=6, time=24.1379 msec
     36264 bytes received: seq_n=7, time=19.6230 msec
     36364 bytes received: seq_n=8, time=20.3931 msec
     36464 bytes received: seq_n=9, time=20.2239 msec
    338365}}}
    339366
     
    344371
    345372For more information regarding the prototype design and updated status, visit the wiki page: https://mobilityfirst.orbit-lab.org/
    346