Differences From
Artifact [62be460f20]:
134 134 isolation and node stability.
135 135 - uses traffic control, filtering and anonymization to ensure network
136 136 stability, isolation and privacy (partialy implemented).
137 137 - The recovery device (not implemented) can force a remote hardware reboot of
138 138 the RD in case it hangs. It also helps with upgrade and recovery. *##*
139 139
140 140 * Experiments support
141 -# Axel: Turn around as of mail: from PoV of researcher: 1) testbed through API, choose nodes, 2) login OoB, 3) auto creation, 4) specific interfaces.
142 -Researchers can configure slivers with different types of network interfaces
143 -depending on the connectivity needs of experiments. For instance, to *##*
141 +These testbed and node architectures offer varied support for experiments. *##*
144 142
145 -- mimic a home PC: use the private interface, *##* which has L3 traffic
146 - forwarded using NAT to the CN but filtered to ensure network stability. *##*
147 -- implement a network service: create a public interface, *##* which has a CN
148 - address and L3 traffic routed directly to the CN but filtered to ensure
149 - network stability. *##*
150 -- experiment with routing algorithms: create an isolated interface, *##* which
151 - uses a VLAN on top of a direct interface. All L2 traffic is allowed, but
152 - only between other slivers of the same slice with isolated interfaces on the
153 - same physical link.
143 +- Researchers can query testbed management information via server and node
144 + APIs. This can help them implement external services to help monitor and
145 + choose the most appropriate nodes. *##*
146 +- Researchers can log into their running slivers using SSH out-of-band access
147 + against the node to run arbitrary programs. *##*
148 +- A researcher can use a sliver as a home PC with L3 traffic forwarded using
149 + NAT to the CN but filtered to ensure network stability. *##*
150 +- A researcher can offer a network service in a sliver by using a public
151 + interface, which has a CN address and L3 traffic routed directly to the CN
152 + but filtered to ensure network stability. *##*
153 +- Routing experiments can use an isolated interface in a sliver, which uses a
154 + VLAN on top of a direct interface. All L2 traffic is allowed, but only
155 + between other slivers of the same slice with isolated interfaces on the same
156 + physical link. *##*
154 157
155 158 These were demonstrated with BitTorrent and mesh routing experiments at IEEE
156 159 P2P'12 Conference. *##* Future support is also planned for experiments that:
157 160
158 -- analyze traffic: create a passive interface *##* to capture traffic on a
159 - direct interface, which is filtered and anonymized to ensure network
160 - privacy. *##*
161 -- perform low-level testing: *##* the sliver is given free raw access to a
162 - direct interface. For privacy, isolation and stability reasons this should
163 - only be allowed in exceptional occasions. *##*
161 +- analyze traffic: using a passive interface to capture traffic on a direct
162 + interface, which is filtered and anonymized to ensure network privacy. *##*
163 +- perform low-level testing: the sliver is given free raw access to a direct
164 + interface. For privacy, isolation and stability reasons this should only be
165 + allowed in exceptional occasions. *##*
164 166
165 -Besides experiments run in slices, researchers will soon be able to collect
166 -link quality and bandwidth usage measurements of all RDs' interfaces through
167 -the DLEP protocol. *##*
168 -
169 -Moreover, the server and nodes will soon publish management information
170 -through an API that can be used to study the testbed itself, or to implement
171 -external services like node monitoring and selection.
167 +Also, researchers will soon be able to collect link quality and bandwidth
168 +usage measurements of all RDs' interfaces through the DLEP protocol. *##*
172 169
173 170 ** An example experiment
174 171 to show how the testbed works. We'll create two slivers which ping each
175 172 other. *##*
176 173
177 174 1. The researcher first contacts the server and registers a slice description
178 175 which specifies a template for slivers (e.g. Debian Squeeze) and includes