Changes between Version 2 and Version 3 of FeddPubs

Timestamp:

Oct 25, 2008 8:02:38 AM (16 years ago)

Author:

faber

Comment:

--

FeddPubs

@@ -12 +12 @@
 For the system implementers the centerpiece of the federation system is the federator. It takes input from experimenters or their tools and creates an experimental environment split across federant testbeds. Specifically, the federator decomposes an experimenter's annotated topology into federable sub-experiments, acquires access to appropriate federants, embeds the sub-experiments in federants, and then connects them into a shared environment. The following figure illustrates this architecture.
 
-[[Image(fed_arch_fig.png)]]
+[[Image(Fed_arch_fig.png)]]
 
 The architecture is partitioned to separate concerns of the various players. The partitioning of the experiment into pieces suitable to federation depends on the nature of the experiment.  This split must be guided by the experimenter using knowledge of the resources provided by the federation system. For example, an experiment used to study throughput of a new protocol must be aware which links are inside a testbed and completely controlled and which are not, to ensure that the unpredictable link performance does not invalidate the results. Collaborative or adversarial experiments will divide along the lines of visibility and testbed administrative boundaries.