Introduction to Network Function Virtualization (NFV)rjain51
Class lecture by Prof. Raj Jain on Introduction to Network Function Virtualization (NFV). The talk covers Four Innovations of NFV, Network Function Virtualization, NFV, Why We need NFV?, NFV and SDN Relationship, Mobile Network Functions, ETSI NFV ISG, NFV Specifications, NFV Architecture, NFV Concepts, Network Forwarding Graph, NFV Reference Points, NFV Framework Requirements, NFV Use Cases, NFV Proof of Concepts, PoCs, ETSI ISG Timeline, Introduction to, Four Innovations of NFV, Network Function Virtualization, NFV, Why We need NFV?, NFV and SDN Relationship, Mobile Network Functions, ETSI NFV ISG, NFV Specifications, NFV Architecture, NFV Concepts, Network Forwarding Graph, NFV Reference Points, NFV Framework Requirements, NFV Use Cases, NFV Proof of Concepts, PoCs, ETSI ISG Timeline. Video recording available in YouTube.
A VPN (Virtual Private Network) extends a private network across a public network, such as the
Internet.
A VPN is a network that uses a public telecommunication infrastructure, such as the Internet, to provide
remote offices or individual users with secure access to their organization's network. A VPN ensures
privacy through security procedures and tunneling protocols such as the Layer Two Tunneling Protocol
(L2TP). Data is encrypted at the sending end and decrypted at the receiving end.
Presented by Andy Sutton, Principal Network Architect - Chief Architect’s Office, TSO, BT at IET "Towards 5G Mobile Technology – Vision to Reality" seminar on 25th Jan 2017
Shared with permission
Introduction to Network Function Virtualization (NFV)rjain51
Class lecture by Prof. Raj Jain on Introduction to Network Function Virtualization (NFV). The talk covers Four Innovations of NFV, Network Function Virtualization, NFV, Why We need NFV?, NFV and SDN Relationship, Mobile Network Functions, ETSI NFV ISG, NFV Specifications, NFV Architecture, NFV Concepts, Network Forwarding Graph, NFV Reference Points, NFV Framework Requirements, NFV Use Cases, NFV Proof of Concepts, PoCs, ETSI ISG Timeline, Introduction to, Four Innovations of NFV, Network Function Virtualization, NFV, Why We need NFV?, NFV and SDN Relationship, Mobile Network Functions, ETSI NFV ISG, NFV Specifications, NFV Architecture, NFV Concepts, Network Forwarding Graph, NFV Reference Points, NFV Framework Requirements, NFV Use Cases, NFV Proof of Concepts, PoCs, ETSI ISG Timeline. Video recording available in YouTube.
A VPN (Virtual Private Network) extends a private network across a public network, such as the
Internet.
A VPN is a network that uses a public telecommunication infrastructure, such as the Internet, to provide
remote offices or individual users with secure access to their organization's network. A VPN ensures
privacy through security procedures and tunneling protocols such as the Layer Two Tunneling Protocol
(L2TP). Data is encrypted at the sending end and decrypted at the receiving end.
Presented by Andy Sutton, Principal Network Architect - Chief Architect’s Office, TSO, BT at IET "Towards 5G Mobile Technology – Vision to Reality" seminar on 25th Jan 2017
Shared with permission
The OpenRAN architecture, empowered by intelligence and openness principles, is the foundation for building the virtualized RAN on open hardware and cloud, with embedded AI-powered radio control. The architecture is based on standards defined by O-RAN Alliance, which completely support and are complementary to standards promoted by 3GPP and other industry standards organizations.
Presentation detailed about SDN (Software Defined Network) overview . It covers from basics like different controllers and touches upon some technical details.
Covers Terminologies used, OpenFlow, Controllers, Open Day light, Cisco ONE, Google B4, NFV,etc
Software Defined Networking (SDN) Technology BriefZivaro Inc
An overview of Software-Defined Networking (SDN) and the key benefits of moving to a virtualized network, including:
- Improved time to market through automation
- Optimal trafficking with a global view of the network
- Quicker enablement of new services
- Reduced operating costs
- Improved management and visibility
- Simplified operation of network devices
From "Introduction to Software Defined Networking" webinar presented by GTRI CTO Scott Hogg on March 10, 2016. Webinar recording: https://youtu.be/gRXnctYDBjE
Introduction to Software Defined Networking (SDN)rjain51
Class lecture by Prof. Raj Jain on Introduction to . The talk covers Origins of SDN, What is SDN?, Original Definition of SDN, What = Why We need SDN?, SDN Definition, XMPP, XMPP in Data Centers, Path Computation Element, PCE, Forwarding and Control Element, Sample ForCES Exchanges, Application Layer Traffic Optimization, ALTO, ALTO Extension, Current SDN Debate: What vs. How?, SDN Controller Functions, RESTful APIs, OSGi Framework, Open Daylight SDN Controller, OpenDaylight Tools, Affinity Metadata Service, SDN Related Organizations and Projects, SDN Web Sites, Hierarchy of Operations, Introduction to, Origins of SDN, What is SDN?, Original Definition of SDN, What = Why We need SDN?, SDN Definition, XMPP, XMPP in Data Centers, Path Computation Element, PCE, Forwarding and Control Element, Sample ForCES Exchanges, Application Layer Traffic Optimization, ALTO, ALTO Extension, Current SDN Debate: What vs. How?, SDN Controller Functions, RESTful APIs, OSGi Framework, Open Daylight SDN Controller, OpenDaylight Tools, Affinity Metadata Service, SDN Related Organizations and Projects, SDN Web Sites. Video recording available in YouTube.
The OpenRAN architecture, empowered by intelligence and openness principles, is the foundation for building the virtualized RAN on open hardware and cloud, with embedded AI-powered radio control. The architecture is based on standards defined by O-RAN Alliance, which completely support and are complementary to standards promoted by 3GPP and other industry standards organizations.
Presentation detailed about SDN (Software Defined Network) overview . It covers from basics like different controllers and touches upon some technical details.
Covers Terminologies used, OpenFlow, Controllers, Open Day light, Cisco ONE, Google B4, NFV,etc
Software Defined Networking (SDN) Technology BriefZivaro Inc
An overview of Software-Defined Networking (SDN) and the key benefits of moving to a virtualized network, including:
- Improved time to market through automation
- Optimal trafficking with a global view of the network
- Quicker enablement of new services
- Reduced operating costs
- Improved management and visibility
- Simplified operation of network devices
From "Introduction to Software Defined Networking" webinar presented by GTRI CTO Scott Hogg on March 10, 2016. Webinar recording: https://youtu.be/gRXnctYDBjE
Introduction to Software Defined Networking (SDN)rjain51
Class lecture by Prof. Raj Jain on Introduction to . The talk covers Origins of SDN, What is SDN?, Original Definition of SDN, What = Why We need SDN?, SDN Definition, XMPP, XMPP in Data Centers, Path Computation Element, PCE, Forwarding and Control Element, Sample ForCES Exchanges, Application Layer Traffic Optimization, ALTO, ALTO Extension, Current SDN Debate: What vs. How?, SDN Controller Functions, RESTful APIs, OSGi Framework, Open Daylight SDN Controller, OpenDaylight Tools, Affinity Metadata Service, SDN Related Organizations and Projects, SDN Web Sites, Hierarchy of Operations, Introduction to, Origins of SDN, What is SDN?, Original Definition of SDN, What = Why We need SDN?, SDN Definition, XMPP, XMPP in Data Centers, Path Computation Element, PCE, Forwarding and Control Element, Sample ForCES Exchanges, Application Layer Traffic Optimization, ALTO, ALTO Extension, Current SDN Debate: What vs. How?, SDN Controller Functions, RESTful APIs, OSGi Framework, Open Daylight SDN Controller, OpenDaylight Tools, Affinity Metadata Service, SDN Related Organizations and Projects, SDN Web Sites. Video recording available in YouTube.
Security Advantages of Software-Defined NetworkingPriyanka Aash
Current practices using wide-area routing over Internet infrastructure decentralize the control of how information is transferred. Software-Defined Networking (SDN) centralizes network control functions, offering more holistic network security management and allowing for dynamic divisioning, multivendor end-to-end security and reduced dependence on the traditional perimeter approach.
(Source: RSA USA 2016-San Francisco)
Software Defined Networks
By: Thierry Couture, Consulting Systems Architect
There is currently a lot of buzz around OpenFlow and Software Defined Networks (SDN) in the industry. It would be a mistake to think that these are one and the same. The reality is that the current market conversation has loose semantics mixed in with hyperbole and hearsay that hide the simplicity of SDN behind terms like Openstack, Virtual Overlays, Network Function Virtualization, Orchestration, etc. This session will explain the origins of SDN, establish a basic terminology for SDN concepts, and offer a framework to both understand these trends and distill the applicability of SDN through a use case lens.
DevNet Express - Spark & Tropo API - Lisbon May 2016Cisco DevNet
Direct from the Cisco DevNet Lisbon Portugal Express event in May 2016. Learn about Cisco DevNet, Spark and Tropo APIs any why there's never been a better time to innovate with Cisco.
A session in the DevNet Zone at Cisco Live, Berlin. Network Topology Visualization is an important part of many SDN applications and other domains. Easy customization and building a new component base on NeXt to adapt to different requirements is critical. This session will illustrate how to customize topology components and how to build other visualization components with the latest commercial version.
DEVNET-1114 Automated Management Using SDN/NFVCisco DevNet
How is the open source community using SDN/NFV to create truly heterogeneous, inter-operable, multi-tenant cloud data centers? We’ll present results from our independent testing of cloud orchestration, middleware, SaaS, and Iaas multi-vendor solutions, including SDN’s inroads to the telecommunication world and how networking influences emerging trends like Docker virtual containers in the cloud.
SDN( Software Defined Network) and NFV(Network Function Virtualization) for I...Sagar Rai
Software, Software Defined Network, Network Function Virtualization, SDN, NFV, Internet of things, Basics of Internet of things, Network Basics, Virtualization, Limitation of Conventional Network, Open flow, Basics of conventional network,
The Cisco Open SDN Controller is a commercial distribution of OpenDaylight that delivers business agility through automation of standards-based network infrastructure.
Built as a highly scalable software-defined networking (SDN) platform, the Open SDN Controller abstracts away the complexity of managing heterogeneous networks to improve service delivery and reduce operating costs.
The controller exposes REST APIs to allow other applications to take advantage capabilities of the controller and unlock the power of the underlying network infrastructure, and JAVA APIs to allow for the creation of new network services.
This session will present the basic constructs of the controller and the capabilities of the REST and JAVA APIs to demonstrate how the Open SDN Controller abstracts away the complexity of managing heterogeneous networks to improve service delivery and reduce operating costs.
DEVNET-1154 Open Source Presentation on Open StandardsCisco DevNet
How is the open source community using SDN/NFV to create truly heterogeneous, inter-operable, multi-tenant cloud data centers? We’ll present results from our independent testing of cloud orchestration, middleware, SaaS, and Iaas multi-vendor solutions, including SDN’s inroads to the telecommunication world and how networking influences emerging trends like Docker virtual containers in the cloud.
Smart Citizen Kit in Barcelona, Amsterdam & ManchesterFrank Kresin
From March till June, the Barcelona built Smart Citizen Kit was implemented in Amsterdam. The project aimed to help citizens to get a better grips on the local climate, and to stimulate discussion between citizens, and between citizens and city officials and servants. This presentation talks about the reason for the project, the affordances of the Smart Citizen Kit, and
The project was initiated by Waag Society and Amsterdam Smart City, and partnered with Fablab Barcelona and FutureEverything. It was additionally funded by the Fund for the Creative Industries, NL.
OpenStack and OpenDaylight, The Evolving Relationship in Cloud Networking: a ...Cisco DevNet
A session in the DevNet Zone at Cisco Live, Berlin. OpenStack is well established as the public/private cloud platform, abstracting compute, storage, and networking resources behind a unified set of APIs. OpenStack Neutron provides the lion's share of networking resources and seems sufficient for many small private cloud deployments. As scale increases and service providers with large network footprints come into the picture, new complications arise. Service provider networks have requirements and capabilities far beyond those addressable with Neutron. Software Defined Networking (SDN) and Network Function Virtualization (NFV) has given rise to modular network controllers in the service provider space. OpenDaylight is the open source world’s answer, and service providers want to be able to marry OpenStack orchestration with OpenDaylight networking, as evident by the Open Platform for Network Function Virtualization project (OPNFV). Come learn how SDN controllers fit in this context vs. OpenStack with neutron drivers, when to use one when to use the other, and the benefits and functionality of each.
SDN and NFV integrated OpenStack Cloud - Birds eye view on SecurityTrinath Somanchi
Network security and reliability are the most challenging tasks in any cloud. With NFV and SDN in place, Network Functions are virtualzied and network traffic is managed in separated control and data planes. Thus reducing the operational and capital expenditure. Virtualized Network Functions are tied with Software Defined Networks to boost the power of virtualization.
This itself is challenging when Network services and security is a concern. While OpenStack is the best opted solution for IaaS, many service provides are moving towards best solutions to deal with service delivery and security challenges in SDN and NFV integrated OpenStack Cloud.
An introductory slides for explaining the SDN and NFV technologies. what's the difference between them and when each one is used. Also it talk about some of Cisco products in each area either SDN or NFV or the Automation with some of real use cases deployed in today's service provider network.
Hope you like it
The main scope of up-gradation to the advanced computer networks is to make the technical advancement in the network management and so managing the traffic control (that is the control plane and data or forwarding plane) while abridging it in the Multi-Controller Domain. SDN refers to the isolation of the network control plane from the forwarding plane, with a control plane overseeing many networking systems. This paper investigates how new improvements in SDN and the programmability of networks can be helpful to abridge tasks, improve dexterity, and encounter new task necessities within the U.S. Department of Defense (DoD) and open networks. These improvised network services across the digital network entail a multi-controller domain. This paper represents the research in SDN and multi-controller domain, aiming at OpenFlow Protocol and its upcoming challenging tasks.
SDN Performance evaluation for floodlight controller and OVS controller using adaptive approaches (i.e. statistical approach and genetic algorithm approach).
Software Define Network, a new security paradigm ?Jean-Marc ANDRE
How SDN works, what is openflow, how sdn will change the way you design a network? Is SDN a secure place ? In this slideshow we do a compilation of sources and explain what is SDN reality.
Scott Shenker
ICSI/Berkeley/ONF
ONS2015: http://bit.ly/ons2015sd
ONS Inspire! Webinars: http://bit.ly/oiw-sd
Watch the talk (video) on ONS Content Archives: http://bit.ly/ons-archives-sd
Web-Based User Interface for the Floodlight SDN ControllerEswar Publications
Software Defined Networking (SDN) was born as a solution for next-generation network design. Due to its flexible architecture, SDN promises to make network devices simpler while giving better centralized control ability over network and improving parameters such as flexibility, resilience, reliability, and security. In this paper, we briefly introduce the SDN architecture and the Floodlight Controller that is one of the popular SDN controllers. We build a web-based user interface for the Floodlight Controller by using REST API. This application is the first program in the Floodlight SDN Controller literature to view the controller upon several properties such as device connections and flow tables.
Controller Placement Problem resiliency evaluation in SDN-based architecturesIJCNCJournal
The Software-Defined Networking (SDN) paradigm does represent an effective approach aimed at enhancing the performance of core networks by introducing a clean separation between the routing plane and the forwarding plane. However, the centralized architecture of SDN networks raises resiliency concerns that are addressed by a class of algorithms falling under the Controller Placement Problem (CPP) umbrella term. Such algorithms seek the optimal placement of the SDN controller. In this paper, we evaluate the main CPP algorithms and provide an experimental analysis of their performance, as well as of their capability to dynamically adapt to network malfunctions and disconnections.
Controller Placement Problem Resiliency Evaluation in SDN-based ArchitecturesIJCNCJournal
The Software-Defined Networking (SDN) paradigm does represent an effective approach aimed at enhancing the performance of core networks by introducing a clean separation between the routing plane and the forwarding plane. However, the centralized architecture of SDN networks raises resiliency concerns that are addressed by a class of algorithms falling under the Controller Placement Problem (CPP) umbrella term. Such algorithms seek the optimal placement of the SDN controller. In this paper, we evaluate the main CPP algorithms and provide an experimental analysis of their performance, as well as of their capability to dynamically adapt to network malfunctions and disconnections.
David Meyer
Distinguished Engineer
Cisco
Agenda
• Problem Space
• A Few Use Cases
• Reflections on the Promise of OF/SDN
• A Few Challenges and Open Questions
ONS2015: http://bit.ly/ons2015sd
ONS Inspire! Webinars: http://bit.ly/oiw-sd
Watch the talk (video) on ONS Content Archives: http://bit.ly/ons-archives-sd
ODL is one of the most reliable and secured controllers in Software Defined Networks. This presentation takes you through the journey of load-balanced switching.
Software Defined Networking: A Concept and Related IssuesEswar Publications
SDN (Software Defined Networking) is the networking architecture that has gained attention of researchers in recent past. It is the future of programmable networks. Traditional networks were very complex and difficult to manage. SDN is going to change this by offering a standard interface (OpenFlow) between the control plane and the networking devices (data plane). Its implementation is fully supported by software so that we can control the behavior of networking devices through programmatic control. This programmatic control provides various new ways to find breakpoints and failures in networking devices. Today SDN has become an important part of networking, so it is important to emulate its behavior. SDN support virtualization which makes it scalable and flexible. Data traffic resides in the data plane. The main function of intelligent controller is to decide the routing
policy and manage the traffic in data plane. So effectively SDN emerges as a networking architecture that has the ability to solve all problems those were found in traditional architecture In this paper the authors discussed historical perspective of SDN, languages that support SDN, emulation tools, security issues with SDN and advantages that makes SDN suitable choice for today’s network.
Many thanks to Nick McKeown (Stanford), Jennifer Rexford (Princeton), Scott Shenker (Berkeley), Nick Feamster (Princeton), Li Erran Li (Columbia), Yashar Ganjali (Toronto)
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overview
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf
SDN Abstractions
1. The Future of Networking,and the Past of Protocols Scott Shenker with Martin Casado, TeemuKoponen, Nick McKeown (and many others….)
2. Developments in Network “Management” 2004: Early work on new management paradigms RCP, 4D, SANE, Ethane,….. 2008: Software-Defined Networking (SDN) NOX Network Operating System OpenFlow switch interface 2011: Open Networking Foundation Over 30 companies endorsing SDN Board: Google, Yahoo!, Verizon, DT, Microsoft, Facebook Members: Cisco, Juniper, HP, Dell, Broadcom, IBM,…..
3. Software-Defined Networking (SDN) Not just an idle academic daydream Tapped into some strong market need One of those rare cases where we “know the future” Still in development, but consensus on inevitability Much more to story than “OpenFlow” trade rag hype A revolutionary paradigm shift in the network control plane This talk will “derive” SDN from first principles By looking for key network control abstractions
4. I Will Address Two SDN Questions Why is SDN the right choice for future networks? Obviously efficiency, scalability, security, functionality… Not directly. What are the fundamental aspects of SDN? Obviously OpenFlow… No, quite the opposite.
5. But Talk Is Not Primarily About SDN Main focus is on: The Role of Abstractions in Networking
6. Weaving Together Three Themes Networking currently built on weak foundation Lack of fundamental abstractions Network control plane needs three abstractions Leads to SDN v1 and v2 Key abstractions solve other architecture problems Two simple abstractions make architectures evolvable
7. WeakIntellectualFoundations OS courses teach fundamental principles Mutual exclusion and other synchronization primitives Files, file systems, threads, and other building blocks Networking courses teach a big bag of protocols No formal principles, just vague design guidelines
8. WeakPracticalFoundations Computation and storage have been virtualized Creating a more flexible and manageable infrastructure Networks are still notoriously hard to manage Network administrators large share of sysadmin staff
9. WeakEvolutionaryFoundations Ongoing innovation in systems software New languages, operating systems, etc. Networks are stuck in the past Routing algorithms change very slowly Network management extremely primitive
10. Why Are Networking Foundations Weak? Networks used to be simple Basic Ethernet/IP straightforward, easy to manage New control requirements have led to complexity ACLs, VLANs, TE, Middleboxes, DPI,… The infrastructure still works... Only because of our great ability to master complexity Ability to master complexity both blessing and curse
11. A Story About Mastering Complexity ~1985: Don Norman visits Xerox PARC At start of his talk on UI design he asks: “Who in the audience drives a stick shift” After most of the audience raises their hands, he looks sternly out over the crowd and says: “None of you should ever design a user interface
12. Two Points to Story His point: The ability to master complexity is not the same as the ability to extract simplicity When first getting system to work, focus on former When making system easy to use, focus on latter My point: Networking has never made the transition!
13. How Programming Made the Transition Machine languages: no abstractions Had to deal with low-level details Higher-level languages: OS and other abstractions File system, virtual memory, abstract data types, ... Modern languages: even more abstractions Object orientation, garbage collection,... Abstractions simplify programmingEasier to write, maintain, reason about programs
14. Why Are Abstractions/Interfaces Useful? Interfaces are instantiations of abstractions Interface shields a program’s implementation details Allows freedom of implementation on both sides Which leads to modular program structure Barbara Liskov: “Power of Abstractions” talk “Modularity based on abstraction is the way things get done” So, what role do abstractions play in networking?
15. Layers are Main Network Abstractions Layers provide nice data plane service abstractions IP's best effort delivery TCP's reliable byte-stream Aside: good abstractions, terrible interfaces Don’t sufficiently hide implementation details Main Point: Nocontrolplane abstractions No sophisticated management/control building blocks
16. No Abstractions = Increased Complexity Each control requirement leads to new mechanism TRILL, LISP, etc. We are really good at designing mechanisms So we never tried to make life easier for ourselves And so networks continue to grow more complex But this is an unwise course: Mastering complexity cannot be our only focus Because it helps in short term, but harms in long term We must shift our attention from mastering complexity to extracting simplicity….
17. Three Basic Themes of Talk Networking currently built on weak foundation Lack of fundamental abstractions Network control plane needs three abstractions Leads to SDN v1 and v2 Key abstractions solve other architecture problems Two simple abstractions make architectures evolvable
18. How Do We Build Control Plane? We define a new protocol from scratch E.g., routing Or we reconfigure an existing mechanism E.g., traffic engineering Or leave it for manual operator configuration E.g., access control, middleboxes
19. What Are The Design Constraints? Operate within the confines of a given datapath Must live with the capabilities of IP Operate without communication guarantees A distributed system with arbitrary delays and drops Compute the configuration of each physical device Switch, router, middlebox FIB, ACLs, etc. This is insanity!
20. Programming Analogy What if programmers had to: Specify where each bit was stored Explicitly deal with all internal communication errors Within a programming language with limited expressability Programmers would redefine problem by: Defining higher level abstractions for memory Building on reliable communication primitives Using a more general language Abstractions divide problem into tractable pieces Why aren’t we doing this for network control?
21. Central Question What abstractions can simplify the control plane? i.e., how do we separate the problems? Not about designing new mechanisms! We have all the mechanisms we need Extracting simplicity vs mastering complexity Separating problems vs solving problems Defining abstractions vs designing mechanisms
22. Abstractions Must Separate 3 Problems Constrained forwarding model Distributed state Detailed configuration
23. Forwarding Abstraction Control plane needs flexible forwarding model With behavior specified by control program This abstracts away forwarding hardware Crucial for evolving beyond vendor-specific solutions Flexibility and vendor-neutrality are both valuable But one economic, the other architectural Possibilities: General x86 program, MPLS, OpenFlow,….. Different flexibility/performance/deployment tradeoffs
24. State Distribution Abstraction Control program should not have to deal with vagaries of distributed state Complicated, source of many errors Abstraction should hide state dissemination/collection Proposed abstraction: global network view Don’t worry about how to get that view (next slide) Control program operates on network view Input: global network view (graph) Output: configuration of each network device
25. Network Operating System (NOS) NOS: distributed system that creates a network view Runs on servers (controllers) in the network Communicates with forwarding elements in network Gets state information from forwarding elements Communicates control directives to forwarding elements Using forwarding abstraction Control program operates on view of network Control program is not a distributed system NOS plus Forwarding Abstraction = SDN (v1)
26. Current Networks Software-Defined Networking (v1) Protocols Protocols Control Program Global Network View Network Operating System Control via forwarding interface
27. Major Change in Paradigm No longer designing distributed control protocols Now just defining a centralized control function Control program: Configuration= Function(view) Why is this an advance? Much easier to write, verify, maintain, reason about, …. NOS handles all state dissemination/collection Abstraction breaks this off as tractable piece Serves as fundamental building block for control
28. WhatAboutConsistency? NOS must achieve eventual consistency View eventually consistent with real network The configuration is therefore eventually correct Simple function of view What about transient conditions? Hard to ensure good transient behavior with protocols Much easier with NOS What about distributed NOS (multiple controllers)? Need to split up decisions among controllers sensibly
29. Why Does This Approach Scale? Modification of Control Program Strong Consistency 0 - 10/s Per Network Event Eventual Consistency 101 – 103/s Per Flow No Consistency 103 – 106/s Per Packet No Consistency 106 – 108/s
30. Is Performance Good Enough? Architect for simplicity, engineer for performance Many engineering tricks can help SDN performance Caching state Backup paths ….. Don’t overly restrict vision of SDN Key SDN principle: configuration derived from global state “Configuration” can include more general device behaviors SDN ≠ OpenFlow
31. What Role Does OpenFlow Play? NOS conveys configuration of global network view to actual physical devices But nothing in this picture limits what the meaning of “configuration” is OpenFlow is one possible definition of how to model the configuration of a physical device Is it the right one? Absolutely not. Crucial for vendor-independence But not the right abstraction (yet)
32. Alternative SDN Implementation Linecard forwarding model: (per packet behavior) Supports OpenFlow plus x86 (and perhaps GPU) Switch configuration model: (management CPU) Supports JVM (controller can download code) NOS distributed state model: Key-value store Merely an illustration of a richer form of SDN Enables features to emerge in software, migrate to HW
33. Are We Done Yet? This approach requires control program (or operator) to configure each individual network device This is much more complicated than it should be! NOS eases implementation of functionality But does not help specification of functionality! We need a specification abstraction
34. Specification Abstraction Give control program abstract view of network Where abstract view is function of global view Then, control program is abstract mapping Abstract configuration = Function(abstract view) Model just enough detail to specify goals Don’t provide information needed to implement goals
36. More Detailed Model Service model can generally be described by a table pipeline Packet In Packet Out L2 L3 ACL
37. Implementing Specification Abstraction Given: Abstract Table Pipeline L3 ACL L2 Network Hypervisor (Nypervisor) Compiles abstract pipeline into physical configuration Need: pipeline operations distributed over network of physical switches
38. Two Examples Scale-out router: Abstract view is single router Physical network is collection of interconnected switches Nypervisor allows routers to “scale out, not up” Multi-tenant networks: Each tenant has control over their “private” network Nypervisor compiles all of these individual control requests into a single physical configuration “Network Virtualization”
39. Abstract Network View Nypervisor Control Program Global Network View Network Operating System Moving from SDNv1 to SDNv2
40. Clean Separation of Concerns Network control program specifies the behavior it wants on the abstract network view Control program: maps behavior to abstract view Abstract model should be chosen so that this is easy Nypervisor maps the controls expressed on the abstract view into configuration of the global view Nypervisor: abstract model to global view Models such as single cross-bar, single “slice”,… NOS distributes configuration to physical switches NOS: global view to physical switches
41. Three Basic Network Interfaces Forwarding interface: abstract forwarding model Shields higher layers from forwarding hardware Distribution interface: global network view Shields higher layers from state dissemination/collection Specification interface: abstract network view Shields control program from details of physical network
42. Three Basic Themes of Talk Networking currently built on weak foundation Lack of fundamental abstractions Network control plane needs three abstractions Leads to SDN v1 and v2 Key abstractions solve other architecture problems Two simple abstractions make architectures evolvable
43. More General Use of Abstractions So far, focus was on network “management” Operator control within a single domain Ignores host and interdomain issues Did not address basic network “architecture” Naming, addressing, interdomain routing, security,… What abstractions describe Internet architecture? Too general a question…. How can abstractions help clean-slate redesign?
44. What is Goal for Architectural Redesign? A more functional architecture? Pro: We know how to improve security, reliability, etc. Con: Design will be fixed for a generation Like today’s architecture A more evolvable architecture! Pro: Allows functionality to evolve over time Con: We don’t know how to build one Much talk about architectural evolution, no progress Two simple abstractions sufficient to solve problem
45. Why Is Current Architecture Rigid? IP is central component of architecture IP is embedded in interdomain routing And interdomain routing is hard to change IP is embedded in applications (via API) And hard to change all applications Therefore, very hard to change IP!
46. The Current Internet Application Network Stack Architecture is very rigid IP Domain BGP Rest of Internet
47. Insert Two Architectural Abstractions Clean IDR interface: No leakage of intradomain routing across interface Flexible route computation Clean network API (netAPI) No leakage of network architecture across interface Flexible interface semantics Architecture is then evolvable! By making both interfaces abstract and extensible!
48. A More Evolvable Internet Application netAPI Extensible and Abstract Network Stack Network stack and domain have complete freedom to innovate Architecture is very rigid IP Domain BGP Extensible and Abstract IDR Rest of Internet
49. Two Abstractions Evolvability Domains can independently adopt new protocols IPv6, AIP, and other network-level protocols No need for interdomain agreements on L3 New naming systems, APIs can be introduced DONA, CCN, and other data-oriented architectures No need to change existing applications New forms of QoS and other path services No need to change interdomain routing
50. Evolvabilityvs Functionality The IDR/netAPI abstractions help evolvability Specific architectures need functionality abstractions Sockets vsPubSub Delivery models …. Once we fix evolution, we can then take our time to get these other abstractions right!
51. End of Three Themes, Back to SDN SDN not about new mechanisms; can use current Forwarding primitives (e.g., MPLS) State distribution primitives (e.g., flooding as in OSPF) Operator control programs (e.g., BGP on scale-out router) SDN is all about modularity Giving networking the benefits of modular programming Can reliably build more complicated functionality No more designing distributed control protocols Merely define control programs over abstract model Given abstract network, what behavior do you want?
52. Control Plane Research Agenda Create three modular, tractable pieces Nypervisor Network Operating System Design and implement forwarding model Build control programs over abstract models Identify appropriate models for various applications Virtualization, Access Control, TE, Routing,…
53. Implementations vs Abstractions SDN is an instantiation of fundamental abstractions Don’t get distracted by the mechanisms The abstractions were needed to separate concerns Network challenges are now modular and tractable The abstractions are fundamental SDN implementations are ephemeral OpenFlow/NOX/etc. particular implementations
54. Future of Networking, Past of Protocols The future of networking lies in cleaner abstractions Not in defining complicated distributed protocols SDN is only the beginning of needed abstractions Took OS researchers years to find their abstractions First they made it work, then they made it simple Networks work, but they are definitely not simple It is now networking’s turn to make this transition Our task: make networking a mature discipline By extracting simplicity from the sea of complexity…
Editor's Notes
This can be pretty much any forwarding element in networks today.
The short answer is that it solves a bunch of operational problems today
If you don’t do this carefully, just end up with parallel architectures, but even then our framework provides an advantage Applications don’t need to changeInterdomain routing isn’t a constraint on the changeThat’s more than you get out of GENI, or overlays, or other approaches people typically take to innovation.
If you don’t do this carefully, just end up with parallel architectures, but even then our framework provides an advantage Applications don’t need to changeInterdomain routing isn’t a constraint on the changeThat’s more than you get out of GENI, or overlays, or other approaches people typically take to innovation.