Network Virtualization With Vmware NSX: Scott Lowe, VCDX Engineering Architect Networking & Security Bu, Vmware, Inc

Download as pdf or txt
Download as pdf or txt
You are on page 1of 23

Network Virtualization with VMware NSX

Scott Lowe, VCDX


Engineering Architect
Networking & Security BU, VMware, Inc.
http://blog.scottlowe.org
1
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
Your name is familiar...

3
Networking can be a barrier to the
software-defined data center
Software Defined Data Center
§ Provisioning is slow
VDC
§ Placement is limited
§ Mobility is limited
§ Hardware dependent
SOFTWARE-DEFINED
DATACENTER SERVICES

§ Operationally intensive

Compute Virtualization

Any Physical
Infrastructure

4
How can we solve this challenge?

5
Many technologies are claiming to be
able to address this challenge

SR-IOV
Open vSwitch
SDN controllers
STT

Network overlays TRILL


Merchant silicon
VXLAN LISP
SDN Fabrics
OpenFlow
NVGRE
OpenStack Networking

Northbound APIs
6
By themselves, these technologies
don’t change the operational model.

7
To change the operational model,
what’s needed is the right abstraction.

8
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
Along comes VMware and the VM

§ VMware
introduced a new abstraction: the virtual
machine (VM)

10
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
So what does this have to do with
network virtualization?

12
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
What is a virtual network?

Application Application Application Workload Workload Workload

x86 Environment L2, L3, L4-7 Network Services


Software
Virtual Virtual Virtual Virtual Virtual Virtual
Machine Machine Machine Network Network Network

Server Hypervisor Decoupled Network Hypervisor


Requirement: x86 Requirement: IP Transport

Hardware

General Purpose Server Hardware General Purpose IP Hardware


(Dell, HP, IBM, OpenCompute, Quanta) (Arista, Cisco, HP, Juniper, Accton)

14
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
Key functions of a virtual network

Virtual Virtual Network


Operations

1. Decouples 2. Reproduces 3. Automates

Cloud
Physical Physical Operations

Hardware No change to network Operational benefits


independence from end host perspective of virtualization

16
VMware NSX provides the right
abstraction—the virtual network—to
enable operational change that
addresses pain points and meets
business needs.

17
Networking can be a barrier to the
software-defined data center
Software Defined Data Center
§ Provisioning is slow
VDC
§ Placement is limited
§ Mobility is limited
§ Hardware dependent
SOFTWARE-DEFINED
DATACENTER SERVICES

§ Operationally intensive

Compute Virtualization

Any Physical
Infrastructure

18
Network virtualization addresses this
challenge
Software Defined Data Center
§ Programmatic provisioning
VDC
§ Place any workload anywhere
§ Move any workload anywhere
§ Decoupled from hardware
SOFTWARE-DEFINED
DATACENTER SERVICES

§ Operationally efficient

Network Virtualization
Compute Virtualization

Any Physical
Infrastructure

19
Looking a bit deeper at VMware NSX

20
Some technologies you might find
helpful

§ Linux
§ Open vSwitch (OVS)
§ OpenFlow
§ OVSDB
§ Cloud management systems
§ vCloud Automation Center (vCAC)
§ OpenStack
§ CloudStack

21
Questions & answers

22
Thank you

Scott Lowe
[email protected]

23

You might also like