[OOD-users] minimal implementation of interactive apps

[E.M. Dragowsky]

Hi, Shawn --

This looks very useful -- Thanks!

On Fri, Sep 14, 2018 at 1:09 PM, Sivy, Shawn <ssivy at tcnj.edu> wrote:

> When testing an application, I hard code the options into the
> submit.yml.erb file as native SLURM options.  Below is a sample that
> basically translates to the following sbatch options:
>
> -N 1 -n 2 -J ondemand -p normal --nodelist=node001
>
> *submit.yml.erb*
> script:
>   native:
>     - "-N"
>     - "1"
>     - "-n"
>     - "2"
>     - "-J"
>     - "ondemand"
>     - "-p"
>     - "normal"
>     - "--nodelist"
>     - "node001"
>
> You can use the default form.yml variables for some of these entries.
> Others, like nodelist, would require you to create your own form variable.
> I remember seeing examples in some of the OOD docs.
>
> ------------------------------
> [image: The College of New Jersey] <http://tcnj.pages.tcnj.edu/> Shawn
> Sivy
> HPC System Administrator
> School of Science
> PO Box 7718 Ewing, NJ 08628-0718
> 609-771-3475
> ssivy at tcnj.edu <email at tcnj.edu>
>
>
> On Fri, Sep 14, 2018 at 12:51 PM E.M. Dragowsky <dragowsky at case.edu>
> wrote:
>
>> Hi, Eric, others --  Yes, I'm looking to restrict the submission of an
>> interactive job to the one node that I will initially configure to support
>> that. So I would not say that I'm looking for 'simpler' documentation. I'm
>> suggesting that my interest does seem captured by the existing
>> documentation.
>>
>> Maybe the simplest way to express my question, is there a similar entry
>> that I can make for 'form.yml', to restrict by feature? What I see for the
>> Jupyter form file is:
>> form:
>>   - modules
>>   - extra_jupyter_args
>>   - bc_account
>>   - bc_queue
>>   - bc_num_hours
>>   - bc_num_slots
>>   - bc_email_on_started
>>
>> Is there a bc_nodename? or a bc_feature entry to form.yml? Or would these
>> be implemented as extensions to the Jupyter app?
>>
>> Cheers,
>> ~ Em
>>
>>
>> On Fri, Sep 14, 2018 at 11:41 AM, Franz, Eric <efranz at osc.edu> wrote:
>>
>>> Dr. Dragowsky,
>>>
>>>
>>>
>>> Are you looking for something simpler than https://osc.github.io/ood-
>>> documentation/master/app-development/tutorials-
>>> interactive-apps/add-jupyter.html which includes Slurm specific details
>>> when submitting a job: https://osc.github.io/ood-
>>> documentation/master/app-development/tutorials-
>>> interactive-apps/add-jupyter/modify-submit-parameters.html#slurm? This
>>> tutorial uses the https://github.com/OSC/bc_example_jupyter git repo
>>> which you can clone and fork etc.
>>>
>>>
>>>
>>> Thanks,
>>>
>>> Eric
>>>
>>>
>>>
>>>
>>>
>>> ---
>>>
>>> Eric Franz, Senior Web & Interface App Engineer
>>>
>>> Ohio Supercomputer Center
>>>
>>> An Ohio Technology Consortium (OH-TECH) Member
>>>
>>> 1224 Kinnear Road
>>>
>>> Columbus, OH 43212
>>>
>>> email: efranz at osc.edu
>>>
>>>
>>>
>>> *From: *OOD-users <ood-users-bounces at lists.osc.edu> on behalf of "E.M.
>>> Dragowsky" <dragowsky at case.edu>
>>> *Reply-To: *User support mailing list for Open OnDemand <
>>> ood-users at lists.osc.edu>
>>> *Date: *Friday, September 14, 2018 at 11:37 AM
>>> *To: *User support mailing list for Open OnDemand <
>>> ood-users at lists.osc.edu>
>>> *Subject: *[OOD-users] minimal implementation of interactive apps
>>>
>>>
>>>
>>> At least for testing, I'd like to install turbovnc and websockify on
>>> just one compute node, and then further implement the jupyter app to just
>>> that one compute node before committing to implement jupyter app on the
>>> full cluster.
>>>
>>> Is the documentation to cover limiting cases? For me, I'm asking for the
>>> single compute node, but perhaps I'd also later want to restrict
>>> interactive apps by other means: by partition, by compute node features.
>>> We're using slurm, so if there are slurm-specific details, being pointed to
>>> that along with the general case documentation would be great.
>>>
>>> Thanks!
>>>
>>> ~ em
>>>
>>>
>>> --
>>>
>>> E.M. Dragowsky, Ph.D.
>>>
>>> Research Computing -- UTech
>>>
>>> Case Western Reserve University
>>>
>>> (216) 368-0082
>>>
>>> _______________________________________________
>>> OOD-users mailing list
>>> OOD-users at lists.osc.edu
>>> https://lists.osu.edu/mailman/listinfo/ood-users
>>>
>>>
>>
>>
>> --
>> E.M. Dragowsky, Ph.D.
>> Research Computing -- UTech
>> Case Western Reserve University
>> (216) 368-0082
>> _______________________________________________
>> OOD-users mailing list
>> OOD-users at lists.osc.edu
>> https://lists.osu.edu/mailman/listinfo/ood-users
>>
>
> _______________________________________________
> OOD-users mailing list
> OOD-users at lists.osc.edu
> https://lists.osu.edu/mailman/listinfo/ood-users
>
>


-- 
E.M. Dragowsky, Ph.D.
Research Computing -- UTech
Case Western Reserve University
(216) 368-0082
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osu.edu/pipermail/ood-users/attachments/20180914/4251e1ed/attachment-0001.html>