[Swift-devel] Fwd: [gateways] Fwd: GRAM V5 Alpha 3 now available

[Stuart Martin]

True.  This will be one of the things we'll need to emphasize with  
gram5 admin/maintenance.  The problem with GRAM4 was not the SEG, but  
the entire container going down and no one noticing.  The SEG is just  
another process that needs to be running on a host.  The SEG will need  
to be included in the boot/startup script.  I think there are various  
programs/tools that people use to do this.  We will need to make this  
loud and clear and also provide an example or two for how to do this.

On Sep 18, 2009, at Sep 18, 8:26 AM, Mihael Hategan wrote:

> On Fri, 2009-09-18 at 08:01 -0500, Stuart Martin wrote:
>> Mike, Tibi,
>>
>> Do you have more job runs that you can send to this gram5 alpha3
>> deployment on queen bee?
>>
>> http://dev.globus.org/wiki/GRAM/GRAM5#Deployments_2
>>
>> 	• LSU Queen Bee cluster
>> 		• https://queenbee.loni-lsu.teragrid.org:2120/jobmanager-fork
>> 		• https://queenbee.loni-lsu.teragrid.org:2120/jobmanager-pbs
>>
>> Tibi, I think the problem in the past was that the head node was
>> rebooted and for a while the SEG was not running there.
>
> That was one of the big problems of WS-GRAM I think. Is there any  
> way to
> ensure that the history won't repeat itself with GRAM5?
>
>