1 / 9

Reforming Software Delivery Using P2P Technology Purvi Shah Advisor: Jehan-François Pâris

Reforming Software Delivery Using P2P Technology Purvi Shah Advisor: Jehan-François Pâris Department of Computer Science University of Houston Jeffrey Morgan Miranda Mowbray John Schettino, Chandrasekar Venkatraman Enterprise Systems and Software Lab Hewlett-Packard.

mcleodr
Download Presentation

Reforming Software Delivery Using P2P Technology Purvi Shah Advisor: Jehan-François Pâris

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Reforming Software Delivery Using P2P Technology • Purvi Shah • Advisor: Jehan-François Pâris • Department of Computer Science • University of Houston • Jeffrey MorganMiranda MowbrayJohn Schettino,Chandrasekar Venkatraman • Enterprise Systems and Software Lab • Hewlett-Packard

  2. Problem:Fast and Inexpensive Software Delivery Central server HP’s Internal Managed Service department Software synchronization Software package delivery • Waystations • Edge servers • Maintain all or few Linux distributions Customers

  3. Achieving Efficient Synchronization • One – to – many problem • Can we significantly improve performance? • Sure, combining P2P technology with rsync (currently used protocol and tool) • Use file swarming • Chop files into chunks (similar to rsync) • Disseminate files by exchanging chunks between peers • Verify data integrity using hashes obtained from the server • Rely on BitTorrent protocol

  4. Experimental Results • Using Emulab testbed • Examine issues when using synchronization with swarming • Large chunk sizes • Low per chunk overhead • Less opportunities to exploit similarity • Tradeoff between exploiting similarity and improving swarm performance

  5. Software Package Delivery • Avoid custom applications for software package delivery • Several different types of applications used • Decreasing customer request rate during the post flash crowd scenario • Increases the downloading time in a multiple file system as the server may have other workload • Avoid consuming the customer upload bandwidth • Can we provide enough bandwidth in an alternate way • Using Volunteer Assistance • Maximize the advantages, minimize the constraints

  6. Using Volunteer Assistance Server 2: Redirection 1: Request Software synchronization Software package delivery Tracker • Volunteers • (partial) mirrors 3: Send Customers

  7. Related Work • Content Delivery Networks (Akamai, CORAL) • Key differences • Customer is redirected to volunteer only when volunteer has the requested data • Server aided by tracker redirects the customer to the volunteers • Full decentralization can make security and optimization hard when using volunteers • Opportunity to make intelligent decisions at the tracker

  8. Ongoing Work • Load-balancing • Selection of volunteers to respond to customer requests • Tracker-based approach • Tracker collects synchronization information • What files on what volunteers • What volunteers are currently synchronizing their repository • Readily available without much overhead • Use this information to make better load balancing decisions • Future: Study data placement policies required to handlevolatilevolunteers • Allow individuals to donate idle machine time to improve the software delivery process • Use access patterns to replicate the packages

  9. purvi@cs.uh.edu Thank you Questions?

More Related