View
215
Download
0
Category
Preview:
Citation preview
Closed2Open Networking
Linux Day 2015Napoli, October 24 2015
Antonio Pescapè, pescape@unina.it
Who am I? Antonio Pescape' Dipartimento di
Ingegneria Elettrica e delle Tecnologie dell'Informazione (DIETI)
University of Napoli ''Federico II''
Via Claudio, 21 - 80125, Napoli (Italy) [Room n. 4.09]
tel. +39 081 7683856 - fax +39 081 7683816
e-mail : pescape@unina.it2
Agenda From “Closed Networking” to “Open
Networking” Software Defined Networks Open Network Technologies A Real Example: Google Data Network References
3
From “Closed Networking” to “Open
Networking”
4
Million of linesof source code
5400 RFCs Barrier to entry
500M gates10Gbytes RAM
Bloated Power Hungry
Many complex functions baked into the infrastructureOSPF, BGP, multicast, differentiated services,Traffic Engineering, NAT, firewalls, MPLS, redundant layers, …
An industry with a “mainframe-mentality”
We have lost our way
Specialized Packet Forwarding Hardware
OperatingSystem
App
App
App
Routing, management, mobility management, access control, VPNs, …
slide by Nick McKeown, Stanford University
Operating System
Reality
App Ap
p
App
Specialized Packet Forwarding Hardware
Specialized Packet Forwarding Hardware
OperatingSystem
App
App
App
• Lack of competition means glacial innovation• Closed architecture means blurry, closed interfaces
slide by Nick McKeown, Stanford University
Glacial process of innovation made worse by captive standards process
DeploymentIdea Standardize
Wait 10 years
• Driven by vendors• Consumers largely locked out• Lowest common denominator features• Glacial innovation
slide by Nick McKeown, Stanford University
Total number of RFCs published
8slide by Ronald van der Pol, Surfnet
Example: IEEE 802.11Q
9slide by Ronald van der Pol, Surfnet
Example: specs of an Ethernet Switch
10slide by Ronald van der Pol, Surfnet
Computing
11slide by Nick McKeown, Stanford University
Networking
12slide by Nick McKeown, Stanford University
Software Defined Networks
14
Specialized Packet Forwarding Hardware
App
App
App
Specialized Packet Forwarding Hardware
App
App
App
Specialized Packet Forwarding Hardware
App
App
App
Specialized Packet Forwarding Hardware
App
App
App
Specialized Packet Forwarding Hardware
OperatingSystem
OperatingSystem
OperatingSystem
OperatingSystem
OperatingSystem
App
App
App
Network Operating System
App App App
Change is happening in non-traditional markets
slide by Nick McKeown, Stanford University
App
Simple Packet Forwarding Hardware
Simple Packet Forwarding Hardware
Simple Packet Forwarding Hardware
App App
Simple Packet Forwarding Hardware Simple Packet
Forwarding Hardware
Network Operating System
1. Open interface to hardware
3. Well-defined open API2. At least one good operating system
Extensible, possibly open-source
The “Software-defined Network”
slide by Nick McKeown, Stanford University
Vision behind SDN
17
Slicing the physical network
18slide by Nick McKeown, Stanford University
Simple Packet Forwarding Hardware
Network Operating System 1
Open interface to hardware
Virtualization or “Slicing” Layer
Network Operating System 2
Network Operating System 3
Network Operating System 4
App
App
App
App
App
App
App
App
Many operating systems, orMany versions
Open interface to hardware
Isolated “slices”
Simple Packet Forwarding Hardware
Simple Packet Forwarding Hardware
Simple Packet Forwarding Hardware
Simple Packet Forwarding Hardware
slide by Nick McKeown, Stanford University
Consequences
More innovation in network services Owners, operators, 3rd party developers,
researchers can improve the network E.g. energy management, data center
management, policy routing, access control, denial of service, mobility
Lower barrier to entry for competition Healthier market place, new players
slide by Nick McKeown, Stanford University
The change has already started
In a nutshell Driven by cost and control Started in data centers…. and has spread Transition is towards an open-source,
software-defined network Growing interest for cellular and telecom networks
(5G)
Modified slide by Nick McKeown, Stanford University
Windows(OS)
Windows(OS)
Linux
MacOS
x86(Computer)
Windows(OS)
AppApp
Linux
Linux
MacOS
MacOS
Virtualization layer
App
Controller 1
AppApp
Controller2
Virtualization or “Slicing”
App
OpenFlow
Controller 1
NOX(Network OS)
Controller2
Network OS
Transition
Computer Industry Network Industry
Modified slide by Nick McKeown, Stanford University
Open Network Technologies
(not exhaustive)
23
Overview of Open Network Technologies
24slide by Ronald van der Pol, Surfnet
Typical Network Operating System (switch and/or router)• Structured as “black box”
CLI != API
• Closed development model Diagnostics “under the hood” difficult to see
• Complicated management tool chains SNMP MIB’s… hell Screen scraping… regex’s change on OS version Arcane / low adoption scripting languages
• Not geared for rapid spin-up / spin-down of resources
Traditional networking
October 16, 201325
slide by Cumulus Networks
• IP-based networks Limited adoption - large scale L2, InfiniBand, ATM
• Configuration management / automation Monitoring Policy enforcement Rapid spin-up / spin-down
• New breed of applications East-West vs. North-South flows
October 16, 201326
Modern datacenter network roots
slide by Cumulus Networks
• Dominate server platform Well established ecosystem of distributions, best practices,
knowledge Open well documented API, large selection of language
interpreters Excellent networking support - IPv6, NAT’s, QoS, accounting
• Vibrant community which fuels rapid innovation
• Heavy automation frameworks Open nature has facilitated huge management tool-chain progress
October 16, 201327
Linux?
slide by Cumulus Networks
GNU/Linux is a great fit as the OS for not just servers but also routers and switches in the modern data center
In other words…
October 16, 201328
slide by Cumulus Networks
October 16, 201329
Linux as the embedded OS: process and memory mgmt
Embedded OS with process and memory mgmt
No real OS, while loop
Monolithic OS 3rd Real-time OS
Linux-based OS
Eg: IOS, CatOS
Proprietary routingand switching stack
Eg: ION Eg: NX-OS, EOS
Eg: Cumulus Linux
Linux OS
Linux as Network OS:Native routingand switching
Proprietary routingand switching stack
Proprietary routingand switching stack
Network Device Operating System Evolution
Modified slide by Cumulus Networks
Open Hardware Switches
30slide by Ronald van der Pol, Surfnet
Open Compute Project
31slide by Ronald van der Pol, Surfnet
Open Network Install Environment (1/2)
32slide by Ronald van der Pol, Surfnet
Open Network Install Environment (2/2)
33slide by Ronald van der Pol, Surfnet
FaceBook Wedge 6-Packopen hardware modular switch
34
Edge-Core White Label Switches
35slide by Ronald van der Pol, Surfnet
DELL ONIE Switches
36slide by Ronald van der Pol, Surfnet
Open Network Linux
39slide by Ronald van der Pol, Surfnet
Emerging Open Switch Ecosystems
40slide by Ronald van der Pol, Surfnet
Apple
41slide by Ronald van der Pol, Surfnet
Facebook and Mellanox
42slide by Ronald van der Pol, Surfnet
HP and Microsoft
43slide by Ronald van der Pol, Surfnet
A Real Example:Google Data Network
44
Google Data Network
45slide by Ronald van der Pol, Surfnet
Google Data Network
46slide by Ronald van der Pol, Surfnet
Google Data Network: Google Open Flow Switch
47slide by Ronald van der Pol, Surfnet
Google Data Network
48slide by Ronald van der Pol, Surfnet
Google Data Network: almost 100% utilization
49slide by Ronald van der Pol, Surfnet
Google Data Network
50slide by Ronald van der Pol, Surfnet
References/Credits
51
• This talk contains slides or ideas from the following sources:
• Ronal van der pol, Emerging Software Defined Networking & Open APIs Ecosystem, March 2015
• Ronal van der pol, Abstractions and Open APIs in Networking, April 2015• Nick McKneown, Software-defined Networks, October 2009• Over coming traditional network limitations with open source, Cumulus
Networks
This talk and/or part of it can be used freely.
Thank you for your attention!
52
Any Questions?
?
Recommended