109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
|
- Each node is able to run several experiments simultaneously.
- An experiment runs in a given node as a sliver which holds a share of its
resources (CPU, memory, disk, bandwidth, interfaces…).
- Finally, related slivers are grouped in a slice for management purposes.
- All these concepts are inspired in PlanetLab. *##*
** Node architecture
# Axel: More stress on node itself.
# Ivan: Don't zoom!!
allows the realization of these concepts. *##* A node consists of a CD, a RD
and a rD connected to the same wired local network. *##*
- The community device
- Completely normal CN device, so existing ones can be used.
- routes traffic between the CN and the local network (which runs no routing
protocol). *##*
- The research device
- Usually more powerful than CD, since experiments run here.
- Separating the RD from the CD minimizes tampering with CN infrastructure.
- Also experiments can't crash CN devices.
- runs the versatile, light & free OpenWrt distro, customized by CONFINE. *##*
- Slivers are implemented as lightweight Linux containers.
- So researchers get root access to a familiar environment. *##*
- provides direct interfaces to allow low-level interaction of experiments
with the CN bypassing the CD. *##*
- runs CONFINE control software
- uses LXC tools to manage containers and enforce resource limits,
isolation and node stability.
- uses traffic control, filtering and anonymization to ensure network
stability, isolation and privacy (partialy implemented). *##*
- The recovery device (not implemented) can force a remote hardware reboot of
the RD in case it hangs. It also helps with upgrade and recovery. *##*
* Experiments support
# 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.
Researchers can configure slivers with different types of network interfaces
depending on the connectivity needs of experiments. For instance, to *##*
|
|
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
|
- Each node is able to run several experiments simultaneously.
- An experiment runs in a given node as a sliver which holds a share of its
resources (CPU, memory, disk, bandwidth, interfaces…).
- Finally, related slivers are grouped in a slice for management purposes.
- All these concepts are inspired in PlanetLab. *##*
** Node architecture
allows the realization of these concepts. *##* A node consists of a CD, a RD
and a rD connected to the same wired local network.
- The community device
- Completely normal CN device, so existing ones can be used.
- routes traffic between the CN and the local network (which runs no routing
protocol).
- The research device
- Usually more powerful than CD, since experiments run here.
- Separating the RD from the CD minimizes tampering with CN infrastructure.
- Also experiments can't crash CN devices.
- runs the versatile, light & free OpenWrt distro, customized by CONFINE.
- Slivers are implemented as lightweight Linux containers.
- So researchers get root access to a familiar environment.
- provides direct interfaces to allow low-level interaction of experiments
with the CN bypassing the CD.
- runs CONFINE control software
- uses LXC tools to manage containers and enforce resource limits,
isolation and node stability.
- uses traffic control, filtering and anonymization to ensure network
stability, isolation and privacy (partialy implemented).
- The recovery device (not implemented) can force a remote hardware reboot of
the RD in case it hangs. It also helps with upgrade and recovery. *##*
* Experiments support
# 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.
Researchers can configure slivers with different types of network interfaces
depending on the connectivity needs of experiments. For instance, to *##*
|