Jupyter (or other interactive batch app) restriction to partitions

Get Help
1

Hi. We’ve got a Jupyter Notebook Server deployed on a Slurm cluster, based essentially on the tutorial.

Open Ondemand is installed/configured using the OSC ansible role.

Our config looks like this:

title: Jupyter Notebook
  description: Request a Jupyter Notebook server
  cluster: slurm
  form:
    - modules
    - extra_jupyter_args
    - bc_queue
    - bc_num_hours
    - num_cores
    - node
  attributes:
    num_cores:
      label: Number of cores
      value: 1
    modules: ""
    extra_jupyter_args: ""
    bc_queue:
      value: "{{ openondemand_jupyter_partition | default(none) }}"
    node: ""
  submit: |
    ---
    batch_connect:
      template: "basic"
    script:
      job_name: "ood-jupyter"
      native:
        - <%= "--nodes=1" %>
        - <%= "--ntasks=#{num_cores}" %>
        - <%= "--nodelist=#{node}" %>

As far as I understand it, the bc_queue.value property is just setting the default queue/partition to use? And users can select another on the form.

If we want to support multiple partitions, how can we define/restrict which partitions are even available via the form?

2

We do have the auto_queues feature which presents the queues as a select widget.

https://osc.github.io/ood-documentation/latest/how-tos/app-development/interactive/form.html?highlight=auto_queues

Is this the type of thing you were looking for?