Changes between Version 5 and Version 6 of NewExperimentAPI

Timestamp:

Aug 13, 2013 2:13:40 PM (11 years ago)

Author:

Alefiya Hussain

Comment:

--

NewExperimentAPI

@@ -21 +21 @@
 The experiment environment defines the set of 
 resources required to configure a DETERLab experiment. 
-It consists of three planes: 
+It consists of the three planes and 
+elements with different functional behaviors mapped onto them. 
+We discuss each in detail below. 
+
+The experiment environment consists of three planes: 
 
 * '''an experiment plane: ''' 
@@ -29 +33 @@
   and their topological structure. 
   The functional behaviors are 
-  mapped onto the experiment nodes.
+  mapped onto the experiment nodes. 
+  For example, an experiment may consist of background
+  traffic generators including webserver and webclients, 
+  attack traffic generators, including botmasters and bots. 
   The structure is defined in the TopDL/ns-2 
   description file.
@@ -38 +45 @@
    signalling commands to the experiment nodes. 
    In addition to the experiment nodes, other control-specific 
-   nodes such as an orchestrator and a bridge may also belong to the control plane. 
+   nodes such as an orchestrator and a bridge may also belong to the control     
+   plane. 
    The topological structure of the control plane 
    is defined by the testbed or configured per experiment
    in the TopDL/MesDL description file.
-   The topology consists of directors, bridges, overlays, and orchestrators 
+   The topology consists of four types of elements. 
+   Namely, directors, bridges, overlays, and orchestrators. 
 
 * '''a data plane: '''
@@ -53 +62 @@
    is defined by the testbed or configured per experiment
    in the description TopDL/MesDL file.  
-   The topology consists of sensors, collector, aggregators and queriers 
+   The topology consists of four types of elements, 
+   namely, sensors, collector, aggregators and queriers. 
 
-Each of the above plane may be combined 
-due to resource constraints on the testbed. 
+
+There are five types of properties that can be configured for 
+each experiment element: 
+
+* '''process''': 
+   The property characterizes the ''computational capacity'' 
+   of the element. 
+   A functional mapping of the behavior onto the element can impose 
+   requirement constraints, that is, a webserver requires at least 200Mhz 
+   of computational capacity. 
+   Computational capacity units can be specified in jiffies and clock speed. 
+   
+
+* ''' storeage''':
+   This property characterizes the local ''persistent'' (and non--persistent) 
+   recording capacity of the element. 
+   A functional mapping of the behavior onto the element can impose 
+   different storage requirement constraints. For example, a router 
+   element in the experiment may not require any storage, whereas, a 
+   collector element may require a lot of storage capacity.  
+
+* '''network interface''':
+   This property characterizes the cardinality and type of network interface 
+   on the experiment element. There may be more than one interface. 
+   Each interface has its own rate and delay characteristics. 
+   The functional mappings of the behavior onto the element can impose 
+   different interface requirements. For example, collectors may require 
+   a high bandwidth interface, core routers in an experiment topology 
+   may require many interfaces. 
+
+* '''sense''':
+     This property characterizes the types of stimulus the element can sense. 
+     For example, all network traffic, CPU load, heat. 
+     
+     
+* '''actuate''': 
+     This property characterizes the types of responses the element can implement. 
+     For example, bring down an interface, increase delay on a link, 
+     partition a network 
+
+
+Each experiment element has incoming and outgoing connections to one or more 
+experiment planes. 
+
 
 == Workflow ==