Upgrade to Pro — share decks privately, control downloads, hide ads and more …

How to Get Started with Network Virtualization ...

How to Get Started with Network Virtualization (Columbus)

This presentation was given on May 21, 2013 at the Central OH VMUG User Conference, and discusses network virtualization in the context of why it matters, how it will affect IT pros, and some key technologies that are involved.

Scott Lowe

May 21, 2013
Tweet

More Decks by Scott Lowe

Other Decks in Technology

Transcript

  1. How to Get Started with Network Virtualization Why it matters,

    how it will affect you, and some key technologies to know 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 #COVMUG) •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. •What is network virtualization? •How is it similar to compute

    virtualization? •Why does network virtualization matter to me? •How does network virtualization change my job? •How does network virtualization affect my networking group? •What are some key technologies I should know? •What are the key components of network virtualization? Agenda
  4. •A combination of technologies to support the creation of virtual

    (or logical) networks •A virtual network is a network that can be created, modified, and destroyed without any interaction with physical network assets •Network virtualization: •Decouples virtual networks from physical networks •Reproduces the physical network faithfully in the virtual network •Automates the creation of virtual networks programmatically What is network virtualization?
  5. •It works on any physical hardware (only requires an IP

    fabric) •Decouples virtual (logical) networks from underlying physical networks (hardware independence) •Does not require changes to applications/workloads in order to support network virtualization •Doesn’t preclude the use of hardware support to enhance the virtualization functionality (e.g., hardware offloads) How is it similar to compute virtualization?
  6. •Other than jumping on the buzzword bandwagon? •It makes it

    easier to provision new logical networks •It makes it faster to provision new logical networks •Logical networks can be quickly created, modified, and deleted as needed without involving the physical network •It brings network functionality closer to the workloads Why does network virtualization matter to me?
  7. •It actually simplifies your job as a vSphere admin •You'll

    be responsible for creating, modifying, and deleting virtual (logical) networks, typically from within your cloud management system •You are abstracted away from the specific technical details of how the network provides the functionality you need for your workloads How will network virtualization change my job?
  8. •It actually simplifies their job •The networking group no longer

    needs to worry about workload provisioning tasks •Instead, they can focus on the key values of the network in moving data from point A to point B •Performance •Reliability •Cost-effectiveness How will network virtualization affect my networking group?
  9. •Edge virtual switch •Southbound communications protocols •Northbound APIs •Centralized controller

    •Encapsulation protocols What are the key components of network virtualization?
  10. •Open vSwitch (OVS) •OpenFlow •OVSDB (and possibly OF-Config) •Network encapsulation

    protocols (STT, VXLAN, GRE) What are some key technologies I should know?