ONOS Summit: "SDN, open-source and ONOS"

"SDN, open-source and ONOS" talk by Nick McKeown at ONOS Summit on Dec 9th, 2014

Transcript

1. SDN,  open-­‐source  and  ONOS   Nick  McKeown   Stanford  University  
2. What  is  happening?  
3. 1.  The  rise  of  open-­‐source  soCware   2.  The  rise  of  merchant  switching  chips   3.  The  need  for  operators  to  reduce  cost  and  differenHate  
4. SoCware  in  2014   Smartphone:  Open  75%,  Closed  25%   Browser:  Open  63%,  Closed  37%   Websites:  Open  67%,  Closed  33%     DC  servers:  Open  70%,  Closed  30%   Tablet:  Open  62%,  Closed  38%   Mainframes:  Open  60%,  Closed  40%   Supercomputers:  Open  99%       Open-­‐source  sHll  growing  fast   4  
5. Why  open-­‐source   •  Many  more  developers  and  QA   •  More  agile,  reliable  and  secure   •  Used  where  essenHal  but  “non-­‐differenHaHng”   5  
6. “SoCware  will  eat  the  world”   Marc  Andreessen   6  
7. 1.  The  rise  of  open-­‐source  soCware   2.  The  rise  of  merchant  switching  chips   3.  The  need  for  operators  to  reduce  cost  and  differenHate  
8. 2012:  The  baremetal  switch   Sheet  metal   DRAM   CPU   Power  supply  +  fans   Linux   xChip  
9. Programmable  h/w  +  open-­‐source  +  apps   Sheet  metal   DRAM   CPU   Power  supply  +  fans   Linux   xChip   Open-­‐source   P4   App   App   App   Proprietary   SoCware   Programmable   Hardware   Open-­‐source   SoCware  
10. It’s  happening  fast!  
11. OCP:  Wedge  switch   11   BCM    xChip:  1.2Tb/s  
12. DRAM   CPU   Power  supply  +  fans   Linux   xChip   OpHonal  Remote    API   Open-­‐source   ONL   API/Driver   Open-­‐source   OF-­‐DPA   Open-­‐source   P4   Forwarding  Agent   Open-­‐source   FBOSS,  OVS,  Indigo,  SwLight.   Network  Control  Plane   Open-­‐source   ONOS,  ODL   NOX,  POX,  Ryu   Floodlight,  Beacon   Open-­‐source   ONIE   Boot  Loader   App   App   App   Proprietary   SoCware  
13. 1.  The  rise  of  open-­‐source  soCware   2.  The  rise  of  merchant  switching  chips   3.  The  need  for  operators  to  reduce  cost  and  differenHate  
14. The  Problem   Global  IP  traffic  growing  40-­‐50%  per  year   End-­‐customer  monthly  bill  remains  unchanged   Therefore,  cost  of  ownership  needs  to  reduce  40-­‐50%  per  Gb/s  per  year   But  in  pracHce,  reduces  by  <20%  per  year     $30/month   Hme   Revenue  
15. Simpler  hardware  +  open-­‐source  +  apps   1. Reduce  capital  cost   Move  to  simpler  hardware  +  open-­‐source  control  plane     2. Reduce  operaHonal  cost   Streamline  protocols,  features  and  soCware     3. Increase  price   DifferenHate  with  new  proprietary  soCware  services  
16. The  Internet  was  deliberately  designed  …   To  be  simple  and  streamlined.     To  have  decentralized  control:  Lots  of  individually  controlled  pieces.       Which  led  to  …   •  Explosive  organic  growth  of  the  Internet.   •  A  great  business  for  companies  selling  routers.   simple  and  streamlined   A  great  business  
17. Strategy  1:  VerHcal  integraHon   Proprietary Operating System Proprietary Hardware Proprietary Features “CLI”   Network Management
18. Strategy  2:  High  barrier  to  entry  
19. Number  of  published  Internet  Standards   0   1,000   2,000   3,000   4,000   5,000   6,000   7,000   1969   1979   1989   1999   2009  
20. 50+  million  lines  of  code   Tens  of  billions  of  gates   “Great  business”  triumphed  over  “simple  and  streamlined”.   Proprietary Operating System Proprietary Hardware Proprietary Features
21. SDN  and  NFV  inevitable  because…   1.  Rise  of  Linux.   2.  Rise  of  simpler  servers  and  switches.   3.  NFV:  Rise  of  virtualizaHon.   4.  SDN:  Rise  of  merchant  switching  silicon.     21  
22. SoCware  Defined  Network  (SDN)   Packet   Forwarding       Packet   Forwarding     Packet   Forwarding       Packet   Forwarding       Packet   Forwarding       Control     Control       Control       Control       Control     Global Network Map Remote  Control  Plane   Control Program Control Program Control Program
23. Network  FuncHon  VirtualizaHon  (NFV)   Packet   Forwarding       Packet   Forwarding     Packet   Forwarding       Packet   Forwarding       Packet   Forwarding         Middlebox       Middlebox       Middlebox       Middlebox     Public  Internet    
24. Network  FuncHon  VirtualizaHon  (NFV)   Packet   Forwarding       Packet   Forwarding     Packet   Forwarding       Packet   Forwarding         Middlebox     Public  Internet     VM   VM   VM   VM   VM   VM   Packet   Forwarding       Packet   Forwarding      
25. 25   Server   Switch   Radio   VM   Linux   Linux   Linux   Linux   Programmable   Hardware   Open  Source   SoAware   PIC   Linux   (Remote)  Open  Source  Control  Plane   RouHng,  Traffic  Engineering,   Mobility,  VPN   Proprietary   SoAware   DPI,  Load   Balance,  SPAM   New   Services   Overall  System  Management  
26. Why  ONOS?   1. Network  operators  need  an  open-­‐source  control  plane   (it  is  non-­‐differenHaHng)   2. …with  HA  and  scalability  built-­‐in  from  the  ground-­‐up   3. Which  is  why  we  are  here  today  
27. “Because  there  is  no  army  that  can  hold  back  an   economic  principle  whose  Hme  has  come.”                    John  Donovan,  AT&T  (2014)     27  
28. When  we  look  back  in  20  years…   1.  “SoCware  will  eat  the  world”   –  SDN  and  NFV  are  a  natural  consequence  of  a  bigger  trend.   2.  Network  infrastructure  will  be:     –  Simpler  hardware  +  open-­‐source  infrastructure  +  proprietary  apps   3.  Network  operators  will  have  developed  and  will  own  proprietary   soCware   4.  Standards  will  sHll  mater,  but  with  diminished  value   28  
29. <The  End>   29