Surviving the SDN Wars. Curt Beckmann Chair of Forwarding Abstractions WG, ONF and EMEA CTO

Transcription

1 Surviving the SDN Wars Curt Beckmann Chair of Forwarding Abstractions WG, ONF and EMEA CTO 2014

2 Sequence Defining SDN and NFV Last 4 years Last 6 months What happens next for SDN?

3 Defining SDN and NFV

4 Technical Definition of Software Defined Networking A network where the control and data planes have been separated.

5 Technical Definition of Software Defined Networking A network where the control and data planes have been separated. WRONG QUESTION

6 *Why* SDN?

7 Why SDN? What is the motivation? The old model was not working in new (cloud) environment Network boxes do not have enough information Innovation is slow Leading vendors are in control, but don t want big changes

8 Why SDN? What is the motivation? The old model was not working in new (cloud) environment Network boxes do not have enough information Innovation is slow Leading vendors are in control, but don t want big changes A better definition An open and interoperable network architecture / market ecosystem that allows control plane products to be purchased independently of data plane products.

9 Software-Defined Network Framework Management and Orchestration Application e.g., OpenStack (i.e., Network Virtualization) plugins to network OpenStack Control OpenDaylight A basic conceptual structure from which SDN solutions can be built Example OpenFlow Network Virtualization Physical Infrastructure Compute Storage Brocade Communications Systems, Inc. Company Proprietary Information

10 What is Network Functions Virtualisation (NFV)? Movement to transition away from: specialized (expensive and locked) hardware (inflexible) to a software (flexible) model on common (inexpensive, open) servers

11 European Telecom Standards Institute (ETSI) NFV White Paper ( Classical Network Appliance Approach Message Router CDN Session Border Controller WAN Acceleration Orchestrated, automatic & remote install DPI Firewall Carrier Grade NAT Tester/QoE Monitor Standard High Volume Servers SGSN/GGSN PE Router BRAS Radio/Fixed Access Network Nodes Fragmented non-commodity hardware. Physical install per appliance per site. Hardware development large barrier to entry for new vendors, constraining innovation & competition. Figure 1: Vision for Network Functions Virtualisation Standard High Volume Storage Standard High Volume Ethernet Switches Network Functions Virtualisation Approach Brocade Communications Systems, Inc. Company Proprietary Information

12 Software-Defined Networking MULTIPLE DEFINITIONS OF SCOPE SDN is Still Evolving Brocade Communications Systems, Inc. Company Proprietary Information

13 Last 4 Years

14 Major Milestones OPNFV OpenDaylight OpenFlow OpenStack 2010 ONF founded Mar 2011 Nicira bought July 2012 NFV Sep 2012 Mar 2013 Oct 2014

15 ONF / OpenFlow Timeline Network Functions Virtualisation (NFV) (GOOG builds OF DC-to-DC network) (GOOG presos OF Net) (VMW buys Nicira) (OpenDaylight Project / Hydrogen Release) Hybrid WG, Config WG, Mkt Ed WG & Test WG all get set up Future DG FPMODS charter (BRCD buys Vyatta) FAWG (ODL TTP) ONF founded, Ext WG Google shares ideas with ONF TAG; ONF responds with the OpenFlow Future DG Future DG submits charter for FPMODS WG as ONF slows 1.4 ONF approves FAWG, re-instates: working code before spec policy ArchDT/WG, base+ext specs, End Hybrid WG Config WG adds OAM Add MigWG, OTWGs FAWG sends draft doc for review New WMDG, New NBI Chipmakers Advisory Board st plugfest (1.0 only) 2nd plugfest (1.0 & 1.2) 3rd plug Adds 1.3 4th plug All 1.3 OF1.1 released (no working code) OF1.2 released (no working code) OF1.3 released (no working code) First test lab approved, pilot certification starts OF1.4 working code under development 2013 Brocade Communications Systems, Inc. CONFIDENTIAL

16 Who is OpenDaylight? (The Corporate View) PLATINUM MEMBERS GOLD MEMBERS SILVER MEMBERS 2014 Brocade Communications Systems, Inc. Company Proprietary Information

17 Controller Network application, orchestration and services User Interfaces Network Applications, Orchestration, and Services OpenDaylight APIs (Rest) Controller platform Network Service Functions Platform Services Extensions Southbound interfaces & protocols OpenFlow Service Abstration Layer (SAL) Other Standard Protocols (ONE, IETF, ) Vendor-Specific Interfaces Data plane elements (virtual switches, physical device interfaces) 2014 Brocade Communications Systems, Inc. Company Proprietary Information

18 Tunnel Tunnel Software-Defined Networking: Two Approaches Hardware Underlay Software Overlay SDN Controller SDN Controller OpenFlow Logical Network vswitch vswitch Physical Network VM VM VM Physical Network VM VM VM Brocade Communications Systems, Inc. Company Proprietary Information

19 OpenStack Powered Cloud Solutions Ecosystem Delivering Enterprise-class Cloud Deployments Support OPENSTACK ECOSYSTEM Software Hardware Certified, Managed, Supported Stacks Enterprise-grade OpenStack Distro Raw OpenStack Open Source System Integration Compute Network Storage 2014 Brocade Communications Systems, Inc. Company Proprietary Information

20 Data Center : Virtualize the Network INTERNET Replace hardware networking with vrouter-based virtual networking Brocade Communications Systems, Inc. Company Proprietary Information

21 ONF Membership Well over 100 member firms 2014 Brocade Communications Systems, Inc. CONFIDENTIAL For internal Use Only 21

22 OpenFlow Disillusionment 2014 Brocade Communications Systems, Inc. CONFIDENTIAL For internal Use Only 22

23 Last 6 Months

24 Open Source Config Mgmt Software 2014 Brocade Communications Systems, Inc. CONFIDENTIAL For internal Use Only 24

25 OFS1.3: Multiple tables Plus group tables, actions for IPv6 support, MPLS, etc Flow Entry Matching Fields Actions Stats Packet counters, byte counters, and etc Forward packet to a port list Add/remove/modify VLAN Tag Drop packet Send packet to the controller ADDED A GOTO TABLE N action Multiple tables means multiple entries can match. Flow definition and end-to-end actions no longer fits nicely in a single flow entry, or a single message OpenFlow-Enabled Router Control Plane OpenFlow Client Data Plane Flow Table Flow Table Flow Table Flow Table OpenFlow Switch protocol Flow Table Flow Table Flow Table OpenFlow Controller Layer 2 Layer 3 Ingress Port MAC DA MAC SA EtherType VLAN ID P-bits IP Src IP Dst IP Protocol IP DSCP TCP/UDP src port TCP/UDP dst port Brocade Communications Systems, Inc. Company Proprietary Information

26 OpenDaylight TTP Project 2014 Brocade Communications Systems, Inc. CONFIDENTIAL For internal Use Only 26

27 ONF Forwarding Abstractions (my) WG TTP Spec 2014 Brocade Communications Systems, Inc. CONFIDENTIAL For internal Use Only 27

28 Another important change Early OpenFlow has tried to do two things Decouple control from data plane Make the data plane programmable (this is separate) First (decouple) is a little bit hard, but useful and doable Second is much harder, and benefit is less clear Change has been to focus on these one at a time New effort started to work on #2 as a separate, long term effort

29 What comes next for SDN?

30 Early Takeaways: OpenFlow has moved slowly OpenDaylight was unknown No Unified Open SDN architecture yet Gartner trough comes from overpromising, SDN-washing Yet ONF membership grows No alternative open low level interface has appeared But no question that controller convergence needed And no other controller maturing like ODL Yet we know that Service Providers and Web2.0 companies have a strategic need This need is a light to steer by (it provides the main direction) But the industry is maturing. Observers have been forming more realistic expectations

31 Second Round Takeaways: Relative convergence down the stack (OF, ODL, YANG, NETCONF, REST) Growth at the top of the stack (Puppet, Chef, Ansible, etc) While the tent continues to grow (Campus, WAN, Optical) Vendors position proprietary as Open ; proprietary has time-to-market advantage SPs and Web2.0 largely holding firm on strategic commitment to Open SDN/NFV

32 Anticipated Shifts: Visible PoCs become more relevant, compelling Ability to create interoperable SDN improves dramatically Common understanding of Open v Interoperable grows Ability to deploy useful SDN without big dev budget emerges

33 THANK YOU