<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body>
<p>I have done that for several clients.</p>
<ol>
<li>Staging data is a pain. The simplest thing was to have it as
part of the job script, or have the job itself be dependent upon
a separate staging job. Where bandwidth is an issue, we have
implemented bbcp</li>
<li>Depending on size and connectivity, you can use hosts files or
create a subdomain for the cluster nodes. I prefer the latter.
Just use static IPs for your cloud nodes. You do need to ensure
connectivity with networks, etc. of course</li>
<li>SchedMD has the info on cloud nodes:
<a class="moz-txt-link-freetext" href="https://slurm.schedmd.com/elastic_computing.html">https://slurm.schedmd.com/elastic_computing.html</a></li>
<li>Try to isolate everything you use so it isn't overly dependent
on some other groups services (eg: DNS, authentication, etc)
unless you can be aware of any changes they are making so aren't
surprised. Also, avoid network mounts on nodes. Performance
takes a big hit when you have that going over a direct-connect
or VPN.</li>
</ol>
<p>Brian Andrus<br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 12/15/2020 12:02 PM, Sajesh Singh
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:BN8PR14MB2898AFB10A04A49AF99FE736ACC60@BN8PR14MB2898.namprd14.prod.outlook.com">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<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;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}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]-->
<div class="WordSection1">
<p class="MsoNormal">We are currently investigating the use of
the cloud scheduling features within an on-site Slurm
installation and was wondering if anyone had any experiences
that they wish to share of trying to use this feature. In
particular I am interested to know:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><a
href="https://slurm.schedmd.com/elastic_computing.html"
moz-do-not-send="true">https://slurm.schedmd.com/elastic_computing.html</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">1) Recommendations for staging the data
that was needed by the nodes in cloud<o:p></o:p></p>
<p class="MsoNormal">2) How did you handle name resolution<o:p></o:p></p>
<p class="MsoNormal">3) Any resources/documentation in
particular that proved helpful while setting up the
environment<o:p></o:p></p>
<p class="MsoNormal">4) Any bits of advise or horror stories
that may be helpful in avoiding pitfalls.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Regards,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">-SS-<o:p></o:p></p>
</div>
</blockquote>
</body>
</html>