[gram-user] SGE WS-GRAM integration - it works on CentOS 5.3 64bit after a simple trick

[Stuart Martin]

Thanks for this report Fabio.  We have heard a number of request for  
SGE to be supported by Globus.  We do plan to get to that soon.  We  
are focused on getting an initial version of GT 5.0.0 out the door.   
Then I think the first development task for GRAM will be to make  
available an SGE adapter for GRAM5.

-Stu

On Oct 27, 2009, at Oct 27, 9:41 AM, Fabio.Martinelli at esa.int wrote:

> I know WS-GRAM doesn't support Sun Grid Engine ( why??  ) but I'm  
> sure a
> lot of people like this great queue system, so I'd like share the
> installation experience I had integrating WS-GRAM/SGE on the new  
> CentOS
> 5.3 64bit linux cluster I'm building:
>
> I followed this procedure http://www.lesc.ic.ac.uk/projects/SGE-GT4.html
> with GT4.0.8 64bit and SGE6.2u4, it was fine, but then I spent 2 days
> trying to understand why the job submission phase doesn't work like in
> this case:
> [fmartine at scigrid ~]$ globusrun-ws -submit   -F scigrid.net4.lan: 
> 8443 -Ft
> SGE    -c /bin/hostname
> Submitting job...Done.
> Job ID: uuid:7aedf8a6-c2e1-11de-9571-0019b9f69014
> Termination time: 10/28/2009 10:14 GMT
> Current job state: Failed
> Destroying job...Done.
> globusrun-ws: Job failed: Error code: 201
> Script stderr:
> error: could not get environment variable SGE_QMASTER_PORT or service
> "sge_qmaster"
>
> [fmartine at scigrid ~]$
>
> I double checked everything, at the end it was a couple of rows to  
> insert
> in /etc/services like in this example:
>
> [fmartine at scigrid ~]$ grep sge /etc/services
> sge_qmaster     6444/tcp                        # Sun Grid Engine  
> Queue
> Master port
> sge_execd       6445/tcp                        # Sun Grid Engine
> Execution port
> [fmartine at scigrid ~]$
>
> perhaps it was obvious reading the error message but I hope this e- 
> mail is
> going to save those 2 days for an other admin !
>
>
>
>
>