当前位置:文档之家› vmware NSX介绍

vmware NSX介绍

Linux CLIs
Python SDKs
Compute & Images API
Compute Logic (quotas, scheduling) Compute Drivers (vSphere, KVM)
User Keystone authentication, autho rization Network API Block Storage API Block Storage Logic (quotas, scheduling) Block Storage Drivers (vSAN, EMC)
28
Hardware VTEPs
Benefits:
• Fine-grained access: can pull a single physical port into the virtual world • Connect bare metal workloads with higher performance/throughput
Extensibility of the header likely needed
• STT has 64-bit “context” vs 24-bit VNI
Tunnel format decoupled from control plane Tunnel format != virtualization architecture
8
Visibility and Debugging
9
Visibility and Debugging
Virtualization made network visibility difficult
Network virtualization provides visibility
10
Basic Idea
5
What is VMware NSX?
Internet
6
The Virtual Network
7
The Time is Now
60
Ports in Millions
40
Virtual Server Access Ports 32% CAGR
20
Physical Server Access Ports 15 % CAGR
29
Connecting the Physical to the Virtual
Logical network (VNI)
Controller Cluster
VM MACS
DB
API (OVSDB)
Tunnels (VXLAN)
vSwitch vSwitch vSwitch Hypervisor vSwitch Hypervisor Hypervisor Hypervisor
PHYMACS
VM VM VM
IP Underlay (no mulitcast required)
Physical Workloads
30
VMware Message for Openstack
Cloud Management Platforms (CMPs)
Business Goals: Reduce costs Increase agility
VXLAN Cable Hypervisor
STT Cable
27
Why Not a Single Tunnel Format?
STT was designed to optimize performance for hypervisorhypervisor traffic • Leveraging commodity NIC behavior so that tunneling has negligible
• Ideal for multi-vendor situations (e.g. vswitch-physical switch communication) • Will start to see NIC support for high performance in the next year
Provides ability to change performance characteristics on the fly.
18
Example: Runtime Deployment of Distributed Routing
VM VM VM
VM VM VM VM
VM VM VM VM VM
One Complex Network
Multiple Simple Networks
11
Visibility & Troubleshooting
12
Visibility & Troubleshooting
Disconnected
Disconnected
Disconnected
Disconnected
Controller Cluster L3 L2 L2
CMP
VM
பைடு நூலகம்
VM
“NSX API”
VTEP API Software Hardware
VLAN
NSX vSwitch
vSphere Host
NSX vSwitch
vSphere Host
Open vSwitch
KVM
Open vSwitch
Xen Server NSX Gateway
Agenda
NSX Message Quick Update VMWare Message for Openstack Media Feedback and Response
1
What is VMware NSX?
Internet
4
What is VMware NSX?
Internet
Tools for selfservice + automation, built on top of API
Applications
Web GUI CLI SDK Identity
Varies greatly by CMP: determines whether a request is allowed, updates external systems, decides what part of underlying infrastructure will host the workload
Network Logic (quotas, scheduling) Compute Drivers (NSX, Cisco)
Nova / Glance Neutron (Quantum) OpenStack CMP Software Infrastructure Hardware Infrastructure
API Layer CMP Logic
(governance, workflow, placement)
Models available resources. Handles requests to create/ destroy/update and view current status
Driver Layer Cloud Management Platform Software Infrastructure Hardware Infrastructure
VM VM VM
VM
19
Latency Impact on Production Network
20
And Much, Much More …
• • • • •
MPLS integration Control plane federation Policy frameworks
Flow-level tracking for fabric optimization

21
NSX EcoSystem
VMware NSX Ecosystem
23
Seeing Broad Adoption
24
Eco Sysem Integration and Positioning Today
NSX Optimized For vSphere
Service Composer for L4-L7 integration
Possible root cause
Collected metrics Calculated metrics
Metric values
14
Virtual Network Health Monitoring & Troubleshooting
15
Physical Components Health Monitoring and Troubleshooting
performance impact
• Unfortunately, it’s hard for switches to implement & can raise issues
with firewalls
VXLAN is the de facto industry standard for network virtualization
Same operational model (provisioning, monitoring) as
virtual networks Consistent provisioning and operations for entire Data Center, regardless of workloads, over a simple IP fabric
16
Runtime Network Optimization
相关主题