gluster-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gluster-devel] Fwd: Using Bittorrent Protocol as basis for Geo-Repl


From: Theron Conrey
Subject: Re: [Gluster-devel] Fwd: Using Bittorrent Protocol as basis for Geo-Replication
Date: Wed, 11 Sep 2013 11:02:46 -0500

Thanks John Mark! 

I've been starting actually with murder, but it's really optimized for same datacenter style deployments.

Ideally, there'd be an open source version of Sync (bittornado libs?) that also allowed for a private tracker that could be setup as well.  This should be able to be public facing (same as bittorrent.com's ) to allow for private setups.  also (interestingly) there could be a gluster.org tracker created to host user test environments. 

Obviously such an awesome project should be dropped in the forge as a module for gluster :)

If anyone is interested in talking about this, please let me know!


On Wed, Sep 11, 2013 at 10:15 AM, John Mark Walker <address@hidden> wrote:
This is an interesting post:

http://blog.bittorrent.com/2013/09/10/sync-hacks-how-to-use-bittorrent-sync-as-geo-replication-for-storage/

I'm not necessarily recommending it, but it's an interesting way to create a geo-rep solution. It's copied from Theron Conrey's original blog post on the subject - http://conrey.org/2013/05/21/bittorrent-sync-as-geo-replication-for-storage/

Next step, for someone who wanted to continue this line of thought to its logical conclusion, is to perhaps use Murder, an open source project from Twitter:

    - https://blog.twitter.com/2010/murder-fast-datacenter-code-deploys-using-bittorrent

Murder is an unfortunately-named project for deploying binaries and code across a massively scaled web environment. It might be interesting to apply it to the geo-rep context.

-JM

_______________________________________________
Gluster-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/gluster-devel


reply via email to

[Prev in Thread] Current Thread [Next in Thread]