Roy:
There is a strong correspondence between the VOSpace v1 design and
the Storage Resource Manager design. SDSC is collaborating with
groups in the high-energy physics community to port SRM as an
interface on a SRB data grid. This will support simple access to
data. SDSC will also collaborate on a port of VOSpace as an
interface to a SRB collection.
Since the Amazon S3 interface is proprietary, I do not expect it will be ported on top of the SRB.
VOSpace, SRM, and Amazon S3 provide minimal access mechanisms to data that are being stored in other remote systems. A very interesting research issue is the number of additional capabilities that will be added in VOSpace v2 to improve the ability to manage the shared data. The corresponding set of management operations in the SRB environment now consists of over 80 different remote actions.
I have attached a report that describes many of the operational challenges in managing distributed data collections.
Reagan
>Dave & VOSpacers:
>
>Perhaps I can ask my questions more specifically.
>
>(1) Why not take the Amazon definition and just use that exactly?
>(2) What can Amazon do that VOSpace cannot (and why is that feature there?)
>(3) What can VOSpace do that Amazon cannot (and which use-case needs that?)
>(4) How does the metadata model differ between Amazon and VOSpace?
>(5) What are the differences in security model? If the VO model is
>different, why is it different?
>(6) What does VOSpace do that Amazon cannot (and who is demanding
>that extra feature?)
>(7) Is there a problem in implementing Amazon on top of SRB?
>
>Roy
>
>
>On Aug 17, 2006, at 6:07 AM, Dave Morris wrote:
>
>>Alasdair Allan wrote:
>>
>>>Roy Williams wrote:
>>>
>>>>I wonder what is common and what is different between Amazon S3
>>>>and VOSpace?
>>>>
>>>
>>>I think VOStore and Amazon S3 are very similar, VOSpace is
>>>something that could sit on top of both (wasn't there some
>>>mumbling about using S3 as one of the backends for VOStore?)
>>>
>>
>>Yes.
>>Once we get the initial inter-op services running, one of the
>>things I'd like to experiment with is a VOSpace service (facade)
>>that stores its data in an Amazon S3 account.
>>
>>Dave
>>
>
>California Institute of Technology
>
>626 395 3670