Evolution And Challenges Of Software Defined Networking
EVOLUTION AND CHALLENGES OF SOFTWAREDEFINED NETWORKINGÁngel Leonardo ValdiviesoLorena Isabel Barona{angevald,lorebaro}@ucm.esGroup of Analysis, Security and SystemsDepartment of Software Engineering and Artificial IntelligenceComplutense University of MadridEvolution and Challenges of Software Defined Networking
Outline1. Introduction2. Evolution of Software Defined Networking3. SDN Research Initiatives4. SDN Challenges5. ConclusionsEvolution and Challenges of Software Defined Networking2
Introduction1. IntroductionGlobal Internet IP Traffic by Device Type2. Evolution ofSDN3. SDN ResearchInitiatives4. SDN Challenges5. ConclusionsEvolution and Challenges of Software Defined Networking3
Introduction1. IntroductionGlobal Consumer IP Traffic2. Evolution ofSDN3. SDN ResearchInitiatives4. SDN Challenges5. ConclusionsEvolution and Challenges of Software Defined Networking4
Introduction1. Introduction2. Evolution ofSDN3. SDN ResearchInitiativesNew requirements: Easy support to implement custom network services Changing traffic patterns dynamically4. SDN Challenges5. Conclusions Support to public and private cloud services Intelligent network management of increasing bandwidth –Big data supportThe networks are ready to support this newrequeriments?Evolution and Challenges of Software Defined Networking5
Introduction1. IntroductionLimitations of Current Networking Technologies:2. Evolution ofSDN3. SDN ResearchInitiatives4. SDN ChallengesCONTROL PLANECONTROL PLANEDATA PLANEDATA PLANE5. Conclusions Protocols solve a specific problem (ACL, VLAN, QoS,Firewall, NIDS, authentication ) complexity Need to configure network devices individually (using CLI) Static nature of networks in contrast to the today s dynamicenvironment (server virtualization, distributed applications) Vendor dependence to support new capabilities and servicesEvolution and Challenges of Software Defined Networking6
Evolution of SDN1. Introduction3. SDN ResearchInitiatives4. SDN ChallengesActive Networks:5. Conclusions (2010 )(2000-2010)(1990 – 2000)2. Evolution ofSDNSeparation Control-Data:Openflow and NOS: Smart Packets Tempest Openflow Protocol SwitchWare ForCES NOX, Beacon Calvert RCP Procera Ethane Open the controlnetwork through aprogramminginterface (networkAPI)Programming models:Node OperatingSystem (NodeOS) Not offer practicalperformance andsecurity Evolution and Challenges of Software Defined Networking Open interfacebetween control anddata planesLogically centralizedcontrol of the networkDistributed statemanagement Difficult implementationin production networks(compatible hardware) Interface build onalready supportedtechnology(flowtables)Vision of a NetworkOperating System(NOS)Difficult to enablesophisticated middleboxfunctionality7
Evolution of SDN1. Introduction2. Evolution ofSDNSoftware Defined Networking is an emerging network architecture wherenetwork control is decoupled from forwarding and is directlyprogrammable.3. SDN ResearchInitiatives4. SDN Challenges5. ConclusionsEvolution and Challenges of Software Defined Networking8
Evolution of SDN1. Introduction2. Evolution ofSDNSoftware Defined Networking is an emerging network architecture wherenetwork control is decoupled from forwarding and is directlyprogrammable.3. SDN ResearchInitiatives4. SDN Challenges5. ConclusionsSource: Open Networking Foundation (ONF)Evolution and Challenges of Software Defined Networking9
SDN Research Initiatives1. Introduction2. Evolution ofSDNVirtualization & NOSSimulation3. SDN ResearchInitiatives4. SDN Challenges5. ConclusionsTestbedsEvolution and Challenges of Software Defined NetworkingMultimedia10
SDN Research Initiatives1. IntroductionVirtualization2. Evolution ofSDN3. SDN ResearchInitiatives4. SDN Challenges5. ConclusionsEvolution and Challenges of Software Defined Networking11
SDN Research Initiatives1. IntroductionVirtualization: FlowVisor2. Evolution ofSDNAPP3. SDN ResearchInitiatives4. SDN ChallengesFRENETIC APPPROCERA 5. ConclusionsNOXBeacon ow ProtocolFlowtableOpenFlow SwitchFlowtableDATA PLANEEvolution and Challenges of Software Defined NetworkingOpenFlow SwitchFlowtableOpenFlow Switch12
SDN Research Initiatives1. IntroductionNetwork Operating System NOS2. Evolution ofSDN3. SDN ResearchInitiatives4. SDN Challenges5. ConclusionsProceraSwitch, Virtual Switch, RouterEvolution and Challenges of Software Defined Networking13
SDN Research Initiatives1. Introduction2. Evolution ofSDNSimulation: Mininet - An Instant VirtualNetwork on your Laptop3. SDN ResearchInitiatives4. SDN Challenges5. ConclusionsSource: B. Lantz, B. Heller, and N. McKeown, “A Network in a Laptop: Rapid Prototyping for Software-Defined Networks”Evolution and Challenges of Software Defined Networking14
SDN Research Initiatives1. Introduction2. Evolution ofSDNTestbeds: Global Environment for NetworkInnovation (GENI)3. SDN ResearchInitiatives4. SDN Challenges5. ConclusionsEvolution and Challenges of Software Defined Networking15
SDN Research Initiatives1. Introduction2. Evolution ofSDNTestbeds: OpenFlow in EuropeLinking Infrastructure and Applications (OFELIA)3. SDN ResearchInitiatives4. SDN Challenges5. ConclusionsEvolution and Challenges of Software Defined Networking16
SDN Research Initiatives1. IntroductionMultimedia: SDN helps to improve the QoE experienceSDN Path Optimization SystemsArchitecture: QoS Matching andOprtimization Function (QMOF)and Path Assignment Function(PAF)2. Evolution ofSDN3. SDN ResearchInitiatives4. SDN Challenges5. ConclusionsIf the quality of the network isdegraded, the system can react anddynamically modify the pathparameters of the networkprioritizing the users configurationSource: A. Kassler, L. Skorin-Kapov, O. Dobrijevic, “Towards QoE-driven Multimedia Service Negotiation and Path Optimization with SoftwareDefined Networking,”Evolution and Challenges of Software Defined Networking17
SDN Research Initiatives1. Introduction2. Evolution ofSDNMultimedia: Fast Recovery of a link failureSDN improves the recovery time from a link failure using an alternative path3. SDN ResearchInitiativesThe system uses the restorationand protection mechanism.4. SDN ChallengesIn restoration system, thecontroller calculates andestablishes an alternative pathwhen a path failure signal isreceived.5. ConclusionsIn protection system, the controlleranticipates a failure and calculatestwo disjoint paths (working andprotected)The experiments show a recovery time of less than 50 ms for carrier-gradenetwork.Source: S. Sharma, D. Staessens, D. Colle, M. Pickavet, and P. Demeester, “A Demonstration of Fast Failure Recovery in Software DefinedNetworking,”Evolution and Challenges of Software Defined Networking18
SDN ChallengesModeling and Performance:1. Introduction2. Evolution ofSDNHow many controllers needed and the localization of thesecontrollers?3. SDN ResearchInitiatives4. SDNChallenges SDN establishes the separation of controland data planes, but doesn’t necessarilyorder the existence of a single controller. Control plane may have a singlecontroller, a set of controllers of even anydynamic topology5. Conclusions The number and position of the controllers depends on desiredreaction bounds, metric choice and the network topologyEvolution and Challenges of Software Defined Networking19
SDN ChallengesModeling and Performance:1. Introduction2. Evolution ofSDNHow to select the appropriate NOS and how to measure itsperformance?3. SDN ResearchInitiatives4. SDNChallenges5. Conclusions The performance of the controller depends directly of programminglanguage (C , Java, Python) and the development environment It is necessary to establish a balance between high performance andthe productivity of developers (a developer friendly language)Evolution and Challenges of Software Defined Networking20
SDN ChallengesNOS: How to measure its performance?1. Introduction2. Evolution ofSDN3. SDN ResearchInitiatives4. SDNChallenges5. ConclusionsHow many datapath requestcan the controller handle persecond?How fast the controllerresponds to datapathrequest?Source: D. Erickson, “The Beacon Openflow Controller,”Evolution and Challenges of Software Defined Networking21
SDN ChallengesResilience and Recovery:1. Introduction2. Evolution ofSDN3. SDN ResearchInitiatives4. SDNChallenges5. ConclusionsA failure of the controller can negatively compromise resilienceof the whole network. The failure can be fired by abruptly aborting of a NOS process, anunexpected error of the application or a DDoS attack. Openflow establishes the configuration of one or more backup controllers,but doesn’t provide a coordination mechanism between them.The project CPRecovery permits thereplication between primary and secondarySDN controller in two phases.The replication phase acts during normalfunctioning of the controller and sendregular updates to the backup controller. Therecovery phase acts during a failure state ofthe primary controller and starts the backupcontroller as a main controller.Source:P. Fonseca, R. Bennesby, E. Mota, and A. Passito, “A Replication Component for Resilient OpenFlow-based Networking,”Evolution and Challenges of Software Defined Networking22
SDN ChallengesConvergence and Integration:1. Introduction2. Evolution ofSDN3. SDN ResearchInitiatives4. SDNChallenges5. ConclusionsIntegration with legacy networks (actual Internet infrastructure) The equipment could be upgraded or even replaced to support Openflow High costly network re-engineering OpenFlow is unable to handle ormanage legacy equipment it isdifficult to connect two-Openflowenvironments with legacy networks. It is necessary a coordinationbetween SDN equipment andlegacy infrastructureSource:F. Farias, J. Salvatti, E. Cerqueira, “A Proposal Management of the Legacy Network Environment Using Openflow Control Plane,”Evolution and Challenges of Software Defined Networking23
Conclusions1. Introduction2. Evolution ofSDN3. SDN ResearchInitiatives SDN can be expanded beyond actual match/action paradigm. For example,it could integrate middleboxes or programmable custom packet processors. This integration could offers new services like on the fly encryption,transcoding, or traffic classification. This require coordination, consensus andvendor support. In control plane, the composing and coupling of heterogeneous componentsare still difficult. For example, compose application using Beacon, POX orFloodlight simultaneously. Finally, remark that SDN is a tool. The research community can use this toolto create new innovative services and applications.4. SDN Challenges5. ConclusionsEvolution and Challenges of Software Defined Networking24
Thanks for your time andattention !Ángel Leonardo Valdiviesoangevald@ucm.esGroup of Analysis, Security and SystemsDepartment of Software Engineering and Artificial IntelligenceComplutense University of MadridEvolution and Challenges of Software Defined Networking25
Evolution and Challenges of Software Defined Networking Evolution of SDN 8 Software Defined Networking is an emerging network architecture where network control is decoupled from forwarding and is directly programmable. 3. SDN Research Initiatives 1. Introduction 5. Conclusions 4. SDN Challenges 2. Evolution of SDN
Evolution 2250e and Evolution 3250e are equipped with a 2500 VApower supply. The Evolution 402e and Evolution 600e are equipped with a 4400 VA power supply, and the Evolution 403e and Evolution 900e house 6000 VA power supplies. Internal high-current line conditioning circuitry filters RF noise on the AC mains, as well as
Chapter 4-Evolution Biodiversity Part I Origins of life Evolution Chemical evolution biological evolution Evidence for evolution Fossils DNA Evolution by Natural Selection genetic variability and mutation natural selection heritability differential reproduct
The process of software evolution is driven by requests for changes and includes change impact analysis, release planning and change implementation. Lehman’s laws, such as the notion that change is continuous, describe a number of insights derived from long-term studies of system evolution. Chapter 9 Software evolution 22
tres tipos principales de software: software de sistemas, software de aplicación y software de programación. 1.2 Tipos de software El software se clasifica en tres tipos: Software de sistema. Software de aplicación. Software de programación.
that depended on interactions between a participant’s perception of religion, science, medicine, and a host of . Muslims, Culture, Evolution and religion, Evolution and medicine, Evolution acceptance, Evolution rejection Background . to elicit a
important ideas in modern biology What is the evidence for evolution? Evolution in action: two case studies 22.4 The process of evolution by natural selection 22.3 Common myths about natural selection and adaptation 22.5 The pattern of evolution: species have changed and are related 22.2
Krell Current Mode circuitry, the Evolution 2250e and Evolution 3250e deliver per-formance that was previously reserved for products costing far more. Featuring a 2,500 VA power transformer the Evolution 2250e and Evolution 3250e are powerhous-es. Power output of 250 W per chan-nel into 8 ohms and 500 W per channel
CCSS English/Language Arts Standards Reading: Informational Text Second Grade Key Ideas and Details Craft and Structure Integration of Knowledge and Ideas. Indicator Date Taught Date Retaught Date Reviewed Date Assessed Date Re-Assessed CCSS.ELA-LITERACY.W.2.1 Write opinion pieces in which they introduce the topic or book they are writing about, state an opinion, supply reasons that support .
