You will need to have the $SGE_ROOT dir available on your submit host.
$SGE_ROOT need not be shared, but at least the act_qmaster and a few configuration variables are
needed. You need to keep in mind that StarCluster uses the private IP & hostname, so you will need
to make sure that "act_qmaster" contains the public hostname & not the private one.
And you will need to add the host as submit host (qconf -as):
I *think* if you tar up the $SGE_ROOT dir on the master machine, untar it on your local machine, and point
the $SGE_ROOT env var to your local dir, adjust act_qmaster, and also have a local copy of qsub binary
available, then it *should* work. Try it with a 1-node test cluster (I usually use t1.micro for these types of things).
Open Grid Scheduler / Grid Engine
Scalable Grid Engine Support Program
From: Robert Yu <robert.yu_at_aditazz.com>
To: starcluster <starcluster_at_mit.edu>
Sent: Friday, February 24, 2012 3:07 PM
Subject: [StarCluster] sge submit host question
This is more of a best-practice question.
Let's say I am on machine A. From it, I create a cluster. I can then
ssh into the "master" and launch jobs. Can this also be done from
machine A directly? I know one can do "starcluster sshmaster -u
sgeadmin <clustername> 'some command'" but then I typically run into
environment issues. Is there (simple) a way to make machine A an sge
Robert Yu, Member Technical Staff
www.aditazz.com | robert.yu_at_aditazz.com
1111 Bayhill Drive Suite 260 | San Bruno | CA 94066
510.459.0216 | cell
650.627.7357 | 650.492.7000 x1008 | work
650.684.1149 | fax
StarCluster mailing list
Received on Fri Feb 24 2012 - 16:09:02 EST