Planet Lab

Experiences Building PlanetLab

Iuliia ProskurniaEMDC

April 23, 2012

Introduction

Background

Slice Management

Resource allocation

Stability

Conclusions

Introduction

Background

Slice ManagementRequirements CoverageTrust AssumptionVM and Resource PoolsDelegationManagement Services

Resource allocationRequirements CoverageWorkload

StabilityRequirements CoverageNode Availability

Conclusions

Iuliia Proskurnia EMDC Experiences Building PlanetLab 1

Introduction

Background

Slice Management

Resource allocation

Stability

Conclusions

Introduction

Main dimension of the innovation:

I Novel Management Architecture

I Novel Usage Model

I Experience-driven Desigh

I Conflict-driven Design


Introduction

Background

Slice Management

Resource allocation

Stability

Conclusions

Introduction

Background




Conclusions


Introduction

Background

Slice Management

Resource allocation

Stability

Conclusions

Requirements

(R1) It must provide a global platform that supports bothshort-term experiments and long-running services.(R2) It must be available immediately, even though no one knowsfor sure what it is.(R3) We must convince sites to host nodes running code writtenby unknown researchers from other organizations.(R4) Sustaining growth depends on support for autonomy anddecentralized control.(R5) It must scale to support many users with minimal resources.


Introduction

Background

Slice Management

Resource allocation

Stability

Conclusions

Initial Design and Challenges

Design

I Distributed Virtualization

I Resource and SecurityIsolation

I PlanetLab Central(PLC)

Challenges

I Management Architecture

I Resource Allocation

I Stable system maintenance

Related Systems

I ISP

I Hosting Center

I GRID


Introduction

Background

Slice Management

Resource allocation

Stability

Conclusions

Requirements Coverage

Trust Assumption

VM and Resource Pools

Delegation

Management Services

Introduction

Background




Conclusions


Introduction

Background

Slice Management

Resource allocation

Stability

Conclusions


Trust Assumption


Delegation

Management Services

Challenges

I Minimizing Centralized Component(R4) yet maintaining thenecessary trust assumption(R3);

I Balancing the need for slices to acquire the resources theyneed(R1) yet coping with scarce resources(R5);

I Isolating slices from each other(R1) yet allowing some slicesto manage other slices(R2);


Introduction

Background

Slice Management

Resource allocation

Stability

Conclusions


Trust Assumption


Delegation

Management Services

Trust Assumption


Introduction

Background

Slice Management

Resource allocation

Stability

Conclusions


Trust Assumption


Delegation

Management Services


Require:

I Support long-lived slices(R1) and scarce of resources(R5)

I Decouple slice creation from resource allocation

Node Manager:

I VM - Point-of-presence on a node for a slice

I Resource Pool - Collection of physical and logical resourcespossible bound to a VM


Introduction

Background

Slice Management

Resource allocation

Stability

Conclusions


Trust Assumption


Delegation

Management Services

PLC

PLC Structure

I Owners assign all of its resources to PLC for redistribution

I PLC runs a slice creation service on each node (pl conf)

I PLC provide a front-end through which users create slices

I Direct and delegated slice creation


Introduction

Background

Slice Management

Resource allocation

Stability

Conclusions


Trust Assumption


Delegation

Management Services

Management Services

I Slice Creation ServiceResource Pool Assigns to pl conf

I Brokerage ServiceResource Pool Control

I Monitoring ServiceStates of the local node

I Environment ServiceSpecify immutability, Installing necessary packages

I Auditing ServicePacket flow log


Introduction

Background

Slice Management

Resource allocation

Stability

Conclusions


Workload

Introduction

Background




Conclusions


Introduction

Background

Slice Management

Resource allocation

Stability

Conclusions


Workload

Conflicts

I Requirements for isolation

I Reality of limited resources

I Model of Weak Resource Isolation


Introduction

Background

Slice Management

Resource allocation

Stability

Conclusions


Workload

WorkLoad


Introduction

Background

Slice Management

Resource allocation

Stability

Conclusions


Workload

Workload

CPU


Introduction

Background

Slice Management

Resource allocation

Stability

Conclusions


Workload

Workload

Memory


Introduction

Background

Slice Management

Resource allocation

Stability

Conclusions


Workload

Workload

Bandwidth

Pay?

I Total Tra�c generated during the month

I Incoming bandwidth

Tra�c

I Transmission - 1Mb/s

I Receive - 500Kb/s


Introduction

Background

Slice Management

Resource allocation

Stability

Conclusions


Workload

Workload

Disk


Introduction

Background

Slice Management

Resource allocation

Stability

Conclusions


Node Availability

Introduction

Background




Conclusions


Introduction

Background

Slice Management

Resource allocation

Stability

Conclusions


Node Availability

Conflicts

Conflicts:

I System on behalf of the user community(R1)

I Evolve the platform to provide long-term sustainability(R2)

Strategies:

I Relatively Stable Environment for Users

I New Releases implemented incrementally


Introduction

Background

Slice Management

Resource allocation

Stability

Conclusions


Node Availability

Node Availability


Introduction

Background

Slice Management

Resource allocation

Stability

Conclusions

Introduction

Background




Conclusions


Introduction

Background

Slice Management

Resource allocation

Stability

Conclusions

Conclusions

Conclusions:

I Carefully selected ideas Synthesis

I Real-World usage Finalization

I Large-Scale DS

I Coverage of Conflicting Requirements


Experiences Building PlanetLab

Iuliia ProksurniaEMDC

April 23, 2012

Technology

Planet Lab