Hi Folks
Sorry this is so late - I had hoped to write this out in a more coherent
fashion, but I've got this chep paper still only 1/2 written...
Anyway, I hope it's a starting point - particularly the general
principle of publishing SEs as an abstract Glue service.
Graeme
PS. I've almost certainly got the actual Glue syntax horribly wrong
(sorry Stephen), but I think the struatural ideas are correct - see
section 2.2 of
http://infnforge.cnaf.infn.it/glueinfomodel/uploads/Spec/GLUEInfoModel_1_2_final.pdf
In response to some of Greig's ideas about SRMs handling more than one
filetype through their interfaces (I agree) we might have to publish
multiple SAs to represent each part of the SRM's capabilities. There's
no reason I can see that the GlueSAPaths even need to be different
(i.e., the actual storage model used is handled in the SRM v2
transaction, not encoded into the SURL in some hokey way).
Hope it's a start...
--
--------------------------------------------------------------------
Dr Graeme Stewart http://www.physics.gla.ac.uk/~graeme/
GridPP DM Wiki http://wiki.gridpp.ac.uk/wiki/Data_Management
|