Changes between Version 1 and Version 2 of GEC22Agenda/LabWiki/ModuleA/Execute

Timestamp:

03/09/15 14:06:55 (9 years ago)

Author:

eswer18@gmail.com

Comment:

--

GEC22Agenda/LabWiki/ModuleA/Execute

@@ -12 +12 @@
 To get started point your browser to [http://labwiki.casa.umass.edu]. Labwiki has three major windows. We will focus on the leftmost window first. This is the "Planning" window in which you document your experiment. (This is somewhat the equivalent of an electronic lab journal.) Documents are written in [http://daringfireball.net/projects/markdown/ Markdown].
 
-At the top of that window is a text field which you can use to search for existing MD scripts. Type "GEC21-learningswitch" in the field and then select "GEC21-learningswitch.md" from the list of files that are offered. This document has some information on the experiment that will be performed in Module A of the tutorial.
+At the top of that window is a text field which you can use to search for existing MD scripts. Type "GEC22-learningswitch" in the field and then select "GEC22-learningswitch.md" from the list of files that are offered. This document has some information on the experiment that will be performed in Module A of the tutorial.
 
 === 3.1.2 The "Prepare" Window ===
@@ -18 +18 @@
 The "Prepare" (middle) window allows you to define your experiment through and [http://mytestbed.net/projects/omf/wiki/OMF_Main_Page OMF] experiment script specified in [http://mytestbed.net/projects/omf6/wiki/OEDLOMF6 OMF Experiment Description Language] (OEDL).
 
-At the top of that window is a text field which you can use to search for existing OEDL scripts. Type "GEC21" in the field and then select "GEC21-learningswitch.oedl" from the list of files that are offered. This shows the experiment script in the field below.
+At the top of that window is a text field which you can use to search for existing OEDL scripts. Type "GEC22" in the field and then select "GEC22-learningswitch.oedl" from the list of files that are offered. This shows the experiment script in the field below.
 
 For reference, we show the experiment script here:
@@ -24 +24 @@
 #!ruby
 
-defProperty('resource1', "nodea", "ID of a resource")
-defProperty('resource2', "switch", "ID of a resource")
+defProperty('source1', "nodea-learningswitch", "ID of a resource")
+defProperty('source2', "switch-learningswitch", "ID of a resource")
 
 
@@ -32 +32 @@
 
 defProperty('sinkaddr21', '192.168.1.9', "Ping destination address")
-
+defProperty('sinkaddr11', '192.168.1.6', "Ping destination address")
+peak_list = []
 
 defApplication('ping') do |app|
@@ -59 +60 @@
   app.binary_path = '/bin/sh /root/ovs-setup2.sh'
 end
-defGroup('Source2', property.resource2) do |node|
+defGroup('Source2', property.source2) do |node|
   node.addApplication("trema")
 end
-defGroup('Source1', property.resource1) do |node|
+defGroup('Source1', property.source1) do |node|
   node.addApplication("ping") do |app|
     app.setProperty('target', property.sinkaddr12)
@@ -83 +84 @@
 end
 
+defGroup('Source3', property.source1) do |node|
+  node.addApplication("ping") do |app|
+    app.setProperty('target', property.sinkaddr11)
+    app.setProperty('count', 30)
+    #app.setProperty('interval', 1)
+    app.measure('ping', :samples => 1)
+  end
+end
+
+defEvent(:MY_EVENT, every: 0.5) do
+# Query for some measurements...
+  # returns an array where each element is a hash representing a row from the DB
+  query = ms('ping').select { [ :remote] }
+  data = defQuery(query)
+  # Alternatively the above line could also be:
+  # data = defQuery('select oml_ts_client, value from signalgen_sin')
+  #
+  # Also if you want to rename 'oml_ts_client' to 'ts'
+  # query = ms('sin').select { [ oml_ts_client.as(:ts), :value ] } 
+  # data = defQuery('select oml_ts_client as ts, value from signalgen_sin')
+
+  triggered = false
+  if !data.nil? && !(last_row = data.pop).nil? # Make sure we have some data
+    next if peak_list.include?(last_row[:remote]) # Do nothing if we have seen this sample before
+    if !peak_list.include?(last_row[:remote])
+      peak_list << last_row[:remote] # record that sample, so we dont trigger on it again
+    end
+    if peak_list.include?('192.168.1.9')&&peak_list.include?('192.168.1.7')&&peak_list.include?('192.168.1.8')
+      
+      triggered = true
+    end
+  end
+  triggered
+end
+onEvent :MY_EVENT do
+  #group('switch').exec("ping www.google.com")
+  group('Source3').startApplications
+end
 
 onEvent(:ALL_UP_AND_INSTALLED) do |event|
@@ -107 +146 @@
   g.yaxis :legend => 'rtt', :ticks => {:format => 's'}
 end
+
 
 }}}
@@ -146 +186 @@
  * Finished - When your experiment is done, you will see this status
 
-= [wiki:GEC21Agenda/LabWiki/ModuleA/Finish Next: Finish] =
-= [wiki:GEC21Agenda/LabWiki/ModuleA/DesignSetup Design] =
+== Note to the Instructors ==
+
+* Students can be asked to implement a particular functionality of the OpenFlow controller. A template should be given to them[[BR]]
+
+* LabWiki has a new feature that enables the instructor to auto-grade the students' experiments. LabWiki allows people to write user-defined event, which is triggered upon an  
+experiment-generated measurements reaching a specific value. In the above script, the event will be triggered when Node A is able to ping all the other nodes in the topology. It will trigger a ping event to itself on Node A. In this way, you can say that the experiment is run successfully if the Ping on Node A is seen on the graph
+
+= [wiki:GEC22Agenda/LabWiki/ModuleA/Finish Next: Finish] =
+= [wiki:GEC22Agenda/LabWiki/ModuleA/DesignSetup Design] =