gtr at ast.cam.ac.uk
Thu Aug 17 08:13:10 PDT 2006
On Thu, 17 Aug 2006, Roy Williams wrote:
> 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
> (3) What can VOSpace do that Amazon cannot (and which use-case needs
> (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?
VOSpace is specified to use IVOA security mechanisms which means that it
accepts RFC3820 certificates (i.e. Globus-style proxies). Almost nothing
other than Grid software knows about RFC3820; I'd be suprised if S3
does. This affects both digital signature (SOAP) and TLS (HTTP-Get)
> (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?
> 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
Guy Rixon gtr at ast.cam.ac.uk
Institute of Astronomy Tel: +44-1223-337542
Madingley Road, Cambridge, UK, CB3 0HA Fax: +44-1223-337523
More information about the vospace