SDN in Real World-Google's Story The industries were skeptical whether SDn was possible Google had big problems High financial cost managing their datacenters hardware and software upgrade, over provisioning fault tolerant), manage large backup traffic, time to manage individual switch, and a lot of men power to manage the infrastructure Delay caused by rebuilding connections after link failure Slow to rebuild the routing tables after link failure Difficult to predict what the new network may perform Google went a head and implemented SDn Built their hardware and wrote their own software for their internal datacenters Surprised the industries when google announced sdn was possible in production How did they do it? Read"B4: Experience with a Globally-Deployed Software Defined WAN, ACM Sigcomm 2013
SDN in Real World – Google’s Story • The industries were skeptical whether SDN was possible. • Google had big problems: • High financial cost managing their datacenters: Hardware and software upgrade, over provisioning (fault tolerant), manage large backup traffic, time to manage individual switch, and a lot of men power to manage the infrastructure. • Delay caused by rebuilding connections after link failure. • Slow to rebuild the routing tables after link failure. • Difficult to predict what the new network may perform. • Google went a head and implemented SDN. • Built their hardware and wrote their own software for their internal datacenters. • Surprised the industries when Google announced SDN was possible in production. • How did they do it? • Read “B4: Experience with a Globally-Deployed Software Defined WAN”, ACM Sigcomm 2013
The origin of sdn Martin Casado 2006: Martin Casado a phd student at stanford and team propose a clean-slate security architecture(sane which defines a centralized control of security in stead of at the edge as normally done. Ethane generalizes it to all access policies The idea of software defined Network is originated from Open Flow project (ACM SIGCOMM 2008) 2009: Stanford publishes Open Flow V1.0.0 specs June 2009 Martin Casado co-founds nicira March 2011: Open Networking Foundation is formed Oct 2011: First Open Networking Summit. Many Industries ( Juniper, Cisco announced to incorporate. July 2012: VMware buys Nicira for $1. 26B Lesson Learned: Imagination is the key to unlock the power of possibilities
The Origin of SDN • 2006: Martin Casado, a PhD student at Stanford and team propose a clean-slate security architecture (SANE) which defines a centralized control of security (in stead of at the edge as normally done). Ethane generalizes it to all access policies. • The idea of Software Defined Network is originated from OpenFlow project (ACM SIGCOMM 2008). • 2009: Stanford publishes OpenFlow V1.0.0 specs. • June 2009: Martin Casado co-founds Nicira. • March 2011: Open Networking Foundation is formed. • Oct 2011: First Open Networking Summit. Many Industries (Juniper, Cisco announced to incorporate. • July 2012: VMware buys Nicira for $1.26B. • Lesson Learned: Imagination is the key to unlock the power of possibilities. Martin Casado
What is Open Flow? Application A Application B Control Plane (network OS) Open Flow Protocols Data plane
OpenFlow Protocols Data Path (Hardware) Data Plane Control Path OpenFlow Control Plane (Network OS) Application A Application B What is OpenFlow?
What is Open Flow? Allow separation of control and data planes Centralization of control ·F| ow based contro Takes advantage routing tables in ethernet switches and routers SDN is not OpenFlow SDN is a concept of the physical separation of the network control plane from the forwarding plane, and where a control plane controls several devices Open Flow is communication interface between the control and data plane of an SDn architecture Allows direct access to and manipulation of the forwarding plane of network devices such as switches and routers, both physical and virtual Think of as a protocol used in switching devices and controllers interface
What is OpenFlow? • Allow separation of control and data planes. • Centralization of control. • Flow based control. • Takes advantage routing tables in Ethernet switches and routers. • SDN is not OpenFlow. • SDN is a concept of the physical separation of the network control plane from the forwarding plane, and where a control plane controls several devices. • OpenFlow is communication interface between the control and data plane of an SDN architecture. • Allows direct access to and manipulation of the forwarding plane of network devices such as switches and routers, both physical and virtual. • Think of as a protocol used in switching devices and controllers interface