PRISTINE Project A different approach to SDN

Transcription

1 PRISTINE Project A different approach to SDN Joan A. García-Espín Area Director Distributed Apps and Nets January 30 th, 2014 RINA Research, Korea-EU Workshop

2 Primary Goals of SDN 1. Commodi(za(on of network equipment 2. Programmability What for? Flexibility, agility, re- use and automa5on Seamless integra5on with infra. management solu5ons and lowering CAPEX and OPEX! 1

3 Generic Scenario App. MW or Orchestrator Northbound interface Northbound interface App. MW or Orchestrator Controller East/West interface Controller Southbound interface (Openflow or other) Southbound interface (Openflow or other) 2

4 Inconveniences Commodi(za(on: Who decides what is the minimum? Programmability: Only for the forwarding table? What about data transfer, flow control, resource alloca5on, authen5ca5on, access control, enrolment, Complexity: based on TCP/IP? Tons of RFCs, security, mul5- homing, mobility, 3

5 RINA, Foundation of PRISTINE Inter- Process Communica5on (IPC) Distributed IPC Facility (DIF) Recursive Inter- Network Architecture (RINA) Ref. : J. Day: PaHerns in Network Architecture: A Return to Fundamentals, Pren(ce Hall,

6 RINA Architecture 5

7 RINA and SDN Goals, how? Commodi(za(on: RINA defines the common elements in computer networking Programmability: RINA defines the variable behaviour for common elements, and hence common APIs to program them Complexity: RINA maximizes the invariants, hence requires far less protocols to provide computer networking 6

8 PRISTINE at a glance Design a RINA SDK Design and implement a RINA management system (mul5- layer) Implement trial policies to create op5mized DIFs: distributed cloud, DC networking and NSP External Advisory Board Cisco Systems, Telecom Italia, Deutsche Telekom, Colt Telecom, Boston Univesity, Interoute 7

9 PRISTINE and RINA Roadmap Research on policies for different areas: Conges5on control, distributed resource alloca5on, addressing, rou5ng, authen5ca5on, access control, encryp5on, DIF management Prototype and Test: Implementa5on leveraging IRATI for Linux OS. Develop SDK, Policies and DIF- MS Experiment: Complex deployments, coexis5ng technologies at once (IPv4, IPv6, Ethernet), business applica5ons 8

10 PRISTINE Infrastructure Virtual Wall EXPERIMENTA Tren(no Testbed 9

11 Summary SDN is not only OpenFlow and controllers RINA offers a new playground for SDN PRISTINE project just started, to build RINA SDK for you to experiment SDN in a different way 10

12 Moltes gràcies! Thank you! Joan A.

13 Bottomline Are all these protocols for each layer really required? TCP(L4) IP(L3) IEEE (L2) VXLAN(L2) UDP (L4) IP (L3) IP (L3) IEEE (L2) MPLS (L2.5) IEEE 802.1q (L2) IEEE 802.1ah (L2) How many layers you say? 5? 7? 11? Err.. Who cares? Thanks we have RINA! 12

14 From Theory to Practice Data transfer Manage ment Security DIF crea(on Research on policies for different areas Mul(plexing Applica(on discovery Enrollment Policy specs Rou(ng New Insights & Invariances Resource alloca(on Design and development of simulators Study different use cases and deployment op(ons SDKs Simul ators Use case analy sis Test apps Experiment a(on and valida(on Prototy pes & Tools Data and conclu sions Research on RINA reference model Core RINA specs Prot. analyz Tools Java VM Linux OS Prototyping & Tool Development Different Plaborms Android OS NetFP GA Coexis(ng with different technologies MPLS TCP/ UDP/IP LTE VLANs WiFi 13

15 PRISTINE Use Cases Distributed cloud Decentralized cloud technology; customer s applica5ons run in DCs but also in servers from offices and home users. Infrastructure interconnected through mul5ple ISPs, overall connec5vity provided through overlay on top - > Use RINA to provide this overlay Datacentre networking Evaluate RINA as a technology that allows more dynamicity and 5ghter integra5on with applica5ons (dynamic instan5a5on of applica5on- op5mized VPNs) Network Service Provider Inves5gate benefits of RINA for NSP: beker network design, simpler management, DIFs that support different levels of QoS with stronger flow isola5on, beker security, programmability, etc. 14