WP4 Meeting May 13rd 2005

WP4 Meeting May 13rd 2005

• Pragmatic / theoretical approaches: BitTorrent enhancements / Research work
• Paper "Toward a Common API for P2P Overlays"
• Evaluating Ocean Store, Pastry, Tapestry

EDOS Snapshot slides

EDOS Snapshot slides

WP4 Issues

Protocol abstraction

Users should have the possibility to take advantage of several protocols at the same time: HTTP, FTP, P2P, RSYNC, with flexibility and optimisation. See also SKYPE solutions to get round firewall issues: usage of relays.

Notion of collection of files

A given version of Cooker = a set of RPMs. Users can express the request: I want the version of Cooker tagged "20050513-1000" -> then the client looks up the packages in the multi-protocol network.

Finding a resource

With possibility to specify one wants for example the geographically closest peers

Need for an API describing the distribution process

Goal: be able to switch the underlying P2P system: Pastry, Tapestry etc. or any other part of the system (trust framework etc.)

See the paper "Toward a Common API for P2P Overlays"

• API parts
  • Notification system: peers can define the notification they want receive automatically and the notification level: email with link to new RPM, system update. Need for a declarative language for describing the type of notification.
    • Specific channels
    • Or advanced customization
    • Kadop: you can run queries, or also subscriptions
    • Query: what is available / Query-subscription: what to do with the new resources?
  • Privileged peers
  • Trust
  • Security

BitTorrent

• What is the exact overhead in having one torrent per RPM?
• We can have one single torrent for describing a set of RPM files independently: Torrent Xml

Infrastructure for testing the new architecture

• Planet Lab
• Grid5000
• Xtrem Web

New resources

• Trainee from Ecole Polytechnique
• Vasile Gabriel (18 months)

Metrics

• Cooker: 10000 RPMs
• Biggest RPM: 150 Mb
• we need detailed statistics on RPMs

Specification

Before end of July we need a detailed specification of the API process. The API has to take into account the protocol flexibility.

Actions

• First version ofthe API specification: beginning of June. See the notes of Geneva on the API: http://cui.unige.ch/~bryce/api.pdf
• Make a use case of Kadop + Active Xml in the context of Mandriva Cooker
• Experiment Kadop
• See how to have one torrent for a set of files, with individual chunks for each file
• Conduct an advanced state of the art of existing infrastructures for managing distributed storage
• Stefania decides what she will work on
• See what synergies we can find with Gorda project

{metadata}

Topics Wp4

Type Meeting

{metadata}