<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body dir="auto">
<div>Thanks Mich. on the advice of someone else I did something similar:</div>
<div><br>
</div>
<div>1) set initial-state on all.q to disabled</div>
<div>2) manually enable after manual provisioning check passes</div>
<div><br>
On Apr 14, 2014, at 7:19 AM, "François-Michel L'Heureux" <<a href="mailto:fmlheureux@datacratic.com">fmlheureux@datacratic.com</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div dir="ltr">Hi Stewart!
<div><br>
</div>
<div>I ran into a similar issue. I use a complex value to couter that situation. In steps:</div>
<div>
<ol>
<li>When creating a cluster, I add the complex value in OGS.</li><li>Whenever I run a job, I require that complex value. (See flag "-l" in qrsh/qsub)
</li><li>The last step I do when I initialize a node is add that complex value/resource to that node.</li></ol>
<div>Hence, if a job is queued, it cannot run on a uninitialized node because the complex value is missing. The downside is that you have to alter all your qsub/qrsh commands to request that parameter, otherwise they will bypass it. (It might be possible to
set it as a default requirement, I haven't looked.)</div>
</div>
<div><br>
</div>
<div>Good luck</div>
<div>Mich</div>
</div>
</div>
</blockquote>
</body>
</html>