SFA for FEDERICA within the NOVI project

FEDERICA project was an experimental network infrastructure for trialing new networking technologies. Despite it ended in March 2011, most of the partners taking part in this project want to keep alive the spirit of the project and that’s why they provide their infrastructure belonging to FEDERICA to other projects where they are working. That happens in EC FP7 NOVI project, where part of the partners involved were part of FEDERICA.

NOVI aims to federate at the data, control, monitoring and provisioning planes of existing FI infrastructures. Initially, these platforms are PlanetLab Europe and FEDERICA. In order to do so, it has been decided to adapt FEDERICA infrastructure to SFA architecture. Slice-based Federation Architecture definition (SFA) is that it defines a control framework architecture that permits a federation of slice-based network substrate to interoperate. In other words, SFA defines a minimal set of interfaces and software system that allows different testbeds to federate. It is based in a set of software components that define a concrete architecture.

First of all it’s needed to understand the basic concepts it talks about:


SFA federation in PlanetLab

SFA federation in PlanetLab


  • Component is the primary building block of the SFA architecture.
  • Sliver is the virtualization of a component.
  • Components are grouped into aggregates. Each aggregate is controlled via an Aggregate Manager (AM).
  • If the AM contains only a single component, then it may be called a Component Manager (CM).
  • The AM/CM defines the operations available to user level services to manage the allocation of component resources to different users and their experiments
  • The Slice Manager (SM) is the component that decides which AM should be contacted. It acts as a proxy between users and AM’s.
  • The Registry (R) is the database where the SFA records and credentials are stored.
  • The Resource Specification (RSpec) describes a component in terms of the resources it possesses and constraints and dependencies on the allocation of those resources.
  • Slice is a group of slivers that only can be accessed by a group of users. Resources are acquired and consumed by slices.

So, what is being done in order to adapt FEDERICA to SFA? First of all, understanding what this means and which are the changes needed, and then making the consistent actions:

  • Adapt the RSpec, so network and compute resources can by expressed by it.
  • Offer the same API of calls that SFA, and adapt them to the FEDERICA Web Services. In other words, building a new AM for FEDERICA, so the federation with other facilities is possible as shown in the upper figure.
  • Collaboration with the SFA partners in order to try to take the most profit of their already existing work.  In addition, this collaboration could help them in the adaptation of SFA for new platforms.

It is being a lot of work, more than expected, but we are sure that we will finish doing a great job!


This entry was posted in Uncategorized and tagged , , , . Bookmark the permalink.