SLURM Accounts

Because the Allocations (i.e., SUs) that a PI is given have a particular purpose (condo, meritorious, startup, etc) and thus implicitly have a priority level, a different SLURM Account will be created for each of the SLURM Resource Allocations a PI has been given. To help PIs (and Users) keep track of their SLURM accounts, we define a convention for naming SLURM Accounts. (Note, we use the same convention for naming allocations of other types -- e.g., Ceph storage allocations, OpenStack allocations, etc.). Our convention is to concantenate the ResourceType (e.g., CPU, GPU, etc), the Allocation Purpose (e.g., Condo, Meritorious, etc), and the Instance (e.g., PKS2 Ceph or CoT Ceph) with the LinkblueID and ResearchProject name. An SLURM account name -- more generally knows as an Allocation Account name -- will have the following format:

where

• ResourceType is one of: (note that SLURM account names only use CPU and GPU)

  • c: for CPU

  • g: for GPU

  • o: for Object Storage

  • l: for GPFS Storage

  • a: for Archival Storage (GEMINI)

  • v: for OpenStack vCPU

  • m: for OpenStack Memory

  • d: for OpenStack Disk Storage

• Allocation Purpose is one of:

  • c: Condo Resource (implicit priority 1 -- the highest priority)

  • d: CCS discretionary (implicit priority 1)

  • s: Startup Resource(implicit priority 2)

  • m: Meritorious Research (implicit priority 2)

  • e: Educational (implicit priority 2)

  • i: Condo Incentive (implicit priority 3)

  • o: Open Access (implicit priority 4 -- the lowest priority)

• Instance is one of:

  • a: for MCC

  • l: for LCC (OpenHPC system consisting of McVey Broadwell/Skylake/P100/V100 CPU and GPU nodes)

  • p: for PKS2 Ceph Object Storage cluster

  • f: for CoT Ceph Object Storage cluster

  • o: for CoT OpenStack Cluster

  • k: for KyRIC OpenStack cluster

  • i: for KyRIC OpenHPC cluster (inside VMs)

  • j: for KyRIC OpenHPC cluster (bare metal, not in VMs). May not implement this is VMs work.

  • g: for GEMINI_1 storage cluster

• LinkblueID_ResearchProject is the ProjectName
  (see Projects)

For example, the SLURM Account name:

would refer to a Meritorious Research Allocation given to PI clp251 to be used on CPU nodes on the LCC for the Project next_gen_solar.

More generally, an Allocation account name such as:

would refer to a Meritorious Research Allocation given to PI clp251 in the form of Object Storage on the PKS2 ceph object store to be used for the Project next_gen_solar. In this case the Allocation account name would be used by a Ceph Object Store rather than the SLURM scheduler.

Note that a Project will likely only have an Allocation for one (or possibly a few) Purposes. For example a Project may only have a Startup Allocation or a Meritorious Allocation. A Project for a class, on the other hand, will only have an Educational Allocation. In short, SLURM account names will only be generated for the Allocations that have been awarded.