Changes between Initial Version and Version 1 of GEC21Agenda/LabWiki/ModuleA/Execute

Timestamp:

10/15/14 13:06:24 (10 years ago)

Author:

divyashri.bhat@gmail.com

Comment:

--

GEC21Agenda/LabWiki/ModuleA/Execute

@@ +1 @@
+= Module A Execute Experiment =
+
+== 3. Instrument your Application using !LabWiki ==
+
+In this part of Module A you will learn how you can use !LabWiki to execute an experiment on the slice you 
+reserved in the [wiki:GEC21Agenda/LabWiki/ModuleA/DesignSetup previous step].
+
+=== 3.1 Design and Execute measurement in !LabWiki ===
+
+
+=== 3.1.1. The "Plan" Window ===
+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 "GEC21learningswitch" in the field and then select "GEC21learningswitch.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 ===
+
+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.
+
+For reference, we show the experiment script here:
+{{{
+#!ruby
+defProperty('source1', "nodea-dbhattesteg", "ID of a resource")
+defProperty('source2', "switch-dbhattesteg", "ID of a resource")
+
+
+defProperty('sinkaddr12', '192.168.1.7', "Ping destination address")
+defProperty('sinkaddr13', '192.168.1.8', "Ping destination address")
+
+defProperty('sinkaddr21', '192.168.1.9', "Ping destination address")
+
+
+defApplication('ping') do |app|
+  app.description = 'Simple Definition for the ping-oml2 application'
+  # Define the path to the binary executable for this application
+  app.binary_path = '/usr/local/bin/ping-oml2'
+  # Define the configurable parameters for this application
+  # For example if target is set to foo.com and count is set to 2, then the 
+  # application will be started with the command line:
+  # /usr/bin/ping-oml2 -a foo.com -c 2
+  app.defProperty('target', 'Address to ping', '-a', {:type => :string})
+  app.defProperty('count', 'Number of times to ping', '-c', {:type => :integer})
+  # Define the OML2 measurement point that this application provides.
+  # Here we have only one measurement point (MP) named 'ping'. Each measurement
+  # sample from this MP will be composed of a 4-tuples (addr,ttl,rtt,rtt_unit)
+  app.defMeasurement('ping') do |m|
+    m.defMetric('dest_addr',:string)
+    m.defMetric('ttl',:uint32)
+    m.defMetric('rtt',:double)
+    m.defMetric('rtt_unit',:string)
+  end
+end
+
+defApplication('trema') do |app|
+  app.description = 'This app runs trema from command line'
+  app.binary_path = '/bin/sh /root/ovs-setup2.sh'
+end
+defGroup('Source2', property.source2) do |node|
+  node.addApplication("trema")
+end
+defGroup('Source1', property.source1) do |node|
+  node.addApplication("ping") do |app|
+    app.setProperty('target', property.sinkaddr12)
+    app.setProperty('count', 30)
+    #app.setProperty('interval', 1)
+    app.measure('ping', :samples => 1)
+  end
+  node.addApplication("ping") do |app|
+    app.setProperty('target', property.sinkaddr13)
+    app.setProperty('count', 30)
+    #app.setProperty('interval', 1)
+    app.measure('ping', :samples => 1)
+  end
+   node.addApplication("ping") do |app|
+    app.setProperty('target', property.sinkaddr21)
+    app.setProperty('count', 30)
+    #app.setProperty('interval', 1)
+    app.measure('ping', :samples => 1)
+  end
+end
+
+
+onEvent(:ALL_UP_AND_INSTALLED) do |event|
+  info "Starting the ping"
+  after 1 do
+    group('Source2').startApplications
+  end
+  after 30 do
+    group('Source1').startApplications
+  end
+  after 80 do
+    info "Stopping the ping"
+    allGroups.stopApplications
+    Experiment.done
+  end
+end
+
+defGraph 'RTT' do |g|
+  g.ms('ping').select(:oml_seq, :dest_addr, :rtt) 
+  g.caption "RTT of received packets."
+  g.type 'line_chart3'
+  g.mapping :x_axis => :oml_seq, :y_axis => :rtt, :group_by => :dest_addr
+  g.xaxis :legend => 'oml_seq'
+  g.yaxis :legend => 'rtt', :ticks => {:format => 's'}
+end
+
+}}}
+
+=== 3.1.3 Start your application from !LabWiki ===
+
+To start your experiment, simply drag the icon that is to the left of the file name (see figure below) from the middle (Prepare) to the right (Execute) window.
+That will automatically fill out the experiment relevant information in this window
+ Explanation of the fields in the Execute window:
+
+* name: In this field you specify the name of your experiment.
+
+* project: This pull-down menu list all the projects you are currently a member of. Select the project that contains the slice you want to run your experiment on.
+
+* experiment context: With the context you can specify a certain set of experiments. E.g., a series of experiments you run under a certain set of startup parameters. This field is not mandatory and only necessary if you would like to save your experiment data to view later.
+
+* slice: This pull down menu lists all slice that have been created under "project". Select the slice you would like to run your experiment on.
+
+*Change source1 and source2 fields to include your slice name similar to nodea-<slicename>
+
+Then, start the actual experiment by clicking on the "Start Experiment" button.
+
+[[Image(http://groups.geni.net/geni/raw-attachment/wiki/GEC20Agenda/LabWiki/ModuleA/Execute/LW-execute.pngq, 40%)]]
+
+
+=== 3.1.4 During experiment execution ===
+
+After pressing the "Start" button, the Execute window will change and start showing status information about your experiment.
+The figure below gives an example for the Execute window during experiment execution.
+
+[[Image(http://groups.geni.net/geni/raw-attachment/wiki/GEC20Agenda/LabWiki/ModuleA/Execute/LW-executing.png, 40%)]]
+
+Now the window lists experiment properties, one or several live graphs (if they have been specified in the OEDL script), and logging information. The latter would be a good starting point for trouble shooting, should your experiment not run as expected.
+
+Depending on the status of your resources and experiments, you will see one of the following statuses at the top of the Execute window:
+ * Pending - This is the first state of your experiment where the job scheduler adds it to the run queue. This status would remain for the first few seconds before it changes to Running or Failed
+ * Running - This status appears when your experiment starts running. If it fails for one or more reasons, a Failed status will appear instead
+ * Aborted - When you click on "Stop Experiment" at the top-left corner of the Execute window, the status changes to aborted
+ * Finished - When your experiment is done, you will see this status
+
+= [wiki:GEC21Agenda/LabWiki/ModuleA/Finish Next: Finish] =
+= [wiki:GEC21Agenda/LabWiki/ModuleA/DesignSetup Design] =