This archive was generated by
How about using the SGE plugin (this one  not the baked-in setup) and a simple script-runner plugin (see  for the one I use), but having the SGE plugin last in the order. That way the setup script should run first, and then SGE will be configured second.
I have not tested this approach but in principal it will work.
So a sample config snippet:
# don't use baked-in SGE
disable_queue = True
# the order matters here
plugins = scriptrunner, sge
setup_class = starcluster.plugins.sge.SGEPlugin
master_is_exec_host = False
setup_class = scriptrunner.ScriptRunner
# note this is the path on the cluster itself, e.g., NFS drive.
node_startup_script = /path/to/script
On Jan 6, 2014, at 10:14 AM, Lyn Gerner wrote:
> Hi Folks,
> I need to make node-resource-specific SGE config changes everytime I add a new node. To avoid race conditions, I need to bring the node up in a disabled state, make the changes, then enable it for running jobs.
> I don't see a way to do this with StarCluster commands or config settings. Maybe I missed something.
> Could I get a best practice suggestion for how to achieve that set of interactions? I don't want to hack the SGE plugin if there's a better way.
> StarCluster mailing list
Received on Mon Jan 06 2014 - 20:02:49 EST