Community-Lab introduction

Diff
Login

Differences From Artifact [d327a8d36a]:

To Artifact [a8f7ed4cc8]:


184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199

200
201
202
203

204
205

206
207
208
209
210
211
212
213
214
215
216
   programs query sliver properties to decide their behaviour.
8. Researchers interact straight with containers if needed (e.g. via SSH) and
   collect results from them.
9. When finished, the researcher tells the server to deactivate and
   deinstantiate the slice.
10. Nodes get the instructions and they stop and remove containers.

* Community-Lab integration in existing community networks
# CN diagram (buildings and cloud).
A typical CN looks like this, with most nodes linked using cheap and
ubiquitous WiFi technology (and less frequently Ethernet, optical fiber or
others).  The CONFINE project follows three strategies taking into account
that CNs are production networks with distributed ownership:

# CN diagram extended with CONFINE devices (hover over interesting part).
- Take an existing node owned by CN members, CONFINE provides a RD and

  connects it via Ethernet to the CD.  Experiments are restricted to the
  application layer unless the node owner allows the RD to include a direct
  interface (i.e. antenna).
- Extend the CN with complete nodes, CONFINE provides both the CD and the RD

  and uses a CN member's location.  All but low-level experiments are possible
  using direct interfaces.

- Set up a physically separated cloud of nodes, CONFINE extends the CN with a
  full installation of connected nodes at a site controlled by a partner
  (e.g. campus).  All kinds of experiments are possible using direct
  interfaces.  Users are warned about the experimental nature of the network.

* Recap

- Community networks are an emerging field to provide citizens with
  connectivity in a sustainable and distributed manner in which the owners of
  the networks are the users themselves.
- Research on this field is necessary to support CNs' growth while improving







|

|
|
<
<


<
>
|
|
<
<
>
|
<
>
|
|
|
|







184
185
186
187
188
189
190
191
192
193
194


195
196

197
198
199


200
201

202
203
204
205
206
207
208
209
210
211
212
213
   programs query sliver properties to decide their behaviour.
8. Researchers interact straight with containers if needed (e.g. via SSH) and
   collect results from them.
9. When finished, the researcher tells the server to deactivate and
   deinstantiate the slice.
10. Nodes get the instructions and they stop and remove containers.

* Cooperation between community networks and Community-Lab
# CN diagram (buildings and cloud).
There are different ways.  Given a typical CN like this, with most nodes
linked using cheap and ubiquitous WiFi technology:



# CN diagram extended with CONFINE devices (hover over interesting part).

- CN members can provide an existing CD and let CONFINE connect a RD to it via
  Ethernet.  Experiments are restricted to the application layer unless the
  node owner allows the RD to include a direct interface (i.e. antenna).


- CN members can provide a location and let CONFINE set up a complete node
  there (CD and RD).  All but low-level experiments are possible using direct

  interfaces.  In this way CONFINE helps extend the CN.
- CONFINE can also extend the CN by setting up a physically separated cloud of
  connected nodes at a site controlled by a partner (e.g. campus).  All kinds
  of experiments are possible using direct interfaces.  Users are warned about
  the experimental nature of the network.

* Recap

- Community networks are an emerging field to provide citizens with
  connectivity in a sustainable and distributed manner in which the owners of
  the networks are the users themselves.
- Research on this field is necessary to support CNs' growth while improving