ProActive Infrastructure

13
ProActive Infrastructure Eric Brewer, David Culler, Anthony Joseph, Randy Katz Computer Science Division U.C. Berkeley ninja.cs.berkeley.edu Active Networks Workshop, July 1998

description

ProActive Infrastructure. Eric Brewer, David Culler, Anthony Joseph , Randy Katz Computer Science Division U.C. Berkeley ninja.cs.berkeley.edu Active Networks Workshop, July 1998. Your PDA connects to the local infrastructure and asks it to build a custom GUI. - PowerPoint PPT Presentation

Transcript of ProActive Infrastructure

Page 1: ProActive Infrastructure

ProActive Infrastructure

Eric Brewer, David Culler,

Anthony Joseph, Randy Katz

Computer Science Division

U.C. Berkeley

ninja.cs.berkeley.edu

Active Networks Workshop, July 1998

Page 2: ProActive Infrastructure

7/16/98 ARPA Active Nets 2

Imagine

• You walk into a room

You have complete, secure, optimized access to local devices and your private resources

• Your PDA connects to the local infrastructure and asks it to build a custom GUI

• Next, your PDA then asks the infrastructure for a path out to your personal information space, where agents are processing your e-mail, v-mail, faxes, and pages

Page 3: ProActive Infrastructure

7/16/98 ARPA Active Nets 3

Vision Goal

• The next internet revolution will come from enabling component services and pervasive access

Dynamic, programmatic creation / composition of scalable, highly available, & customizable services

– Automatic adaptation to end device characteristics and network connectivity

• Arbitrarily powerful services on arbitrarily small clients using a proactive infrastructure

Page 4: ProActive Infrastructure

7/16/98 ARPA Active Nets 4

Starting Point: Transcoding Proxies

Scalable Servers

Laptops, Desktops

Info. AppliancesNetwork Computers

Spoon feed web pages to PDAs

Transformation, Aggregation, Caching, and Customization (TACC) Scalability and availability Limited customizability and locality and no persistence

Legacy Servers

Page 5: ProActive Infrastructure

7/16/98 ARPA Active Nets 5

ProActive Approach

• Create a framework that enables programmatic generation and composition of services out of strongly typed reusable components

• Key Elements– Structured architecture with a careful partitioning of state

» Bases, Active Routers, and Units

– Wide-area paths formed out of strongly-typed components

» Operators and Connectors

– Execution environments with efficient, but powerful communication primitives

» Active Messages + capsules

» TACC + persistence + customization

Page 6: ProActive Infrastructure

7/16/98 ARPA Active Nets 6

• Bases– highly available– persistent state (safe)– databases, agents– “home” base per user– service programming environment

Structured Architecture

• Active Routers– not packet routers – soft-state– well-connected– localization (any to any)

• Units– sensors / actuators– PDAs / smartphones / PCs– heterogeneous– Minimal functionality: “Smart Clients”

Wide-Area Path

Page 7: ProActive Infrastructure

7/16/98 ARPA Active Nets 7

Operators/Connectors

Operators:– transformation– aggregation– agents

– PI provides secure execution environment

Connectors:– abstract wires

– ADUs

– varying semantics

– uni/multicast

Interfaces:– strongly typed

– language independent

– control channel» path changes» authentication» feedback

Page 8: ProActive Infrastructure

7/16/98 ARPA Active Nets 8

Wide-Area Paths

• Creation (explicit or automatic):– Query Service Discovery Service to find logical path of operators

– Place operators onto nodes:

» Path is unit of resource allocation and authentication

– Connectors are polymorphic: entire path must type check - statically

• Optimization:– Add (or transpose) operators

» forward error-correction

» compression/decompression

– Change operators, connectors, locations, or parameters

• Interoperability:– Wrapper operators for legacy servers

– Leverage COM objects as operators

Page 9: ProActive Infrastructure

7/16/98 ARPA Active Nets 9

Service request

service threads

OperatorsCaches

PersistentStorage

Managed RMI++

Physicalprocessor

iSpace Execution Environment

• iSpace provides parallel application framework on Bases– RMI++ hides complexity of scalability and availability

– Dynamic customization and composition

• rSpace is limited execution environment for AR

operatorupload

Page 10: ProActive Infrastructure

7/16/98 ARPA Active Nets 10

Pilot PDA: TopGun Wingman / Mediaboard

AR

mic camera

Base

AR

PDA

LegacyServer

PCUn-Zip

Image Converter

AggregatorMulticast connector

MediaBoard

PDA Proxy

• Wingman: Pilot Web browser• Mediaboard: Pilot Mbone tool

Page 11: ProActive Infrastructure

7/16/98 ARPA Active Nets 11

Campus-wide Testbed (Millennium)

Gigabit Ethernet

PDAs Cell PhonesFuture Devices

WirelessInfrastructure

DesktopPCs

Servers

Clusters

Massive Cluster

Page 12: ProActive Infrastructure

7/16/98 ARPA Active Nets 12

Milestones

• Year 1– Architecture definition, Operator/Connector type system,

Active Message-based Active Net

– Technology: PIM prototype with COTS database, Automatic connection, NOW as Base

• Year 2– Wide-Area Paths with intermittent connectivity,

Execution environment for Base, AR, Unit

– Technology: COM integration, shared link mgmt, multicast connectors, Type hierarchy

– Working testbed, PIM prototype

• Year 3– Wide-Area Path transformation, operator migration, large-scale agents

– FSM-based fast operators, operator fusion

– Full testbed, smart-space, PIM release

Page 13: ProActive Infrastructure

ProActive Infrastructure

Eric Brewer, David Culler,

Anthony Joseph, Randy Katz

Computer Science Division

U.C. Berkeley

ninja.cs.berkeley.edu

Active Networks Workshop, July 1998