1 A Blueprint for Introducing Disruptive Technology into the Internet Larry Peterson Princeton...

of 28 /28
1 A Blueprint for Introducing Disruptive Technology into the Internet Larry Peterson Princeton University / Intel Research

Embed Size (px)

Transcript of 1 A Blueprint for Introducing Disruptive Technology into the Internet Larry Peterson Princeton...

  • A Blueprint for Introducing Disruptive Technology into the InternetLarry PetersonPrinceton University / Intel Research

  • ClaimsNetwork/Application distinction is blurringpressure to move intelligence into the networkFull integration will result in a newservice-oriented network architectureHoweverthe Internet is increasingly ossified

  • Take 1: Extensible RoutersLocal (node-centric) perspectiveMotivating examplesdiscontinuity at assumption boundariese.g., trust, performance, address space,Additional factoremerging hardwaree.g., network processorsGoalsextend router with new servicesachieve robust performance on diverse hardware

  • RRest of the InternetMy NetworkUntrustedTetheredHigh LatencyHigh BWHigh PowerDiffServTrustedWirelessLow LatencyLow BWLow PowerIntServAssumption Boundary

  • Take 1: Extensible RoutersLocal (node-centric) perspectiveMotivating examplesdiscontinuity at assumption boundariese.g., trust, performance, address space,Additional factoremerging hardwaree.g., network processorsGoalsextend router with new servicesachieve robust performance on diverse hardware

  • Take 2: PlanetLabGlobal (network-wide) perspectiveMotivating examplesgeographically distributed services (e.g., DHT, CDN)network measurement and anomaly detectionFundamental advantageslatency (proximity)multi-lateralizationdecentralized control

  • Overlay Network1000 viewpoints on the networkincludes both edge sites and network crossroads

  • Dual RolesResearch testbedlarge set of geographically distributed machinesdiverse & realistic network conditionsDeployment platformservices: design evaluation client basenodes: proxy path physical path

  • Design PrinciplesSlice-ability (distributed virtualization)Distributed Control of ResourcesUnbundled ManagementApplication-Centric Interfaces

  • Slice-abilityEach service runs in a slice of PlanetLabdistributed set of resources (network of virtual machines)allows services to run continuouslyVM monitor on each node enforces sliceslimits fraction of node resources consumedlimits portion of name spaces consumedIssue: global resource discoveryhow do applications specify their requirements?how do we map these requirements onto a set of nodes?

  • Distributed Control of ResourcesAt least two interested partiesservice producers (researchers)decide how their services are deployed over available nodesservice consumers (users)decide what services run on their nodesAt least two contributing factorsfair slice allocation policyboth local and global components (see above)knowledge about node statefreshest at the node itself

  • Unbundled ManagementPartition management into orthogonal servicesresource discoverymonitoring node healthtopology managementmanage user accounts and credentialssoftware distributionIssuesmanagement services run in their own sliceallow competing alternativesengineer for innovation (define minimal interfaces)

  • Application-Centric InterfacesInherent problemsstable platform versus research into platformswriting applications for temporary testbedsintegrating testbeds with desktop machinesApproachadopt popular API (Linux) and evolve implementationeventually separate isolation and application interfacesprovide generic shim library for desktops

  • Growth StrategyPhase0: Seeding the testbed100 centrally managed machinespure testbed (no expected client workload)Phase1: Scaling up the testbedgrow to 1000 nodes with user-provided hardwarecontinuously running services (researchers as clients)Phase2: Cultivating a user communitynon-researchers as clientsPlanetLab spinoffs interpreted as success

  • Dynamic Slice CreationN3N4NmN1N2...AgentBroker......ServiceManager

  • Virtual MachinesSecurityprevent unauthorized access to stateFamiliar APIforcing users to accept a new API is deathIsolationcontain resource consumptionPerformancedont want to be apologetic

  • VMM: Short-term PlanHardwareLinux

    VserverService 3

    VserverService 4CombinedIsolation andApplicationInterface+ Resource Isolation+ Safe Raw Sockets+ Instrumentation

  • VMM: Long-term PlanHardwareIsolation Kernel

    XPService 3

    BSDService 4ApplicationInterfaceIsolationInterface Denali Xenoserver

  • VM ExperiencesSecuritythe kernel is the least of our worriesProgramming Interfacehow many do we really need?Isolationbandwidth today, but memory soonPerformancepressure to add capabilities to the kernel

  • SONA RevisitedHow does the network architecture evolve?Is the Internet experience applicable?Overlays InternetasInternet Phone System

  • SONAInternetToday: Internet offers a single service model

  • SONAInternetNew Model: Applications subscribe to service overlaysProblem: Overlays perform redundant tasks

  • SONAInternetOver Time: Common base services emergeThey expose rich interfaces

  • SONAInternetEventually: Popular behavior subsumed into the Internet

  • Routing/Topology ServiceExample of how the process might evolveeach service independently discovers a topologyshared topology probing mechanisme.g., Scriptrouteshare topology information across layerse.g., BGP feed from the Interneta set of common sub-services emergefor a given node, tell me whos nearbyfor a given node pair, tell me the routes between themand the winner is

  • PerformanceSeparate the Control and Data PlanesPlanetLab defines a VM for a new control planeextensible router defines a VM for the data planea new control/data interface emerges

  • WhoArchitecture TeamLarry Peterson (Princeton), David Culler (Berkeley), Tom Anderson (Washington), Timothy Roscoe (Intel), Frans Kaashoek (MIT)Implementation Team4 @ Intel and 2+ @ PrincetonContributing CommunityVMM: Hand (Cambridge), Gribble (Washington)DHT: Stoica (Berkeley), Druschel (Rice), Morris (MIT)Resource Brokers: Vahdat (Duke), Wroclawski (MIT)Applications: Pai (Princeton), Hellerstein (Berkeley)User Community: dozens of projects @ 40+ sites

  • More Informationpl-web1.nbgisp.com