[tahoe-lafs-trac-stream] [Tahoe-LAFS] #78: Cater to rsync as a target Tahoe client.

[Tahoe-LAFS]

#78: Cater to rsync as a target Tahoe client.
----------------------------+----------------------------------------------
     Reporter:  nejucomo    |      Owner:  somebody
         Type:              |     Status:  new
  enhancement               |  Milestone:  undecided
     Priority:  minor       |    Version:  0.4.0
    Component:  code        |   Keywords:  enterprise backup encoding rsync
   Resolution:              |
Launchpad Bug:              |
----------------------------+----------------------------------------------
Changes (by lpirl):

 * cc: tahoe-lafs.org@… (added)


Old description:

> Imagine a scenario where a sysadmin of a large enterprise network needs
> to perform routine backups, and does so by rsyncing from many clients to
> one large raid storage device.
>
> What if they could replace the single large raid with a vdrive, and run
> tahoe storage nodes on each workstation, and have all of the client-side
> rsync automation work without change?
>
> If this use case is as common and the Tahoe replacement as useful as I
> believe it to be, it would behoove Tahoe to cater to rsync for both
> publication and retrieval.
>
> One sufficient support feature would be file-system emulation (fuse,
> WebDav, ...) which rsync can already use.  However, it may also be
> worthwhile to implement an rsync-specialized interface to Tahoe if the
> efficiency-gains-to-development-time tradeoff was right.

New description:

 Imagine a scenario where a sysadmin of a large enterprise network needs to
 perform routine backups, and does so by rsyncing from many clients to one
 large raid storage device.

 What if they could replace the single large raid with a vdrive, and run
 tahoe storage nodes on each workstation, and have all of the client-side
 rsync automation work without change?

 If this use case is as common and the Tahoe replacement as useful as I
 believe it to be, it would behoove Tahoe to cater to rsync for both
 publication and retrieval.

 One sufficient support feature would be file-system emulation (fuse,
 WebDav, ...) which rsync can already use.  However, it may also be
 worthwhile to implement an rsync-specialized interface to Tahoe if the
 efficiency-gains-to-development-time tradeoff was right.

--

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/78#comment:7>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage