Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Network Virtualization with VMware NSX

14,315 views

Published on

This presentation was given at the Boston VMUG on Tuesday, October 29, 2103.

Published in: Technology

Network Virtualization with VMware NSX

  1. 1. Network Virtualization with VMware NSX Scott Lowe, VCDX Engineering Architect Networking & Security BU, VMware, Inc. http://blog.scottlowe.org 1
  2. 2. Before we get started § Get involved! Audience participation is encouraged and requested. § If you use Twitter, feel free to tweet about this session (use @MyVMUG or @BostonVMUG) § 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 2
  3. 3. Your name is familiar... 3
  4. 4. Networking can be a barrier to the software-defined data center Software Defined Data Center VDC SOFTWARE-DEFINED DATACENTER SERVICES § Provisioning is slow § Placement is limited § Mobility is limited § Hardware dependent § Operationally intensive Compute Virtualization Any Physical Infrastructure 4
  5. 5. How can we solve this challenge? 5
  6. 6. Many technologies are claiming to be able to address this challenge SR-IOV Open vSwitch SDN controllers STT Network overlays LISP VXLAN TRILL Merchant silicon SDN OpenFlow Fabrics NVGRE OpenStack Networking Northbound APIs 6
  7. 7. By themselves, these technologies don’t change the operational model. 7
  8. 8. To change the operational model, what’s needed is the right abstraction. 8
  9. 9. Let’s look at compute virtualization § 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. 9
  10. 10. Along comes VMware and the VM § VMware introduced a new abstraction: the virtual machine (VM) 10
  11. 11. 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 § VMs could be deployed programmatically, which enables self-service tools and methodologies § § Success encouraged adoption; adoption encouraged ecosystem development (positive feedback loop) 11
  12. 12. So what does this have to do with network virtualization? 12
  13. 13. What’s needed is the right abstraction § 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
  14. 14. What is a virtual network? Application Application Workload Application Workload Workload L2, L3, L4-7 Network Services x86 Environment Software Virtual Machine Virtual Machine Virtual Machine Server Hypervisor Virtual Network Decoupled Requirement: x86 Virtual Network Virtual Network Network Hypervisor Requirement: IP Transport Hardware General Purpose Server Hardware (Dell, HP, IBM, OpenCompute, Quanta) General Purpose IP Hardware (Arista, Cisco, HP, Juniper, Accton) 14
  15. 15. Networks aren’t just about connectivity § A virtual network must be more than just connectivity § It has to also provide virtual network services: Routing § Firewalling § Load balancing § VPNs § § It has to be extensible, allowing technology partners to “plug into” the virtual network to bring additional services and functionality to bear for customers 15
  16. 16. Key functions of a virtual network Virtual Virtual Network Operations 1. Decouples 2. Reproduces 3. Automates Physical Hardware independence Physical No change to network from end host perspective Cloud Operations Operational benefits of virtualization 16
  17. 17. VMware NSX provides the right abstraction—the virtual network—to enable operational change that addresses pain points and meets business needs. 17
  18. 18. Networking can be a barrier to the software-defined data center Software Defined Data Center VDC SOFTWARE-DEFINED DATACENTER SERVICES § Provisioning is slow § Placement is limited § Mobility is limited § Hardware dependent § Operationally intensive Compute Virtualization Any Physical Infrastructure 18
  19. 19. Network virtualization addresses this challenge Software Defined Data Center VDC SOFTWARE-DEFINED DATACENTER SERVICES § Programmatic provisioning § Place any workload anywhere § Move any workload anywhere § Decoupled from hardware § Operationally efficient Network Virtualization Compute Virtualization Any Physical Infrastructure 19
  20. 20. Looking a bit deeper at VMware NSX 20
  21. 21. Some technologies you might find helpful § Linux § Open vSwitch (OVS) § OpenFlow § OVSDB § Cloud management systems vCloud Automation Center (vCAC) § OpenStack § CloudStack § 21
  22. 22. Questions & answers 22
  23. 23. Thank you Scott Lowe slowe@vmware.com 23

×