110 likes | 227 Views
PlanetLab Workshop May 12, 2006. Incentives. Private PLs are happening… What direction for “public” PL? Growth? Distributing ops? Incentives to move in that direction E.g., give private PLs a good reason to pool resources with the public PL
E N D
Incentives • Private PLs are happening… • What direction for “public” PL? • Growth? Distributing ops? • Incentives to move in that direction • E.g., give private PLs a good reason to pool resources with the public PL • A good incentive model gives everyone something they want
Risk: Fragmentation • Fragmentation of development • Private PLs have incentive to not stray far from PLC’s distribution? • Better communication from PLC • How to contribute to PLC distribution • Fragmentation of user experience • “Full federation” (PLE, PLJ) • Stork, CoMon, etc. – indistiguishable from PLC • Does public PL support other types of federation? • Costs vs. benefits, for users and PLC
Summary • Why federation? • Engine of evolution for public PL • Research problems • Longer term: influence GENI • PlanetLab is… • A testbed • A community • … An experiment!
Agenda • Code base walkthrough • Wish list • Breakout groups • Whatever interests people • 11:30: Group reports (a slide or two)
Wish List • Port reservations on PlanetLab (Justin) • MyPLC build from source (Mark) • Concrete roadmap for federation (Timur, Larry, Aki) • Low risk, low divergence of code/policies • Model for distributed support (Elliot) • Documentation • Community contributes to Wiki (everyone) • Each Private PL effort, why they’re using PPL, why/if federate? • QA framework (Mark) • Training materials (log in, slice expiration, exercises) (Elliot) • Best practices for PlanetLab use (don’t compile, use Emulab) • MyPLC upgrade process • Testing for MyPLC • Looking to community to contribute tests
Wish List 2 • Involvement in federation spec/impl (Emulab) • Communication about API changes? • Federation spec soon, minimal changes • PL v4: Get rid of legacy code, move on • PLC runs MyPLC, upgrade servers • Does it involve a reinstall? • “What does a reinstall buy PLC/our users?” • Incentives discussion on Federation mailing list (Mike, Justin)
Breakout Groups • Clusters (Marc) • Federation roadmap (Aaron) • MyPLC (Mark) • Back at 11:30 for group reports
Federation • How to support discussion of resource allocation/policies in the future? • Technically things under control • Mechanisms ready by summer • Use federation mailing list to figure out what policies people want • What about more restrictive AUPs?
PLC vs. private PLs • What role does PLC play? • Transition to role as an official software vendor • Users of MyPLC become customers • Give feedback, define features, develop code • Separate developers and users of PLC software • PLC probably won’t use MyPLC • Public PL will always lag private PLs • What’s right model for roles? • MySQL, FreeBSD, Linux, …
Clusters • How PL benefits clusters? • PL will release MyPLC+ROCKS soon • Community will run performance tests to ensure that costs are minimal, user transparency tests • What else can we fix through virtualization? • Broken jobs leave behind SysV IPC keys that prevent future jobs running; Vserver fixes • Build a “slice scheduler” to run each job in a slice, remove it after the job is done • Give each slice its own IP address, make it look like you really own a machine • Discussion of clusters on Federation list?