User Tools

Site Tools


Community-Lab architecture overview

This section describes the architecture developed by the CONFINE Project. It applies to all testbeds using CONFINE software.

Through this page we will use some concepts that the reader should be familiar with. For completeness, we provide here a short description of the most relevant ones, but the reader can always check the glossary for further details.

A shown in figure 1, Community-Lab works with nodes which are usually composed by two different types of devices to ease the management of the testbed while being part of a community network:

  • Research devices (RD) or testbed nodes are the devices deployed by CONFINE that run the applications.
  • Community devices (CD) or community nodes are devices connected to the community network (CN), participating on every mechanism required by it (routing protocols, database registration, etc.). These community nodes are integral parts of a CN and form the actual network infrastructure by relaying other nodes’ traffic while respecting the rules and peering agreements of the CN. The community nodes and the network infrastructure itself is managed by community members. Research devices are connected to the community network through a community device, but they do not have to adapt to the requirements of the community network.

Testbed nodes can run applications concurrently. This is achieved by means of Linux Containers (LXC): every application will indicate a set of nodes where it wants to run, and testbed nodes will create a LXC container for the application. Using PlanetLab terminology, we call each of those containers a sliver and the set of slivers belonging to an application is called a slice.

Nodes, slices, users and so on are managed through a testbed registry, which can be reached via the Community-Lab controller.

Fig. 1: Community-Lab general architecture view

intro/community-lab/info.txt · Last modified: 2014/07/01 15:05 by ivilata