[Swift-devel] Status of coasters

[Mats Rynge]

Michael Wilde wrote:
> So instead work with OSG to get WS-GRAM working?

There is a slow movement to make this happen. A couple of smaller VOs
(Engagement, which I'm representing, included) which are asking for
WS-GRAM to become a suggested/required service, but I don't think that
will happen for the next release.

I have heard that the new SEG for pre-WS GRAM will be included in the
next release of the OSG software stack.


> On 2/13/09 9:56 AM, Mats Rynge wrote:
>> Michael Wilde wrote:
>>> For sites where WS-GRAM is not functional, I suggested we consider
>>> configuring our own non-root WS-GRAM, ideally using already-installed
>>> GT4 software, eg, from the OSG package on OSG and TG sites where its
>>> installed. Mihael thought this would be considerable work. I agree but
>>> it might be a stable solution with fewer unknowns and suppot from the
>>> GRAM group. We can bring in the latest GT4 as needed if that provides a
>>> better solution than some older installed GT4 which we have no control
>>> over and which wont change till upcoming releases of say OSG or TG
>>> packages.
>>
>> Please don't do this on OSG. I'm fairly sure that working around the
>> existing interfaces to a resource would just tick off the resource
>> owners.
>>
> 


-- 
Mats Rynge
Renaissance Computing Institute <http://www.renci.org>