Changes between Version 5 and Version 6 of NewExperimentAPI


Ignore:
Timestamp:
Aug 13, 2013 2:13:40 PM (7 years ago)
Author:
Alefiya Hussain
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • NewExperimentAPI

    v5 v6  
    2121The experiment environment defines the set of
    2222resources required to configure a DETERLab experiment.
    23 It consists of three planes:
     23It consists of the three planes and
     24elements with different functional behaviors mapped onto them.
     25We discuss each in detail below.
     26
     27The experiment environment consists of three planes:
    2428
    2529* '''an experiment plane: '''
     
    2933  and their topological structure.
    3034  The functional behaviors are
    31   mapped onto the experiment nodes.
     35  mapped onto the experiment nodes.
     36  For example, an experiment may consist of background
     37  traffic generators including webserver and webclients,
     38  attack traffic generators, including botmasters and bots.
    3239  The structure is defined in the TopDL/ns-2
    3340  description file.
     
    3845   signalling commands to the experiment nodes.
    3946   In addition to the experiment nodes, other control-specific
    40    nodes such as an orchestrator and a bridge may also belong to the control plane.
     47   nodes such as an orchestrator and a bridge may also belong to the control     
     48   plane.
    4149   The topological structure of the control plane
    4250   is defined by the testbed or configured per experiment
    4351   in the TopDL/MesDL description file.
    44    The topology consists of directors, bridges, overlays, and orchestrators
     52   The topology consists of four types of elements.
     53   Namely, directors, bridges, overlays, and orchestrators.
    4554
    4655* '''a data plane: '''
     
    5362   is defined by the testbed or configured per experiment
    5463   in the description TopDL/MesDL file. 
    55    The topology consists of sensors, collector, aggregators and queriers
     64   The topology consists of four types of elements,
     65   namely, sensors, collector, aggregators and queriers.
    5666
    57 Each of the above plane may be combined
    58 due to resource constraints on the testbed.
     67
     68There are five types of properties that can be configured for
     69each experiment element:
     70
     71* '''process''':
     72   The property characterizes the ''computational capacity''
     73   of the element.
     74   A functional mapping of the behavior onto the element can impose
     75   requirement constraints, that is, a webserver requires at least 200Mhz
     76   of computational capacity.
     77   Computational capacity units can be specified in jiffies and clock speed.
     78   
     79
     80* ''' storeage''':
     81   This property characterizes the local ''persistent'' (and non--persistent)
     82   recording capacity of the element.
     83   A functional mapping of the behavior onto the element can impose
     84   different storage requirement constraints. For example, a router
     85   element in the experiment may not require any storage, whereas, a
     86   collector element may require a lot of storage capacity. 
     87
     88* '''network interface''':
     89   This property characterizes the cardinality and type of network interface
     90   on the experiment element. There may be more than one interface.
     91   Each interface has its own rate and delay characteristics.
     92   The functional mappings of the behavior onto the element can impose
     93   different interface requirements. For example, collectors may require
     94   a high bandwidth interface, core routers in an experiment topology
     95   may require many interfaces.
     96
     97* '''sense''':
     98     This property characterizes the types of stimulus the element can sense.
     99     For example, all network traffic, CPU load, heat.
     100     
     101     
     102* '''actuate''':
     103     This property characterizes the types of responses the element can implement.
     104     For example, bring down an interface, increase delay on a link,
     105     partition a network
     106
     107
     108Each experiment element has incoming and outgoing connections to one or more
     109experiment planes.
     110
    59111
    60112== Workflow ==