A Deeper Look at Network Virtualization

This presentation, given in Charlotte in June 2013, takes a look at some of the key components and technologies involved in a network virtualization solution.

Transcript

1. A Deeper Look at Network Virtualization Peeling back the covers to look at the key components in network virtualization Scott Lowe, VCDX 39 vExpert, Author, Blogger, Geek http://blog.scottlowe.org / Twitter: @scott_lowe
2. Before we start •Get involved! Audience participation is encouraged and requested. •If you use Twitter, feel free to tweet about this session (use @MyVMUG or hashtag #CLTVMUG) •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. Your name is familiar...
4. •Quick review of network virtualization •Key components of network virtualization •VMware NSX: VMware’s implementation of network virtualization Agenda
5. •Network virtualization is an abstraction layer that decouples logical (virtual) networks from the underlying physical networks •Benefits include: •Programmatic access to network provisioning and policy •Hardware independence •Workload mobility Quick review of network virtualization
6. What makes up a network virtualization solution?
7. What makes up a network virtualization solution?
8. What makes up a network virtualization solution?
9. What makes up a network virtualization solution?
10. What makes up a network virtualization solution?
11. What makes up a network virtualization solution?
12. What makes up a network virtualization solution?
13. L2 L3 Virtual Network L2 What makes up a network virtualization solution?
14. L2 L3 Virtual Network L2 What makes up a network virtualization solution? CMP
15. •Decoupled control/data planes •Centralized knowledge/control of the network topology •Programmatic access •Virtualized network services •Network traffic isolation mechanism Key components of network virtualization
16. •This is the classical definition of SDN (software-defined networking) •Most common protocol used here is OpenFlow •Requires a programmable virtual switch at the edge; most commonly used here is Open vSwitch (OVS) •OVS is an open source, highly programmable virtual switch that supports OpenFlow and other protocols •Originally started by Nicira, now contributed to by many companies (including Citrix and Cisco, among others) Decoupled control/data planes
17. •This could be considered the role of an “SDN controller” •Computes/calculates/maintains the overall network topology •Communicates with programmable virtual edge switch •OpenFlow alone can’t provide this communication •Need configuration data as well (OVSDB, OF-Config) •Must provide high availability, redundancy, scale-out support Centralized knowledge/control of the network topology
18. •Network provisioning needs to happen in conjunction with server/workload provisioning •Solution must provide APIs (typically REST APIs) northbound •Network virtualization APIs are consumed by CMP/CMS •OpenStack Networking (aka “Quantum”) •CloudStack •vCloud? Programmatic access
19. •Commonly referred to as network functions virtualization (NFV) •Virtualized firewalls, load balancers, etc. •vCNS Edge is one such example Virtualized network services/ functions
20. •Network encapsulation protocol is typically used here •Provides address space isolation •Decouples logical networks from VLAN space •Isolates logical traffic from physical network •Protocols used here include VXLAN, STT, GRE Network traffic isolation mechanism
21. VMware NSX
22. Questions & answers
23. Thank you! Don’t forget to complete the survey in your program guide & provide feedback to your VMUG leaders on this session.