Skip to content

Special use

Our cluster combines various hardware resources from multiple universities and other organizations. By default you can only use the nodes having NO Taints (see the resources page of the portal).

All taints

Here's the full list of taints on the nodes. To run on the node having a taint, you need to use the node toleration in your pod. Some are set automatically on deployed jobs by our cluster, some can only be used by privileged users. Please refer to this list and only set the ones you were allowed to use by cluster admins.

Taint Purpose Who can set manually
Public ARM64 node. Make sure your image supports it. All Ceph will not mount on the node. Otherwise the node is fine. All Node can only access the science DMZ network, and not the public Internet. All
Reserved for group use Measuring and monitoring for SENSE @jjgraham Reserved for the TIDE cluster @youngsu_kim CSUSB reserved nodes. Namespaces: csusb-chaseci, csusb-hpc, csusb-cousins-lab, csusb-jupyterhub, csusb-mpi, csusb-salloum, prp-dvu-csusb Private Hao Su cluster. Namespaces: ucsd-haosulab, ucsd-ravigroup, mc-lab Private use by Missouri researchers on Missouri resources Missouri Researchers RESERVED for PRISM Center @jjgraham Temporary limiting the RY nodes throughput, waiting for the 100G switch @dimm Private OSG nodes @fandri Limiting SDSU nodes throughput to SDSU only jobs all sdsu Reserved for a class to run LLMs until May 24 sdsu-llm Suncave head node is only used for suncave operations suncave
msu-cache Michigan State Cache for ATLAS @ivukotic
Set by system to user jobs Fence GPU nods from CPU jobs (Preferred! Jobs can still go on the node if there are no free CPU nodes) No Node accepts 4- and 8-GPU jobs only. Set automatically. No
Reserved for system use There's a GitLab issue describing the problem No Don't run any user jobs on ceph storage nodes No There's a GitLab issue describing the problem No Don't run any user jobs on linstor storage nodes No

Running in group namespaces

Our cluster contains several sets of nodes dedicated to certain groups.

User can target ONLY THE GROUP NODES by using the nodeAffinity such as:

        - matchExpressions:
          - key:
            operator: In
            - group1

for large jobs to avoid taking over all shared cluster resources. Optionally a higher priority can be used for such jobs (talk to admins before using one).

Other taints

Some nodes in the cluster don't have access to public Internet, and can only access educational network. They still can pull images from Docker Hub using a proxy.

If your workload is not using the public Internet resources, you might tolerate the and get access to additional nodes.