Griffin - The SAHARA Project
Download
Report
Transcript Griffin - The SAHARA Project
Griffin Update: Toward an Agile,
Predictive Infrastructure
Anthony D. Joseph
UC Berkeley
http://www.cs.berkeley.edu/~adj/
Sahara Retreat, January 2004
DETER
Outline
Griffin
–
–
–
2
Motivation
Goals
Components
Tapas Update
Tapestry Update
REAP/MINO Update
Beyond Griffin: DETER
Near-Continuous, Highly-Variable
Internet Connectivity
Connectivity everywhere: campus, in-building, satellite…
–
Most applications support limited variability (1% to 2x)
–
–
–
–
–
–
Design environment for legacy apps is static desktop LAN
Strong abstraction boundaries (APIs) hide the # of RPCs
But, today’s apps see a wider range of variability
–
3
Projects: Sahara (01-04), Iceberg (98-01), Rover (95-97)
35 orders of magnitude of bandwidth from 10's Kb/s 1 Gb/s
46 orders of magnitude of latency from 1 sec 1,000's ms
59 orders of magnitude of loss rates from 10-3 10-12 BER
Neither best-effort or unbounded retransmission may be ideal
Also, overloaded servers / limited resources on mobile devices
Result: Poor/variable performance from legacy apps
Griffin Goals
Users always see excellent ( local, lightly loaded)
application behavior and performance
–
–
–
Help legacy applications handle changing conditions
–
–
Analyze, classify, and predict behavior
Pre-stage dynamic/static code/data (activate on demand)
Architecture for developing new applications
–
–
4
Independent of the current infrastructure conditions
Move away from “reactive to change” model
Agility: key metric is time to react and adapt
Input/control mechanisms for new applications
Application developer tools
Griffin: An Adaptive, Predictive
Approach
Continuous, cross-layer, multi-timescale introspection
–
–
–
Convey app reqs/network info to/from lower-levels
–
–
Break abstraction boundaries in a controlled way
OPEN: Extensible interfaces to avoid existing least common
denominator problems
Overlay more powerful network model on top of IP
–
–
5
Collect & cluster link, network, and application protocol events
Broader-scale: Correlate AND communicate short-/long-term
events and effects at multiple levels (breaks abstractions)
SOLVED: Building accurate models of correlated events
–
Avoid standardization delays/inertia
Enables dynamic service placement
PARTIAL: Efficient interoperation with IP routing policies
Some Enabling Infrastructure
Components
Tapas network characteristics toolkit
–
–
–
REAP protocol modifying / application building toolkit
–
–
–
Introspective mobile code/data support for legacy / new apps
Provides dynamic placement of data and service components
MINO E-mail application, COMPASS service instance locator
Tapestry, Brocade, and Mobile Tapestry
–
6
Measuring/modeling/emulating/predicting delay, loss, …
Provides micro-scale network weather information
Mechanism for monitoring/predicting available QoS
–
Overlay routing layer providing efficient application-level object
location and routing
Mobility support, fault-tolerance, varying delivery semantics
Outline
Griffin
–
–
–
7
Motivation
Goals
Components
Tapas Update
Tapestry Update
REAP/MINO Update
Beyond Griffin: DETER
Tapas Update
Accurate modeling and emulation for protocol design
–
–
Project completed (1998-2003)
–
–
–
–
Multitracer trace analysis tool
Two highly-accurate network models (MTA, M3)
Domain analysis tool
Highly-accurate Tapas-based link simulator
PhD dissertation
–
8
Models/artificial traces that are statistically indistinguishable
from real network traces: delay, error, congestion
Study interactions between protocols at different levels
Almudena Konrad, “TAPAS: A Research Paradigm for the
Modeling, Prediction, and Analysis of Non-stationary Network
Behavior,” (Ph.D., December 2003)
Tapestry Update
Distributed Object Location and Routing (DOLR) overlay
network
Improved static resilience (talk tomorrow)
–
–
–
Support for rapid, hierarchical mobility
–
–
9
Pre-computed backup paths enable near- instantaneous fail-over
(3 paths/router entry)
Better dynamic resilience through improved repair algorithms to
handle long-term faults
IEEE JSAC article pending
Scaleable mobility for large crowds traveling together
IPTPS paper in submission
% of All Pairs Reachable
Tapestry Static Resilience (Sim)
1
0.9
0.8
0.7
0.6
0.5
0.4
0.3
0.2
0.1
0
Instantaneous IP
0
0.05
Tapestry / FRLS
0.1
0.15
Proportion of IP Links Broken
10
0.2
REAP/MINO/COMPASS Update
Introspective code / data migration in 3-tier hierarchies
–
–
Combines static trace analysis w/ dynamic monitoring
of clients to predict appl’n / communication behavior
–
–
Identify and optimize code/data placement
Analyzing EECS IMAP server traces for user session length
and inter-session mobility (see poster)
Testbed technologies:
–
–
–
11
Distributes server load, empowers limited devices
Provides illusion of high connectivity
REAP code migration toolkit
MINO E-mail OceanStore application
COMPASS: service instance location service (talk tomorrow)
User IMAP Session Lengths
(processed to remove auto checks)
1
50% of sessions <1000
seconds (17 minutes)
fraction of sessions
0.9
0.8
0.7
20% of sessions > 6000 secs
0.6
0.5
0.4
0.3
1800 seconds (30 minutes) =
IMAP server's timeout setting
0.2
0.1
0
0
12
2000
4000
6000
session length (seconds)
8000
10000
Outline
Griffin
–
–
–
13
Motivation
Goals
Components
Tapas Update
Tapestry Update
REAP/MINO Update
Beyond Griffin: DETER
DETER
Cyber DEfense Technology
Experimental Research (DETER)
NSF and DHS sponsored cyber-defense research project
–
DETER Goals:
–
–
–
Design and construction of a testbed for network security
experiments,
Research on experimental methodology for network security, and
Research on network security.
DETER: focus on 1), but it needs to do some of 2) and 3)
Goal: Duplicate observed attack effects in the testbed
–
14
Approx $10M total ($2.4 for UCB)
E.g., self-congestion for worms
DETER
Related Goals
Vendor-heterogeneous environment
–
–
–
Create a researcher’s electronic notebook
–
–
Network topologies, attack traces and generators
Background traffic traces and generators
Many requirements (some conflicting!)
–
–
–
15
Reflects real-world, implementation interactions
Open source versus commercial code (e.g., timers)
Behavior under load/attack
Versatility, Controllability, Accessibility, Usability
Functionality, Transparency, Fairness, Containment
Security, Fidelity, Integrity
DETER
Background
People:
–
–
Anthony Joseph, Ruzena Bajcsy, Shankar Sastry, David
Culler, Doug Tygar, David Wagner, Eric Fraser (staff), YihChun Hu (postdoc)
Small initial user community (usability versus containment)
Hardware
–
–
First cluster of ~64 PCs at USC/ISI West (Jan/Feb 04)
Second cluster at UCB (Mar/Apr 04)
Three experiment areas (EMIST)
–
Worms, routing attacks, DDoS attacks
Major demo of experimental results in DC in June 04
–
16
Similar to ISI cluster, but with more hw routers
–
Future: DHS, HSARPA, and White House “exercises”
E.g., LiveWire, DarkScreen, JWIG2004
DETER
Preliminary UCB
Architecture Proposal
Pwr Ctlr
Pwr Ctlr
L3 routers
DNS
3Com
L2 switches
Internet
Ethernet
FW2
DMZ
7x
8x
9x
1x
2x
3x
10x
11x
12x
7x
8x
9x
4x
5x
6x
1x
2x
3x
10x
11x
12x
4x
5x
6x
C
7 8 9 101112
A
d i g i
12 34 56
A
B
t a l
Pwr Ctlr
Ethernet
Hub
7x
8x
9x
1x
2x
3x
10x
11x
12x
7x
8x
9x
4x
5x
6x
1x
2x
3x
10x
11x
12x
4x
5x
6x
C
7 8 9 101112
A
1 2 34 56
A
B
L2 switch
Bay Networks
FW1
Sniffer Server
monitoring/analysis
Sniffer
Pwr Ctlr
Mgmt 2
Mgmt L2 switch
File Server
Serial links
17
Mgmt 1
DETER
Some Collaboration Opportunities
Research opportunities
–
Measuring application behavior under attack
–
Strategies for mitigating attacks
–
Substantial knowledgebase from commercial customers (Tiger
teams)
Donations
–
–
–
18
Worm defenses, DDoS traceback and block, hardening routing
protocols
Operations and management
Web servers, file servers, etc.
VIFs: Cluster or security experience/research
Remote administration tools, remote SW installation setup tools
Nodes, Firewall machines, L2/L3 routers, HW sniffers, etc
Griffin Update: Toward an Agile,
Predictive Infrastructure
Anthony D. Joseph
UC Berkeley
http://www.cs.berkeley.edu/~adj/
Sahara Retreat, January 2004
DETER