{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}

PlanetLab-06-031

PlanetLab-06-031 - PlanetLab Architecture An Overview Larry...

Info iconThis preview shows pages 1–5. Sign up to view the full content.

View Full Document Right Arrow Icon
PlanetLab Architecture: An Overview Larry Peterson*, Steve Muir*, Timothy Roscoe , Aaron Klingaman* * Princeton University Intel Research – Berkeley PDN–06–031 May 2006 Status: Ongoing Draft.
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
PlanetLab Architecture: An Overview Larry Peterson, Steve Muir, Timothy Roscoe, Aaron Klingaman May 5, 2006 Contents 1 Introduction 3 2 Organizing Principles 3 2.1 Distributed Virtualization . . . . . . . . . . . . . . . . . . . . . . 4 2.2 Unbundled Management . . . . . . . . . . . . . . . . . . . . . . 4 2.3 Chain of Responsibility . . . . . . . . . . . . . . . . . . . . . . . 4 2.4 Decentralized Control . . . . . . . . . . . . . . . . . . . . . . . . 5 2.5 Efficient Resource Sharing . . . . . . . . . . . . . . . . . . . . . 5 3 Principals and Trust Relationships 5 4 Architectural Components 8 4.1 Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 4.2 Virtual Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 4.3 Node Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 4.4 Slice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 4.5 Slice Creation Service . . . . . . . . . . . . . . . . . . . . . . . . 15 4.6 Auditing Service . . . . . . . . . . . . . . . . . . . . . . . . . . 15 4.7 Slice Authority . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 4.8 Management Authority . . . . . . . . . . . . . . . . . . . . . . . 19 4.8.1 Public Interface . . . . . . . . . . . . . . . . . . . . . . . 20 4.8.2 Boot Manager Interface . . . . . . . . . . . . . . . . . . 21 4.9 Owner Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 4.10 Resource Specification . . . . . . . . . . . . . . . . . . . . . . . 23 1
Background image of page 2
5 Security Architecture 24 5.1 Preliminaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 5.1.1 Static Key Infrastructure . . . . . . . . . . . . . . . . . . 24 5.1.2 Certificates . . . . . . . . . . . . . . . . . . . . . . . . . 25 5.2 Booting a Node . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 5.3 Creating a Slice . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 5.4 Enabling a User . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 5.5 Certificate-Based Authentication and Authorization . . . . . . . . 27 6 Interfaces 28 2
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
1 Introduction PlanetLab has evolved rapidly over the past three years according to a set of design principles [9], but without formal documentation of its underlying architecture. This document addressees this shortcoming by defining the main architectural ele- ments of PlanetLab. It is the first in a series of documents that collectively define Verion 4 of the PlanetLab architecture. 1 Subsequent documents define specific elements (and their interfaces) in detail: Slice and Management Authorities: Interface Specifications [4]. Node Manager and Slice Creation Service: Interface Specifications [6]. Securely Booting PlanetLab Nodes: Reference Implementation [3]. PlanetFlow and Audit Archive: Reference Implementation [2]. Virtualized Execution Environments: Reference Implementation. Note that with the exception of the last document, this series defines PlanetLab at a global level; it is not intended to serve as a reference manual for typical users. Also note that while pseudo-code corresponding to various interface calls are included in this document for illustrative purposes, the specification documents referenced above should be consulted for the authoritative definitions. We use two sidebars to discuss tangential issues: Implementation Note: Identifies ways in which the current imple- mentation falls short of the architecture, or ways in which the current implementation might be trivially extended to support a cleaner archi- tectural definition. and Evolution Note: Discusses ways in which the architecture and imple- mentation might evolve in the future. 2 Organizing Principles PlanetLab is designed around five organizing principles, each stemming from either a user requirement or a constraint of the environment in which it operates. This section identifies these requirements and the organizing principles they inspire. In the process, it introduces some of the key concepts underlying PlanetLab.
Background image of page 4
Image of page 5
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}