SDN, Network Virtualization, and the Right Abstraction

2,003 views
1,865 views

Published on

This presentation, given at the 2013 Indianapolis VMware User Conference on July 25, discusses the relationship between SDN and network virtualization, and highlights the value of the right abstraction in network virtualization.

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,003
On SlideShare
0
From Embeds
0
Number of Embeds
7
Actions
Shares
0
Downloads
182
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

SDN, Network Virtualization, and the Right Abstraction

  1. 1. Scott Lowe, VCDX Engineering Architect Network & Security Business Unit, VMware, Inc. SDN, Network Virtualization, and the Right Abstraction 1
  2. 2. Before we get started 2 §Get involved! Audience participation is encouraged and requested. §If you use Twitter, feel free to tweet about this session (use @MyVMUG, @IndyVMUG, or hashtag #DemoDays) §I encourage you to take photos or videos of today’s session and share them online §This presentation will be made available online after the event
  3. 3. Your name is familiar... 3
  4. 4. Virtualization in networking isn’t new 4 §Virtual LANs (VLANs) §Virtual private networks (VPNs) §Virtual routing and forwarding (VRF) §MPLS §SPB/PBB/QinQ §Virtual device contexts (VDCs)
  5. 5. So why are we talking about network virtualization? 5
  6. 6. Looking at compute virtualization 6 §Multiple forms of virtualization existed in x86-based computing before VMware § 80386 “protected mode” § Virtual memory § Application virtual machines (e.g., JVM) § Remote presentation (X Window System) §These were all important developments, but... None of them had the power to change the operational model.
  7. 7. How compute virtualization changed with VMware 7 §VMware introduced a new abstraction: the virtual machine (VM)
  8. 8. Why is the VM important? §The VM abstraction encompassed other virtualization technologies, but enabled operational change §Operational change enabled customers to address pain points (speed of provisioning, for example) § Now users could easily create VMs, destroy VMs, clone VMs, start/stop/pause VMs § VMs encouraged more standardized configurations §Success encouraged adoption; adoption encouraged ecosystem development (positive feedback loop) 8
  9. 9. So what does this have to do with network virtualization? 9
  10. 10. A plethora of networking technologies are out there 10
  11. 11. A plethora of networking technologies are out there 10 Merchant silicon OpenFlow Northbound APIs Open vSwitch Network overlays SDN SDN controllers OpenStack Networking Fabrics STT VXLAN NVGRE SR-IOV TRILL LISP
  12. 12. What’s needed is the right abstraction 11 §The right abstraction—the virtual network—lets us change the operational model §Changing the operational model brings benefits: § Greater speed and agility § Lower operational overhead § Decreased capital expenditures § But...it’s really about greater speed & agility
  13. 13. VMware NSX provides the right abstraction—the virtual network—to enable operational change that addresses pain points and meets business needs. 12
  14. 14. Looking a bit deeper at VMware NSX 13
  15. 15. Questions & Answers 14
  16. 16. Please don’t forget to provide feedback to the VMUG leaders on today’s sessions! Thank You 15

×