nesi-ood-marimo-app/form.yml.erb at main · nesi/nesi-ood-marimo-app · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
<%-
  groups = OodSupport::User.new.groups.sort_by(&:id).tap { |groups|
    groups.unshift(groups.delete(OodSupport::Process.group))
  }.map(&:name).grep(/.*[0-9]{5}/)

  all_groups = OodSupport::User.new.groups.sort_by(&:id).tap { |groups|
    groups.unshift(groups.delete(OodSupport::Process.group))
  }.map(&:name)
  has_slurm_apps = all_groups.include?("nesi-staff") || all_groups.include?("ondemand-slurm-apps")
-%>

# Batch Connect app configuration file
#
# @note Used to define the submitted cluster, title, description, and
#   hard-coded/user-defined attributes that make up this Batch Connect app.
---
# Define attribute values that aren't meant to be modified by the user within
# the Dashboard form
attributes:

  # select the cluster
  cluster:
    widget: "select"
    options:
      - [
          "Kubernetes", "my-k8s-cluster",
          data-hide-gpu: true,
          data-set-gpu: 'none',
        ]
<% if has_slurm_apps %>
      - ["Slurm HPC", "nesi_tdc_hpc"]
    help: |
      Kubernetes jobs are more likely to start promptly - "Slurm HPC" jobs may have to wait in the queue.
      If you need GPUs then you must choose "Slurm HPC" currently.
<% end %>
    cacheable: false  # we always want k8s at the top?

  # allow user to choose which Marimo module is loaded
  marimo_module:
    widget: select
    label: "Marimo module"
    options:
      - [ "Marimo 0.20.3 + Python/3.11.6-foss-2023a", "Marimo/0.20.3-foss-2023a-Python-3.11.6" ]
    cacheable: false  # default to latest (first in list)

  account:
    label: "Project Code"
    widget: select
    options:
      <%- groups.each do |group| %>
      - "<%= group %>"
      <%- end %>
    required: true
    display: true

  bc_num_hours:
    max: 24
    min: 1
    step: 1
    value: 1
    widget: number_field

  num_cores:
    label: Number of cores
    min: 1
    value: 2
    max: 4
    widget: number_field
    display: true

  num_mem:
    label: Memory per job (GB)
    max: 32
    min: 4
    step: 1
    value: 4
    widget: number_field
    display: true

  gpu:
    label: GPU
    widget: select
    options:
      - 'none'
      - [ "L4 (24 GB VRAM, aimed at AI workloads, up to single precision)", 'L4' ]
      - [ "H100 (96 GB VRAM, recommend submitting as Slurm jobs due to potential wait times)", "H100" ]
    help: |
      **WARNING**: selecting a GPU can significantly increase the time it takes for your session to start!
    display: true

# All of the attributes that make up the Dashboard form (in respective order),
# and made available to the submit configuration file and the template ERB
# files
#
# @note You typically do not need to modify this unless you want to add a new
#   configurable value
# @note If an attribute listed below is hard-coded above in the `attributes`
#   option, then it will not appear in the form page that the user sees in the
#   Dashboard
form:
  - cluster
  - account
  - marimo_module
  - bc_num_hours
  - num_cores
  - num_mem
  - gpu
description: Request a Marimo Server
submit: submit.yml.erb
title: Marimo