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

Timestamp:

Oct 15, 2014, 7:15:03 AM (11 years ago)

Author:

wontoniii

Comment:

—

Tutorials/oMF/tut1

@@ -51 +51 @@
 }}}
 
-
-
-{{{
-#!sh
-
-omf load -i 'mf-release-latest.ndz' -t system:topo:mf-group1
-}}}
-
-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:
-
-{{{
-#!sh
-omf load -i 'mf-release-latest.ndz' -t 'node1-1,node1-2,node1-3,node1-4'
-}}}
-
-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.
+From the console we will start by loading the Mobilityfirst image into the four nodes that have been assigned to you:
+
+{{{
+#!sh
+
+omf load -i 'mf-release-latest.ndz' -t system:topo:mf-groupX
+}}}
+
+'''system:topo:mf-groupX''' represents the group of 4 nodes and '''mf-groupX''' has to be replaced by the group id assigned to you.
+
+For example, '''mf-group1''' will load the image on nodes 'node1-1,node1-2,node2-1,node2-2'
+
+If the output of your console looks similar to:
+
+{{{
+#!sh
+
+INFO exp:  ----------------------------- 
+ INFO exp:  Imaging Process Done 
+ INFO exp:  4 nodes successfully imaged - Topology saved in '/tmp/pxe_slice-2014-10-15t02.10.16.594-04.00-topo-success.rb'
+ INFO exp:  ----------------------------- 
+ INFO EXPERIMENT_DONE: Event triggered. Starting the associated tasks.
+ INFO NodeHandler: 
+ INFO NodeHandler: Shutting down experiment, please wait...
+ INFO NodeHandler: 
+ INFO NodeHandler: Shutdown flag is set - Turning Off the resources
+ INFO run: Experiment pxe_slice-2014-10-15t02.10.16.594-04.00 finished after 1:50
+}}}
+
+your nodes have been imaged correctly.
 
 === Deploy Network ===
@@ -321 +335 @@
 {{{
 #!sh
-mfping -S <my-GUID>
-}}}
+mfping -s -m 102 -o 101
+}}}
+
+where "-s" specifies that the host is running as server, "-m" specifies the source guid and "-o" the destination one
 
 To run the mfping 'client'
@@ -328 +344 @@
 {{{
 #!sh
-mfping -C <my-GUID> <server-GUID> -i <interval_secs> -c <count>
-}}}
-
-You should see an out at the client similar to below:
-
-{{{
-#!sh
-
+mfping -c -m 101 -o 102 -n 10
+}}}
+
+If successfully executed, the client will display some information similar to the following snippet
+
+{{{
+#!sh
+
+root@node1-1:~# mfping -c -m 101 -o 102 -n 10
+64 bytes received: seq_n=0, time=25.1470 msec
+64 bytes received: seq_n=1, time=23.7070 msec
+64 bytes received: seq_n=2, time=20.0559 msec
+64 bytes received: seq_n=3, time=24.0371 msec
+64 bytes received: seq_n=4, time=23.1831 msec
+64 bytes received: seq_n=5, time=20.3069 msec
+64 bytes received: seq_n=6, time=24.1379 msec
+64 bytes received: seq_n=7, time=19.6230 msec
+64 bytes received: seq_n=8, time=20.3931 msec
+64 bytes received: seq_n=9, time=20.2239 msec
 }}}
 
@@ -344 +371 @@
 
 For more information regarding the prototype design and updated status, visit the wiki page: https://mobilityfirst.orbit-lab.org/
-