1 / 27

CONVERGENCE KO Meeting

EXPRESS: Implementing an SDN infrastructure over a federation of testbeds (experiment within the OpenLab project). CONVERGENCE KO Meeting. Stefano Salsano

mada
Télécharger la présentation

CONVERGENCE KO Meeting

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EXPRESS: Implementing an SDN infrastructure over a federation of testbeds(experiment within the OpenLab project) CONVERGENCE KO Meeting Stefano Salsano and the EXPRESS team: Giuseppe Siracusano, Federico Griscioli, Pier Luigi Ventre, Claudio Pisa, Andrea Detti, Nicola Blefari-Melazzi… CNIT / University of Rome «Tor Vergata» Pre-FIA workshop on TestbedInteroperability - Athens, March 17th 2014

  2. EXPRESS objectives • Design an innovative, resilient SDN system to extend the SDN applicability domain from fixed networks to intermittently connected network, like wireless mesh networks. • Evaluate our solutions over a federation of three OpenLab testbeds (PlanetLab, NITOS and W-iLab.t), where PlanetLab plays the role of the core fixed network and NITOS and W-iLab.t play the role of the wireless mesh networks

  3. Outline • wmSDN : wireless mesh Software Defined Network • SDN in a highly dynamic networking environment with network partitions /merging • Wireless Mesh Router (WMR) architecture • Controller selection aspects • Testebed interoperability aspects

  4. wmSDNwireless mesh Software Defined Network Controller Controller GW to Internet Internet Wireless Mesh Router(WMR) ClientHosts

  5. wmSDNcontrol plane connections with controllers Controller Controller GW to Internet Internet Wireless Mesh Router(WMR) ClientHosts

  6. wmSDNcontrol plane connections with controllers Controller Controller GW to Internet Internet Wireless Mesh Router(WMR) ClientHosts

  7. wmSDN“in-band” control plane Controller Controller GW to Internet Internet Wireless Mesh Router(WMR) ClientHosts

  8. wmSDNnetwork partitions Controller Controller GW to Internet Internet Wireless Mesh Router(WMR) ClientHosts

  9. wmSDNnetwork partitions Controller Controller GW to Internet Internet Wireless Mesh Router(WMR) ClientHosts

  10. Control and data plane • The OLSR routing protocol for Mobile Adhoc Networks isusedto establish a basic IP connectivity in the Wireless Mesh Net • The OpenFlow/SDN control plane (switch-to-controller communication) goes “in-band” over the basic IP connectivity • Data plane uses the IP connectivity or an “SDN based connectivity” in a flexible way • When using SDN based connectivity, the routing of packet flows is decided by the SDN controller

  11. Control and data plane IP basedcontrol-plane IP baseddata-plane OpenFlow baseddata-plane

  12. wmSDN: architecture • OpenFlow controllers • OLSR Daemon • OpenFlow switch(Open vSwitch) • EFCM - External Flow table and Controller Manager

  13. Details of WMR nodearchitecture • Each physical interface is associated with a virtual interface • Traffic can forwarded in two ways • IP forwarding which operates on the virtual interfaces (routing is set by OLSR) • with SDN rules in the OF switch

  14. Master controller election in SDN fixed nets • Communications among controllers are relatively reliable -> the controllers can run a master election procedure to take control of each switch • (Implementation issue) Open vSwitch can only connect to a preconfigured set of controllers

  15. Master controller election in SDN fixed nets • In a traditional OF environment communications among controllers are relatively reliable -> the controllers can run a master election procedure to take control of each switch • (Implementation issue) Open vSwitch can connect to a preconfigured set of controllers (must be known to the switch in advance) Controller election

  16. Master controller election in SDN fixed nets • In a traditional OF environment communications among controllers are relatively reliable -> the controllers can run a master election procedure to take control of each switch • (Implementation issue) Open vSwitch can connect to a preconfigured set of controllers (must be known to the switch in advance)

  17. From Master Election to Controller Selection • WMRs select the more appropriate controller given the connectivity status of the network (Controller Selection) • The Controller Selection procedure is performed by the EFCM • Simple strategy, based on a “Hierarchy of Controllers”: select the connected controller with the highest level in the hierarchy

  18. From Master Election to Controller Selection Controller Controller GW to Internet Internet Wireless Mesh Router(WMR) ClientHosts

  19. Experimenting in OpenLab testbeds Planet Lab NITOS • Wireless testbeds: • W.iLab-T • NITOS • Fixed testbed • PlanetLab • Interconnection of Wireless testbeds with fixed “backbone” • Ethernet over UDP tunnels across Planet Lab Europe to interconnect the testbeds W.ilab-t

  20. Testbeds interconnection issues Ethernet in UDP tunnels Planet Lab Externalhostwith public IP address Externalhostwith public IP address Planet Lab nodesactingas L2 switches Private IPaddress Creates the L2 overlay W.ilab-t Private IPaddress Management host NITOS

  21. Solutions for testbeds interconnection Ethernet in UDP tunnels Planet Lab Externalhostwith public IP address Externalhostwith public IP address Planet Lab nodesactingas L2 switches NAT Private IPaddress Creates the L2 overlay W.ilab-t Private IPaddress Management host NITOS

  22. Solutions for testbeds interconnection Ethernet in UDP tunnels Planet Lab Externalhostwith public IP address Externalhostwith public IP address Planet Lab nodesactingas L2 switches PFPort Forwarder Creates the L2 overlay Private IPaddress Configures the PF W.ilab-t Private IPaddress Management host NITOS

  23. Testbeds interconnection issues Ethernet in UDP tunnels Planet Lab Planet Lab nodesactingas L2 switches NAT Creates the L2 overlay, taking care of the connectionscoming from NAT boxes NAT Private IPaddress W.ilab-t Private IPaddress Management host NITOS

  24. Solutions for testbed interconnection • (1) “Port Forwarder” running in the node that interconnects a testbed with the Internet, it can run at kernel level or application level • (2) Regular NAT translation of an outgoing UDP flow from a node in the testbed and terminating in the tunnel endpiont node in Planet Lab

  25. Controller selection over federated testbeds • The Network is divided in 3 partitions: blue, green and gray • WMRs in different partition are connected to the best available controller (or using only IP routing if no controller is available)

  26. Controller selection over federated testbeds • Network partition are joined together • WMRs are connected to the “best” available controller

  27. http://netgroup.uniroma2.it/wmSDN/ Thank you for your attentionQuestions? UNIVERSITY OF ROME “TOR VERGATA” DepartmentofElectronicsEngineering Via del Politecnico, 1 - 00133 Rome - Italy Stefano Salsano, Ph. D. Assistant professor Phone: +39 06 7259 7770 Fax: +39 06 7259 7435 e-mail: stefano.salsano@uniroma2.it http://netgroup.uniroma2.it/Stefano_Salsano

More Related