[tahoe-dev] using tahoe as a backend driver for irods storage system

[Terrell Russell]

Hi Jimmy,

I'm also sitting at the intersection of these two pieces of grid-aware
software.  I've copied the iRODS list on this reply.

I suspect the performance of Tahoe-LAFS will be a major bottleneck for
using the mass storage driver.  But that's just a hunch.  I'd love to
see real numbers for this kind of thing instead of my idle speculation.
 If you've already got your head around the pieces to build, give it a
go and see if it's usable.

Accessing web-accessible data through iRODS microservices is another option.

However, a third option, released in iRODS 3.0, is the already-included
microservice object (MSO) drivers:


  Microservice Object (MSO) Drivers [1]

  msiobjget_http - Gets an HTTP/HTTPS/FTP object [2]
  msiobjput_http - Puts an HTTP/HTTPS/FTP object [3]


Please keep in touch with what you decide - iRODS currently does not
provide encryption at the file-level, so a Tahoe-LAFS integration has
been interesting to me for a while as well.

Terrell


[1] https://irods.org/index.php/Micro-Service_Objects
[2]
https://www.irods.org/doxygen/mso_http_m_s_8c_acd744d04c89f78276533165d58d6a9c0.html
[3]
https://www.irods.org/doxygen/mso_http_m_s_8c_a2a85e8be4f14a4146f800f9808995b25.html



On 12/5/11 5:14 PM, Jimmy Tang wrote:
> Hi All,
> 
> I've been working on new project has a requirement for storing data in
> a trusted way, and having used tahoe-lafs myself for my own data I am
> now currently entertaining it for evaluation and deployment in a
> production system.
> 
> I was wondering if anyone has looked at integrating tahoe-lafs as a
> backend driver for iRODS using the universal mass storage driver? As I
> recall all I would need to implement in the driver is get, put, delete
> and stat (similar to what I had done with git-annex in the past). I'm
> just thinking whether the idea is crazy or would it be better to
> create a new microservice in iRODS to access the web api?
> 
> Thanks,
> Jimmy.
>