BEACON's Federated SDN

This blog post by OpenNebula Systems, outlines the features of the Federated SDN in BEACON and how it is structured.

BEACON is all about federating networks across clouds infrastructures securely. The Federated SDN is the software component that allows to build a Federated Network by aggregating two or more Federated Network Segments. It features an API to allow for Federated Network definitions, and uses adapters to talk to the federation agents APIs in different cloud infrastructures as well as to the Cloud Management Platforms (CMP). It is in charge of cross site networking, managing federated networks, and as such will address the following functionality in the first cycle. This component addresses the "Management of L2 overlays" software requirement of the project. d4-1-scientific-report-wp4-a  

This component features a REST interface to expose the functionality of the core component, which manages pools for the different data objects that represent the networking infrastructure that federates. A database is used to persist the data moel, and a well defined API allows the interaction between the Federated SDN core with the underlying cloud by the use of different adapters for OpenStack and OpenNebula based infrastructures. A high level view of this component architecture is depicted in the following figure.d4-1-scientific-report-wp4-a-1  

The Federated SDN features four first class data citizens, the federated network and federated segment objects, the tenant representation and the different cloud sites abstractions. Also, to interact with the different clouds that needs to be federated at the network level, the Federated SDN features cloud adapters. Initially two adapters, OpenNebula and OpenStack, have been developed. Each adapter is composed of a set of scripts that receive parameters from standard input and return results with standard output.