[tahoe-dev] some questions about tahoe-lafs

[Paul Rabahy]

https://github.com/LeastAuthority/tahoe-lafs/tree/eaa6e22358f1fcf924b3b26094029fad14d72df7/src/allmydata/storage/backends/cloud
Shows
some work being done to support googlestorage, msazure, openstack, and s3.
I'm not sure how far along this is or if it has plans to get merged into
the mainline client, but there is some work on it.

On Thu, Jul 18, 2013 at 10:17 AM, Avi Freedman <freedman at freedman.net>wrote:

>
> I understand that opinion but I don't believe that will enable the
> largest growth of the LAFS-ecosystem.
>
> Maybe I'm wrong but I think the large mass of users will remain
> locked out of being able to install and configure daemons - but
> finding 10s or 100s providers to use that can offer S3, SWIFT, or
> is doable now - and doesn't diminish the market that (I think)
> LeastAuthority and Havenco are trying to address.
>
> As I said we'll summarize LAFS-related user feedback and in the
> mean time just try to help augment install and basic usage FAQs.
>
> Avi
>
> (Greg wrote:)
>
> > freedman at freedman.net (Avi Freedman) writes:
> >
> > > Right now I think you have to do FUSE mounts of S3 or webdav or
> something
> > > else and run the storage node on top of that but longer term I think
> > > being able to support no-software-install standard-protocol backend
> > > nodes as an option would be great for LAFS.
> >
> > This is IMHO a serious technical step backwards.  We have standard
> > interfaces and a narrow waist for filesystem interfaces, much like IP,
> > which means that tahoe does not need to know about all of these
> > backends.
>
> _______________________________________________
> tahoe-dev mailing list
> tahoe-dev at tahoe-lafs.org
> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20130718/c7c73844/attachment.html>