Your SlideShare is downloading. ×
0
Rina IRATI @ GLIF Singapoure -2013
Rina IRATI @ GLIF Singapoure -2013
Rina IRATI @ GLIF Singapoure -2013
Rina IRATI @ GLIF Singapoure -2013
Rina IRATI @ GLIF Singapoure -2013
Rina IRATI @ GLIF Singapoure -2013
Rina IRATI @ GLIF Singapoure -2013
Rina IRATI @ GLIF Singapoure -2013
Rina IRATI @ GLIF Singapoure -2013
Rina IRATI @ GLIF Singapoure -2013
Rina IRATI @ GLIF Singapoure -2013
Rina IRATI @ GLIF Singapoure -2013
Rina IRATI @ GLIF Singapoure -2013
Rina IRATI @ GLIF Singapoure -2013
Rina IRATI @ GLIF Singapoure -2013
Rina IRATI @ GLIF Singapoure -2013
Rina IRATI @ GLIF Singapoure -2013
Rina IRATI @ GLIF Singapoure -2013
Rina IRATI @ GLIF Singapoure -2013
Rina IRATI @ GLIF Singapoure -2013
Rina IRATI @ GLIF Singapoure -2013
Rina IRATI @ GLIF Singapoure -2013
Rina IRATI @ GLIF Singapoure -2013
Rina IRATI @ GLIF Singapoure -2013
Rina IRATI @ GLIF Singapoure -2013
Rina IRATI @ GLIF Singapoure -2013
Rina IRATI @ GLIF Singapoure -2013
Rina IRATI @ GLIF Singapoure -2013
Rina IRATI @ GLIF Singapoure -2013
Rina IRATI @ GLIF Singapoure -2013
Rina IRATI @ GLIF Singapoure -2013
Rina IRATI @ GLIF Singapoure -2013
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Rina IRATI @ GLIF Singapoure -2013

67

Published on

plennary talk

plennary talk

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
67
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. 13th Annual Global LambdaGrid Workshop Early RINA prototyping and deployment in the IRATI project, and future research in the PRISTINE and IRINA projects Sergi Figuerola, Innovation and Technology Director (sergi.Figuerola@i2cat.net) 13th annual Global LambdaGrid Workshop October 4th, 2013
  • 2. 13th Annual Global LambdaGrid Workshop 2 Agenda • What is RINA • Why researching RINA • Flow of research and development activities • EC-funded RINA research – IRATI – PRISTINE (in negotiations) – IRINA (in negotiations)
  • 3. 13th Annual Global LambdaGrid Workshop RINA is an.. Innovative approach to computer networking using inter-process communications (IPC), a set of techniques for the exchange of data among multiple threads in processes running on one or more computers connected to a network. 3 The RINA principle: Networking is not a layered set of different functions but rather a single layer (DIF) of distributed IPC’s that repeats over different scopes. Ref. : J. Day: “Patterns in Network Architecture: A Return to Fundamentals, Prentice Hall, 2008.
  • 4. 13th Annual Global LambdaGrid Workshop RINA Architecture 4 • A structure of recursive layers that provide IPC (Inter Process Communication) services to applications on top • There’s a single type of layer that repeats as many times as required by the network designer • Separation of mechanism from policy • All layers have the same functions, with different scope and range. – Not all instances of layers may need all functions, but don’t need more. • A Layer is a Distributed Application that performs and manages IPC (a Distributed IPC Facility –DIF-) • This yields a theory and an architecture that scales indefinitely, – i.e. any bounds imposed are not a property of the architecture itself. © John Day, All Rights Reserved, 2011
  • 5. 13th Annual Global LambdaGrid Workshop Naming and addressing in RINA • All application processes (including IPC processes) have a name that uniquely identifies them within the application process namespace. • In order to facilitate its operation within a DIF, each IPC process within a DIF gets a synonym that may be structured to facilitate its use within the DIF (i.e. an address). 5  The scope of an address is the DIF, addresses are not visible outside of the DIF.  The Flow Allocator function of the DIF finds the DIF IPC Process through which a destination Application process can be accessed.  Because the architecture is recursive, applications, nodes and PoAs are relative  For a given DIF of rank N, the IPC Process is a node, the process at the layer N+1 is an application and the process at the layer N-1 is a Point of Attachment. 1 2 3 4 1 2 1 2 3 1 2 1 21 2 DIF A DIF B DIF C DIF D DIF E DIF F
  • 6. 13th Annual Global LambdaGrid Workshop Architectural model DIF System (Host) IPC Process Shim IPC  Process Mgmt Agemt System (Router) Shim IPC  Process Shim IPC  Process IPC Process Mgmt Agemt System (Host) IPC Process Shim IPC  Process Mgmt Agemt Appl.  Process Shim DIF  over TCP/UDP Shim DIF  over Ethernet Appl.  Process IPC API Data Transfer Data Transfer Control Layer Management SDU Delimiting Data Transfer  Relaying and  Multiplexing SDU Protection Transmission  Control Retransmission  Control Flow Control RIB  Daemon RIB CDAP  Parser/Generator CACEP Enrollment Flow Allocation Resource Allocation Forwarding Table  Generator  Authentication State Vector State Vector State Vector Data Transfer Data Transfer  Transmission  Control Transmission  Control Retransmission  Control Retransmission  Control Flow Control Flow Control Increasing timescale (functions performed less often) and complexity 6
  • 7. 13th Annual Global LambdaGrid Workshop 7 Agenda • What is RINA • Why researching RINA • Flow of research and development activities • EC-funded RINA research – IRATI – PRISTINE (in negotiations) – IRINA (in negotiations)
  • 8. 13th Annual Global LambdaGrid Workshop Why researching RINA (I) • Architecture: – Today: 5 layers, layers “2.5”, layer violations, “overlays”, “virtual networks”, “middleboxes” (NATs, firewalls, application-layer gateways) Getting complex! – RINA: Repeating structure, DIF (one type of layer, repeat as needed) • Naming, addressing and routing: – Today: No independent application names, no node names, just PoA names, routing on PoAs (multi-homing and mobility is hard to support) – RINA: Complete naming & addressing, routing on the node; support for multi- homing and mobility without special protocols. No need for global address space. • Congestion control: – Today: Put in TCP, not in the best place it could be, since it maximizes the delay and variance of the control loop (makes the system chaotic: self-similar traffic) – RINA: Each layer can perform congestion control, confining the effects of congestion to that layer. The delay and variance of control loops can be bound. 8
  • 9. 13th Annual Global LambdaGrid Workshop Why researching RINA (II) • Scalability: – Today: Limited due to the fixed number of layers in the architecture – RINA: Recursion provides a divide and conquer approach, the way to scalability • Security: – Today: No systematic approach to security, secure each protocol or add boxes in between to improve security (firewalls). – RINA: Strong design dictates where security functions go in the architecture (encryption, authenticaiton, access control). DIFs are securable containers. • Quality of Service: – Today: Best effort is the dogma, applications cannot express desired outcomes – RINA: Each DIF is free to provide different QoS classes, using different policies for resource allocation, routing and data transfer. Applications can request the desired characteristics for a flow (delay, loss, ordering, etc) • Management: – Today: Complex, reflecting the complexity in the architecture and the high number of protocols. – RINA: The commonality in the structure simplifies management by orders of magnitude 9
  • 10. 13th Annual Global LambdaGrid Workshop 10 Agenda • What is RINA • Why researching RINA • Flow of research and development activities • EC-funded RINA research – IRATI – PRISTINE (in negotiations) – IRINA (in negotiations)
  • 11. 13th Annual Global LambdaGrid Workshop 11 Flow of RINA R&D activities (feedback between activities not shown for clarity reasons) Research on  RINA  reference  model Core  RINA  specs Research on  policies for  different  areas Data  transfer Manage ment Security Routing Resource  allocation Enrollment Application  discovery Multiplexing DIF  creation Policy  specs Design and  development of  simulators Simul ators Prototyping Different  Platforms Java  VM Linux  OS Android  OS NetFP GA Coexisting  with  different  technolog ies TCP/UDP /IP VLANs WiFi LTEMPLS Proto typesStudy  different use  cases and  deployment  options Use  case  analy sis Experiment ation and  validation Data  and  conclu sions
  • 12. 13th Annual Global LambdaGrid Workshop 12 Agenda • What is RINA • Why researching RINA • Flow of research and development activities • EC-funded RINA research – IRATI – PRISTINE (in negotiations) – IRINA (in negotiations)
  • 13. 13th Annual Global LambdaGrid Workshop IRATI @ a Glance http://irati.eu • What? Main goals – To advance the state of the art of RINA towards an architecture reference model and specifications that are closer to enable implementations deployable in production scenarios. – The design and implementation of a RINA prototype on top of Ethernet will enable the experimentation and evaluation of RINA in comparison to TCP/IP. Budget Total Cost 1.126.660 € EC Contribution 870.000 € Duration 2 years Start Date 1st January 2013 External Advisory Board Juniper Networks, ATOS,  Cisco Systems, Telecom Italia, BU  5 activities:  WP1: Project management  WP2: Arch., Use cases and Req.  WP3: SW Design and Implementation  WP4: Deployment into OFELIA  WP5: Dissemination, Standardisation and Exploitation Who? 4 partners 13
  • 14. 13th Annual Global LambdaGrid Workshop 14 IRATI contributions to RINA roadmap • Reference model and core specifications – Detect inconsistencies and errors • Research on policies for different areas – Routing (link-state), Shim DIF over Ethernet VLANs (802.1q) • Use cases – Corporate VPNs and cloud networking • Prototyping – Initial implementation for Linux OS (user-space and kernel) – Porting of RINA implementation to Juniper platforms • Experimentation – First experimental analysis of RINA against TCP/IP in similar conditions (focusing in LAN environments)
  • 15. 13th Annual Global LambdaGrid Workshop Cloud/Network provider use case (Introduction) • RINA applied to a hybrid cloud/network provider – Mixed offering of connectivity (Ethernet VPN, MPLS IP VPN, Ethernet Private Line, Internet Access) + computing (Virtual Data Center) Access Network Wide Area Network Datacenter Design 15
  • 16. 13th Annual Global LambdaGrid Workshop Cloud/Network provider use case (Modeling) 16 HV VM VM VM HV VM VM VM HV VM VM VM HV VM VM VM TOR HV VM VM VM HV VM VM VM HV VM VM VM HV VM VM VM TOR CE Data Center 1 HV VM VM VM HV VM VM VM HV VM VM VM HV VM VM VM TOR HV VM VM VM HV VM VM VM HV VM VM VM HV VM VM VM TOR CE Data Center 2 PE PE CE Customer 1 Site A PE CE Customer 2 Site A PE PE CE Customer 1 Site B CE Customer 1 Site C CE Customer 2 Site B MPLS backbone Internet GW Customer 2 Site C Public Internet End user
  • 17. 13th Annual Global LambdaGrid Workshop Cloud/Network provider use case (Applying RINA) 17 HV VM TOR Datacenter‐wide DIF CE PE Backbone DIF P PE CE TOR HV VM Datacenter‐wide DIF Backbone Provider top‐level DIF Inter‐datacenter DIF Customer A DIF Network Service Provider  Core Network Provider  Access  network Provider  Access  network Datacenter 2 networkDatacenter 1 network HV VM TOR Datacenter‐wide DIF CE PE Backbone DIF P PE CE Provider top‐level DIF Customer A DIF Interoute core network Access  network Access  network Customer 1 site A networkDatacenter 1 network Scenario 1: Inter‐DC Scenario 2: DC‐Customer
  • 18. 13th Annual Global LambdaGrid Workshop Updated RINA specifications • New specifications contributed to RINA during the first phase of the project – Shim DIF over Ethernet: Overlay RINA on top of IEEE 802.1q (VLANs) – Forwarding Table Generator based on Link-State routing technology (to compute the PDU Forwarding Table in medium- sized DIFs – 200 nodes aprox) • More updates to specs foreseen during the next phases – Enrollment specification adapted to unreliable flows • Required to operate over Ethernet (also over UDP) – Concrete policies for data transfer • Sliding window flow control, retransmissions, rate-based flow control – Adaptation of routing update frequency to better support mobility 18
  • 19. 13th Annual Global LambdaGrid Workshop Shim DIF over Ethernet General requirements • The task of a shim DIF is to put a small as possible veneer over a legacy protocol to allow a RINA DIF to use it unchanged. – Not a RINA-conformant application. We are not trying to make legacy protocols provide full support for RINA. – Anything more should be provided by the first full DIF. • The shim DIF should provide no more service or capability than the legacy protocol provides. DIF System (Host) IPC Process Shim IPC  Process Mgmt Agemt System (Router) Shim IPC  Process Shim IPC  Process IPC Process Mgmt Agemt System (Host) IPC Process Shim IPC  Process Mgmt Agemt Appl.  Process Shim DIF  over TCP/UDP Shim DIF  over Ethernet Appl.  Process 19
  • 20. 13th Annual Global LambdaGrid Workshop High-level software architecture General requirements and choices • Linux has been the chosen target platform for IRATI, due to – It is widely used in different contexts – Open source OS with a great community and documentation • However the implementation aims to be as reusable as possible in similar environments – other UNIX-based Operating Systems • The implementation targets both the user-space and the kernel-space, since – Low performance penalties have to be achieved for highly-frequent tasks (such as reading and writing data) -> Some components must be placed in the kernel – There is the need to access device driver functionalities in order to be able to overlay RINA on top of Ethernet (or other networking technologies in the future) -> Some components must be placed in the kernel 20
  • 21. 13th Annual Global LambdaGrid Workshop High-level software architecture Introduction to the software framework • Components have been partitioned into 3 categories: – Daemons (in user-space) – Libraries (in user-space) – Kernel components • Libraries abstract out the communication details between user-space components and user-space and kernel components • Kernel components implement the “data transfer” and “data transfer control” parts of normal IPC Processes, as well as shim DIFs (“fast path”) • Daemons implement the “layer management” parts of IPC Processes, as well as the IPC Manager. 21
  • 22. 13th Annual Global LambdaGrid Workshop Experimental infrastructure: OFELIA i2CAT island “EXPERIMENTA” 22
  • 23. 13th Annual Global LambdaGrid Workshop 23 Agenda • What is RINA • Why researching RINA • Flow of research and development activities • EC-funded RINA research – IRATI – PRISTINE (in negotiations) – IRINA (in negotiations)
  • 24. 13th Annual Global LambdaGrid Workshop PRISTINE @ a Glance • What? Main goals – To design and develop an SDK for the IRATI RINA prototype, to unleash the programmability provided by RINA. – To use the SDK to design, implement and trial a set of a policies to create optimized DIFs for each of the project use cases: distributed cloud, datacenter networking and network service provider. – To design and implement the first RINA multi-layer management system. Budget Total Cost 5.034.961 € EC Contribution 3.337.000 € Duration 2.5  years Start Date 1st January 2014 External Advisory Board Cisco Systems, Telecom Italia,  Deutsche Telekom, Colt Telecom,  BU, Interoute 7 activities:  WP1: Project management  WP2: Use cases, req. analysis and programmable reference architecture  WP3: Programmable performance- enhancing functions and protocols  WP4: Innovative security and reliability enablers  WP5: Multi-layer management plane  WP6: System-level integration, validation, trials and assessment  WP7: Dissemination, standardisation and exploitation Who? 15 partners WIT‐TSSG, i2CAT, TID, Ericsson, NXW, Thales, Nexedi, Atos, BISDN, Juniper, Telecom SudParis, U Brno, UiO, CREATE‐NET, iMinds 24
  • 25. 13th Annual Global LambdaGrid Workshop 25 PRISTINE contributions to RINA roadmap • Reference model and core specifications – Detect inconsistencies and errors • Research on policies for different areas – Congestion control, distributed resource allocation, addressing, routing, authentication, access control, encryption, DIF management • Use cases – Decentralized cloud, datacentre networking, network service provider • Prototyping – Build on IRATI implementation for Linux OS. Develop SDK to allow easier customization, develop sophisticated policies with SDK. Prototype first DIF Management System • Experimentation – More realistic experimentation, with more complex deployments, coexisting with several technologies at once (IPv4, IPv6, Ethernet), usage of business applications
  • 26. 13th Annual Global LambdaGrid Workshop Use cases • Distributed cloud – Decentralized cloud technology; customer’s applications run in datacenters but also in servers from offices and home users. – Infrastructure interconnected through multiple ISPs, overall connectivity provided through overlay on top -> Use RINA to provide this overlay • Datacentre networking – Evaluate RINA as a technology that allows more dynamicity and tighter integration with applications (dynamic instantiation of application-optimized VPNs) • Network Service Provider – Investigate benefits of RINA for NSP: better network design, simpler management, DIFs that support different levels of QoS with stronger flow isolation, better security, programmability, etc. 26
  • 27. 13th Annual Global LambdaGrid Workshop PRISTINE Infrastructure for trials 27 EXPERIMENTA Virtual  Wall Trentino  Testbed
  • 28. 13th Annual Global LambdaGrid Workshop 28 Agenda • What is RINA • Why researching RINA • Flow of research and development activities • EC-funded RINA research – IRATI – PRISTINE (in negotiations) – IRINA (in negotiations)
  • 29. 13th Annual Global LambdaGrid Workshop 29 IRINA @ a glance • What? Main goals – To make a study of RINA against the current networking state of the art and the most relevant clean-slate architectures under research. – To perform a use-case study of how RINA could be better used in the NREN scenario, and showcase a lab-trial of the use case – To involve the NREN and GEANT community in the different steps of the project, in order to to get valuable feedback Budget Total Cost 199.940 € EC Contribution 149.955 € Duration 18 months Start Date 1st November 2013 5 activities:  WP1: Technical coordination and interaction with GEANT3+  WP2: Comparative analysis of network architectures  WP3: Use case study and lab trials  WP4: Dissemination and workshop organization Who? 4 partners
  • 30. 13th Annual Global LambdaGrid Workshop 30 IRINA contributions to RINA roadmap • Reference model and core specifications – Compare with other clean-slate architectures • Use cases – Research network operators (NRENs and GEANT environment) • Prototyping – Little adaptations to the IRATI prototype (Linux OS), to be able to trial the use case in the lab • Experimentation – Focus on the requirements of NRENs
  • 31. 13th Annual Global LambdaGrid Workshop GEANT and NRENs use case 31
  • 32. 13th Annual Global LambdaGrid Workshop Many Thanks ! Moltes gràcies ! Sergi Figuerola, Innovation and Technology Director (sergi.Figuerola@i2cat.net) 13th annual Global LambdaGrid Workshop October 4th, 2013 Eduard Grasa, RINA research line leader (eduard.grasa@i2cat.net) http://www.i2cat.cat http://dana.i2cat.net http://irati.eu

×