<?xml version="1.0" encoding="utf-8"?><!DOCTYPE article  PUBLIC '-//OASIS//DTD DocBook XML V4.4//EN'  'http://www.docbook.org/xml/4.4/docbookx.dtd'><article><articleinfo><title>CONFLATE</title><revhistory><revision><revnumber>5</revnumber><date>2014-04-28 13:41:16</date><authorinitials>ClauzClauz</authorinitials></revision><revision><revnumber>4</revnumber><date>2014-04-28 13:39:45</date><authorinitials>ClauzClauz</authorinitials></revision><revision><revnumber>3</revnumber><date>2014-04-28 13:29:40</date><authorinitials>ClauzClauz</authorinitials></revision><revision><revnumber>2</revnumber><date>2014-03-18 12:26:00</date><authorinitials>ClauzClauz</authorinitials></revision><revision><revnumber>1</revnumber><date>2014-03-18 10:51:17</date><authorinitials>ClauzClauz</authorinitials></revision></revhistory></articleinfo><section><title>CONFINE extension towards OpenFlow experimentation: infrastructure, software and demonstrations (CONFLATE)</title><para>Questa pagina (in inglese) descrive l'estensione del testbed <ulink url="http://wiki.confine-project.eu/usage:start">CommunityLab</ulink> di <ulink url="http://confine-project.eu/">CONFINE</ulink> dentro ninux. </para><para>This page describes the <ulink url="http://wiki.confine-project.eu/usage:start">CommunityLab</ulink> extension from the <ulink url="http://confine-project.eu/">CONFINE</ulink> project in ninux. </para><para><inlinemediaobject><imageobject><imagedata fileref="http://www.nnx.me//CONFLATE?action=AttachFile&amp;do=get&amp;target=testbed-architecture_1.png" width="600px"/></imageobject><textobject><phrase>testbed-architecture_1.png</phrase></textobject></inlinemediaobject> </para><section><title>Abstract</title><para>The <emphasis role="strong">CONFLATE</emphasis> project proposes to extend the <ulink url="http://www.nnx.me/CONFLATE/CommunityLab#">CommunityLab</ulink> testbed, from the <emphasis role="strong"><ulink url="http://confine-project.eu/">CONFINE</ulink></emphasis> project, in <emphasis role="strong">two dimensions</emphasis>: infrastructural and functional. The <emphasis role="strong">infrastructural extension</emphasis> is the <emphasis role="strong">deployment of new Research Devices within the Ninux.org community network</emphasis> in Italy. The <emphasis role="strong">functional extension</emphasis> is the deployment of an <ulink url="http://www.nnx.me/CONFLATE/OpenFlow#">OpenFlow</ulink> eXperimental facility (OFX) within <ulink url="http://www.nnx.me/CONFLATE/CommunityLab#">CommunityLab</ulink>, which allows users/researchers to carry out Software Defined Networking (SDN) experiments based on the <ulink url="http://www.nnx.me/CONFLATE/OpenFlow#">OpenFlow</ulink> standard. With the OFX extension, <ulink url="http://www.nnx.me/CONFLATE/CommunityLab#">CommunityLab</ulink> will be the first wireless testbed which will enable <ulink url="http://www.nnx.me/CONFLATE/OpenFlow#">OpenFlow</ulink> experiments within a large scale production network. </para><para><inlinemediaobject><imageobject><imagedata fileref="http://www.nnx.me//CONFLATE?action=AttachFile&amp;do=get&amp;target=ofx1.png" width="400px"/></imageobject><textobject><phrase>ofx1.png</phrase></textobject></inlinemediaobject> </para><para>OFX makes possible focused experiments on all <ulink url="http://www.nnx.me/CONFLATE/OpenFlow#">OpenFlow</ulink> key aspects: the switch, the controller, and the controller applications (i.e. switching rules). A researcher can deploy and test off- the-shelf or novel <ulink url="http://www.nnx.me/CONFLATE/OpenFlow#">OpenFlow</ulink> switches, controllers and controller applications. And to simplify the realization of focused experiments, the researcher disposes of a pre-installed OFX-toolkit formed by: an <ulink url="http://www.nnx.me/CONFLATE/OpenFlow#">OpenFlow</ulink> switch (i.e. Open vSwitch) per virtual machine; an instance of an <ulink url="http://www.nnx.me/CONFLATE/OpenFlow#">OpenFlow</ulink> controller on a dedicated server of the <ulink url="http://www.nnx.me/CONFLATE/CommunityLab#">CommunityLab</ulink>; and a set of default controller applications, like L2/L3 Learning etc. The different items of the toolkit can be used or not, depending on the specific focus of the experiment. </para><para><ulink url="http://www.nnx.me/CONFLATE/OpenFlow#">OpenFlow</ulink> requires a layer 2 network and OFX provides a “L2 Virtual Topology Deployer” tool, which automatically deploys an arbitrary layer 2 topology among the virtual machines of the researcher.  Obviously, this tool is also re-usable by other experimenters contributing to extend the <ulink url="http://www.nnx.me/CONFLATE/CommunityLab#">CommunityLab</ulink> experimental facility towards different kinds of layer 2 experiments, beyond <ulink url="http://www.nnx.me/CONFLATE/OpenFlow#">OpenFlow</ulink>. The layer topology is formed by Ethernet tunnels, realized by the emerging network virtualization technology, namely Virtual Extensive LAN (VXLAN). The tunneling approach makes possible a pervasive introduction of the OFX facility in <ulink url="http://www.nnx.me/CONFLATE/CommunityLab#">CommunityLab</ulink>, since it makes the OFX platform independent from the specific deployment of Research Devices (i.e., directly connected or connected through non- CONFINE devices) and from the underlying IP routing protocol used in the Community Networks (e.g.  OLSR, BGP, etc.). Indeed, <ulink url="http://www.nnx.me/CONFLATE/CommunityLab#">CommunityLab</ulink> is rather heterogeneous with respect to these two aspects, therefore being the new facility independent from them avoids deployment issues. </para><para><inlinemediaobject><imageobject><imagedata fileref="http://www.nnx.me//CONFLATE?action=AttachFile&amp;do=get&amp;target=ofx2.png" width="600px"/></imageobject><textobject><phrase>ofx2.png</phrase></textobject></inlinemediaobject> </para><para>To test the effectiveness of the proposed extensions, CONFLATE uses the new Research Devices of Ninux.org to deploy a simple (but practical) <ulink url="http://www.nnx.me/CONFLATE/OpenFlow#">OpenFlow</ulink> based MPEG DASH Live Video Streaming service for real users of Ninux.org. Among the plethora of possible test applications, CONFLATE selects the video streaming since it is actually one of the killer applications in Community Networks,is not (yet) available in Ninux.org, and can provide an hands-on user guide about how to use the OFX facility to setup <ulink url="http://www.nnx.me/CONFLATE/OpenFlow#">OpenFlow</ulink> experiments that involve real users. </para><para><inlinemediaobject><imageobject><imagedata fileref="http://www.nnx.me//CONFLATE?action=AttachFile&amp;do=get&amp;target=ofx3.png" width="600px"/></imageobject><textobject><phrase>ofx3.png</phrase></textobject></inlinemediaobject> </para><para>The CONFLATE consortium is formed by the CNIT group at University of Rome “Tor Vergata” and by the Unidata company (SME). Key persons of the Ninux.org community (which is an informal group of volunteers) are involved in the project under the umbrella of CNIT and Unidata. CNIT has a well-established experience in <ulink url="http://www.nnx.me/CONFLATE/OpenFlow#">OpenFlow</ulink> experimentation gained by the participation to EU FP7 projects like: OFELIA, <ulink url="http://www.nnx.me/CONFLATE/OpenLab#">OpenLab</ulink> and GEANT GN3plus. Hence, the CONFLATE project would establish a trait d’union between CONFINE and these projects. Unidata is an Integrated Communications Provider which offers fiber and wireless Internet access in Rome, and also cloud computing services. Unidata has an on-the-field experience in network deployment and virtualization systems. </para></section><section><title>See also</title><itemizedlist><listitem><para><ulink url="http://wiki.confine-project.eu/experiments:opencall2?s[]=conflate#confine_extension_towards_openflow_experimentationinfrastructure_software_and_demonstrations_conflate_cnit_unidata">CONFLATE at the CONFINE Wiki</ulink> </para></listitem><listitem><para><ulink url="http://blog.ninux.org/tag/confine"/> </para></listitem></itemizedlist></section></section></article>