|Components||testbed server, testbed node|
Once the slice is started, the experimenter should be able to start/control/stop the experiment. This means executing commands to start applications, trigger events (failures), etc.
Assuming a slice is configured (resources are allocated), slivers are active and thus ready for launching an experiment.
This requirement is about the necessary steps to control/coordinate the life cycle of an experiment (start, stop, collect results, cleanup) involving any number of slivers.
We can borrow most of the terminology from PlanetLab if not suggested otherwise.
Researchers may want to manage its experiment in different ways depending on the type of experiment, the type of software used, their preferences regarding preferences on automation or detailed control, etc.
What services/hooks should be included in the testbed management system to support these tools (e.g. a daemon may be required to run at each slice)
Confine is quite similar to Planetlab but over a set of nodes inside community networks.