<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Dan,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Were you thinking of starting these on the web node, login node, or just any dedicated node to run these processes on demand, without the wait imposed by the queue?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We proposed to tackle this problem in the CSSI proposal that was recently awarded so this is on the roadmap for next year. We discussed possibly building a “fork” adapter that would implement the same interface as the job adapters, but
instead just fork + exec (or in your case, ssh + fork). The replacement for qstat would be a mixture of ps and inspecting /proc/<pid>; the “job id” would be the process id. qdel would just be kill. There would be problems introduced for process cleanup. Some
type of containerization would be helpful but then that would require escalated privileges, complicating the implementation. Or we might investigate using systemd for supporting the process management.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">At OSC we support such lightweight processing through a “quick cluster” to support “VDI” apps where jobs only get 1 core and we oversubscribe jobs on the nodes. That is explained in the relevant portions in this thread:
<a href="https://listsprd.osu.edu/pipermail/ood-users/2018-March/000122.html">https://listsprd.osu.edu/pipermail/ood-users/2018-March/000122.html</a>. While they use the same batch submission (the torque adapter, in OSC’s case), jobs typically take 10-30 seconds
to start instead of minutes. Would this approach work for you in the interim? Otherwise perhaps we could explore another option till a more robust “fork” adapter is available.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
<p class="MsoNormal">Eric<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">---<o:p></o:p></p>
<p class="MsoNormal">Eric Franz, Senior Web & Interface App Engineer<o:p></o:p></p>
<p class="MsoNormal">Ohio Supercomputer Center<o:p></o:p></p>
<p class="MsoNormal">An Ohio Technology Consortium (OH-TECH) Member<o:p></o:p></p>
<p class="MsoNormal">1224 Kinnear Road<o:p></o:p></p>
<p class="MsoNormal">Columbus, OH 43212<o:p></o:p></p>
</div>
<p class="MsoNormal">email: efranz@osc.edu<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">OOD-users <ood-users-bounces+efranz=osc.edu@lists.osc.edu> on behalf of Dan Dietz via OOD-users <ood-users@lists.osc.edu><br>
<b>Reply-To: </b>Dan Dietz <ddietz@purdue.edu>, User support mailing list for Open OnDemand <ood-users@lists.osc.edu><br>
<b>Date: </b>Tuesday, November 20, 2018 at 8:45 AM<br>
<b>To: </b>"ood-users@lists.osc.edu" <ood-users@lists.osc.edu><br>
<b>Subject: </b>[OOD-users] Launching apps outside job system<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I wonder if there is a way to launch the apps outside the job system, ie, directly on the cluster front-ends? We support running a few lightweight apps on cluster front-ends (visualizations, things like that). Is there a way to have it
just "ssh" instead of "qsub" to start an interactive session? <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Dan<br clear="all">
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">-- <o:p></o:p></p>
<div>
<div>
<div>
<p class="MsoNormal">Dan Dietz<br>
Senior Scientific Applications Analyst<br>
ITaP Research Computing, Purdue University<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>