Download oasis_poster

OASIS: Enabling Services with Programmable Networks
George Porter, Mel Tsai, Li Yin, Randy H. Katz
Enabling Services
• Distributed applications rely on functionality such as
measurements, path selection, filtering, aggregation,
and other services
• These services are partitioned between clients,
servers, and the network fabric itself
• High I/O speed as well as per-packet and per-flow
processing drives placing computation in the network
Research Opportunities
Proposed PNE architecture Services that benefit from PNEs
• Virtual Machine model that can be targeted to
various PNEs
• Built from combination of:
• Generalized Packet Filters with tags
• Rules that respond to packet content, tags,
and internal state
• Persistent State for session and flow
processing
• Identifying which portions of an application to cast
into the network fabric
Ethernet
Port
NAT
Packet
Filter 3
• Application-specific network processing exists
today:
Default
filter
 Intrusion detection
 Overlay networks / P2P
10.0.0.100
eth0
windows1
10.0.0.101
169.229.48.246
L2 Switching
Engine w/ARP
eth1
eth0
client01
QoS Module
IP Router
Engine
10.0.0.102
10.0.0.1 eth0
Node ensembles
eth0
ethernet 4/2
VLAN 5
client02
10.0.0.103
ethernet 4/3
eth0
ethernet 3/1
client03
10.0.0.127 / 24
ethernet 3/3
ethernet 3/7
eth0
VLAN 4
Passport
“Private” Cluster
on 10.2.2.x
10.0.0.104
ethernet 3/5
ethernet 4/8
10.10.140.1 / 24
clientserv04
10.2.2.104
eth1
Default VLAN (all ports)
10.2.2.1 / 24
Default VLAN (all ports)
10.10.140.200 / 24
default gw = 10.10.140.1
Accelar Switch
Alteon
10.2.2.105
10.2.2.106
10.2.2.107
10.2.2.108
eth1
10.10.140.3
client05
client06
client07
client08
iSD
Experimental Plan
 HTTP load balancing
 Intelligent Storage / SANs
• can be separated into filtering and
computational components
Control
Processor
 Traffic shaping and monitoring
 Firewalls
• can be divided into sense/monitor/act
components
server1
• Quantifying the flexibility and reliability of a
programmable network that supports application
services
Network appliances
Packet filter
33
• need to look at the packet’s data, not just its
header
Testbed Design
Backplane
• Managing the state at a programmable network
element (PNE) and state across multiple PNEs
Packet
filter 1
• are heterogeneous
• Build rich measurement and monitoring service
that higher-level applications can make use of
Firewall
• Devices working together must exchange state,
measurements, and actuation responsibilities
• No one device has global visibility, and so
services must collect information and initiate
actuation in a distributed way
• Single-PNE programming model on the Linux
platform
• Distributed state maintenance among device
ensembles
• Test application: cooperative SAN-to-SAN cache