Towards Virtual Networks for Virtual Machine Grid Computing

  • Slides: 28
Download presentation
Towards Virtual Networks for Virtual Machine Grid Computing Ananth I. Sundararaj Peter A. Dinda

Towards Virtual Networks for Virtual Machine Grid Computing Ananth I. Sundararaj Peter A. Dinda Prescience Lab Department of Computer Science Northwestern University http: //virtuoso. cs. northwestern. edu

Outline • • Virtual machine grid computing Virtuoso system Networking challenges in Virtuoso Enter

Outline • • Virtual machine grid computing Virtuoso system Networking challenges in Virtuoso Enter VNET Adaptive virtual network Related Work Conclusions Current Status 2

1 arbitrary amounts of Aim. Deliver computational power to perform distributed and parallel computations

1 arbitrary amounts of Aim. Deliver computational power to perform distributed and parallel computations Traditional Paradigm New Paradigm 2 Resource multiplexing using OS level mechanism Grid Computing 3 b 5 Grid Computing using virtual machines 4 3 a 6 a Problem 1: Complexity from resource Solution user’s perspective Problem 2: Complexity from resource owner’s perspective 6 b Virtual Machines What are they? How to leverage them? 3

Virtual Machines Virtual machine monitors (VMMs) • Raw machine is the abstraction • VM

Virtual Machines Virtual machine monitors (VMMs) • Raw machine is the abstraction • VM represented by a single image • VMware GSX Server 4

Virtual machine grid computing • Approach: Lower level of abstraction – Raw machines, not

Virtual machine grid computing • Approach: Lower level of abstraction – Raw machines, not processes, jobs, RPC calls R. Figueiredo, P. Dinda, J. Fortes, A Case For Grid Computing on Virtual Machines, ICDCS 2003 • Mechanism: Virtual machine monitors • Our Focus: Middleware support to hide complexity – – – – Ordering, instantiation, migration of machines Virtual networking remote devices Connectivity to remote files, machines Information services Monitoring and prediction Resource control 5

The Simplified Virtuoso Model User’s LAN Virtual networking ties the machine back to user’s

The Simplified Virtuoso Model User’s LAN Virtual networking ties the machine back to user’s home network Orders a raw machine VM Specific hardware and performance Basic software installation available Virtuoso continuously monitors and adapts User 6

User’s View in Virtuoso Model User’s LAN VM User 7

User’s View in Virtuoso Model User’s LAN VM User 7

Outline • • Virtual machine grid computing Virtuoso system Networking challenges in Virtuoso Enter

Outline • • Virtual machine grid computing Virtuoso system Networking challenges in Virtuoso Enter VNET Adaptive virtual network Related Work Conclusions Current Status 8

Why VNET? A Scenario Foreign hostile LAN User’s friendly LAN IP network User has

Why VNET? A Scenario Foreign hostile LAN User’s friendly LAN IP network User has just bought Virtual Machine 9

Why VNET? A Scenario VM traffic going out on foreign LAN Foreign hostile LAN

Why VNET? A Scenario VM traffic going out on foreign LAN Foreign hostile LAN User’s friendly LAN X IP network Host Proxy Virtual Machine A machine is suddenly plugged into a foreign network. What happens? • Does it get an IP address? • Is it a routeable address? • Does firewall let its traffic through? To any port? VNET: A bridge with long wires 10

Outline • • Virtual machine grid computing Virtuoso system Networking challenges in Virtuoso Enter

Outline • • Virtual machine grid computing Virtuoso system Networking challenges in Virtuoso Enter VNET Adaptive virtual network Related Work Conclusions Current Status 11

A Layer 2 Virtual Network for the User’s Virtual Machines • Why Layer 2?

A Layer 2 Virtual Network for the User’s Virtual Machines • Why Layer 2? – – Protocol agnostic Mobility Simple to understand Ubiquity of Ethernet on end-systems • What about scaling? – Number of VMs limited (~1024 per user) – One VNET per user – Hierarchical routing possible because MAC addresses can be assigned hierarchically 12

VNET operation ethx “eth 0” Client LAN Client VNET Proxy Ethernet Packet Captured by

VNET operation ethx “eth 0” Client LAN Client VNET Proxy Ethernet Packet Captured by Promiscuous Packet Filter “Host Only” Network ethy VM “eth 0” vmnet 0 ethz IP Network VNET Host Ethernet Packet Tunneled over TCP/SSL Connection Ethernet Packet Injected Directly into VM interface Traffic outbound from the user’s LAN 13

Performance Evaluation However Main goal VNET’s performance should be Convey the network management problem

Performance Evaluation However Main goal VNET’s performance should be Convey the network management problem induced by VMs to the home network of the user • In line with physical network Metrics Latency Why? How? • Comparable to other options • Sufficient for scenarios Bandwidth Why? How? • small transfer • ping • Large transfer • ttcp • Interactivity • hour long intervals • low throughput • socket buffer 14 • 1 GB of data

VNET test configuration 100 mbit Switches Client 100 mbit Switch Firewall 1 100 mbit

VNET test configuration 100 mbit Switches Client 100 mbit Switch Firewall 1 100 mbit Switch Router Proxy VM Host Local IP Network (14 hops via Abilene) Carnegie Mellon University, PA Northwestern University, IL Wide area configuration Client 100 mbit Switches Firewall Switch 1 Router 100 mbit Switch Firewall 2 Proxy VM 100 mbit Switches Host Local area configuration 15

Average latency over WAN Host - VM Proxy - Host Client - Proxy (Physical

Average latency over WAN Host - VM Proxy - Host Client - Proxy (Physical Network) VM Host Client Proxy Northwestern University, IL IP Network 16 Carnegie Mellon University, PA

Standard deviation of latency over WAN What: VNET increases variability in latency Why: TCP

Standard deviation of latency over WAN What: VNET increases variability in latency Why: TCP connection between VNET servers trades packet loss for increased delay 17 (Physical Network)

Bandwidth over WAN Expectation: VNET to achieve throughput comparable to the physical network What

Bandwidth over WAN Expectation: VNET to achieve throughput comparable to the physical network What do we see: VNET achieves lower than expected throughput Why: VNET’s is tricking TTCP’s TCP connection 18

Outline • • Virtual machine grid computing Virtuoso system Networking challenges in Virtuoso Enter

Outline • • Virtual machine grid computing Virtuoso system Networking challenges in Virtuoso Enter VNET Adaptive virtual network Related Work Conclusions Current Status 19

VNET Overlay Foreign hostile LAN 1 User’s friendly LAN VM 1 Host 1 +

VNET Overlay Foreign hostile LAN 1 User’s friendly LAN VM 1 Host 1 + VNET IP network Proxy + VNET VM 4 Foreign hostile LAN 2 Host 4 + VNET VM 3 Host 3 + VNET Foreign hostile LAN 3 VM 2 Host 2 + 20 VNET

Bootstrapping the Virtual Network VM VM Vnetd Host + VNETd Proxy + VNETd •

Bootstrapping the Virtual Network VM VM Vnetd Host + VNETd Proxy + VNETd • Star topology always possible VM • Topology may change • Links can be added or removed on demand • Virtual machines can migrate • Forwarding rules can change • Forwarding rules can be added or removed on demand 21

Application communication topology and traffic load; application processor load Vnetd layer can collect all

Application communication topology and traffic load; application processor load Vnetd layer can collect all this information as a side effect of packet transfers and invisibly act • VM migrates VM Layer VNETd Layer • Topology changes • Routing change • Reservation Network bandwidth and latency; sometimes topology Physical Layer 22

Outline • • Virtual machine grid computing Virtuoso system Networking challenges in Virtuoso Enter

Outline • • Virtual machine grid computing Virtuoso system Networking challenges in Virtuoso Enter VNET Adaptive virtual network Related Work Conclusions Current Status 23

Related Work • Collective / Capsule Computing (Stanford) – VMM, Migration/caching, Hierarchical image files

Related Work • Collective / Capsule Computing (Stanford) – VMM, Migration/caching, Hierarchical image files • Denali (U. Washington) – Highly scalable VMMs (1000 s of VMMs per node) • SODA and VIOLIN (Purdue) – Virtual Server, fast deployment of services • • • VPN Virtual LANs, IEEE Overlay Networks: RON, Spawning networks, Overcast Ensim Virtuozzo (SWSoft) – Ensim competitor • Available VMMs: IBM’s VM, VMWare, Virtual PC/Server, Plex/86, SIMICS, Hypervisor, VM/386 24

Conclusions • There exists a strong case for grid computing using virtual machines •

Conclusions • There exists a strong case for grid computing using virtual machines • Challenging network management problem induced by VMs in the grid environment • Described and evaluated a tool, VNET, that solves this problem • Discussed the opportunities, the combination of VNET and VMs present, to exploit an adaptive overlay network 25

Current Status • Application traffic load measurement and topology inference [Ashish Gupta] • Support

Current Status • Application traffic load measurement and topology inference [Ashish Gupta] • Support for arbitrary topologies and forwarding rules • Dynamic adaptation to improve performance 26

Pseudo proxy Current Status Snapshots 27

Pseudo proxy Current Status Snapshots 27

 • For More Information – Prescience Lab (Northwestern University) • http: //plab. cs.

• For More Information – Prescience Lab (Northwestern University) • http: //plab. cs. northwestern. edu – Virtuoso: Resource Management and Prediction for Distributed Computing using Virtual Machines • http: //virtuoso. cs. northwestern. edu • VNET is publicly available from • http: //virtuoso. cs. northwestern. edu 28