Computational Umbrella Accounts

On HiPerGator a Slurm account is created for each group that has allocated computational resources.

Umbrella accounts (groups) are a way to combine resources from multiple individual accounts under a single entity or to share resources among multiple groups.

Note

Access to the umbrella account just as for an individual group account is governed by group membership. Therefore, members of individual groups that combine their resources into an umbrella account must be added to the 'umbrella group' to access the resources. Since they will be secondary members of the umbrella group they must specify both the account and the qos in Slurm job resource requests.

#SBATCH --account=umbrella
#SBATCH --qos=umbrella

Use cases

Departmental Umbrella

A department or institute provides a shared account for multiple PIs to use. All members of the groups affiliated with the departnet must request support to be added to the umbrella group to access the resources and be approved by the umbrella group sponsor or manager. Since they will be secondary members of the umbrella group they must specify both the account and the qos in Slurm job resource requests.

   flowchart TD
   subgraph dept ["Departmental Umbrella"]
       direction LR
       A1["Group 1 (Storage/Compute)"] --> |Members| U1["Umbrella Group</br>Compute"]
       A2["Group 2 (Storage/Compute)"] --> |Members| U1["Umbrella Group</br>Compute"]
       A3["Group 3 (Storage/Compute)"] --> |Members| U1["Umbrella Group</br>Compute"]
    end
    style dept fill:#f0f9ff,stroke:#3182ce,stroke-width:2px,color:#1e3a8a

Single Sponsor

A single sponsor whose research team works on some regulated data projects, which must store data in a HITRUST project group. Computational resources remain in the main group's account where projects without regulated data are processed. Since all sponsored users already have primary membership in the main group they do not have to specify the account and qos in Slurm job resource requests.

   flowchart TD
   subgraph main ["Main Group Compute"]
       direction LR
       A1["Project group 1 (Storage)"] -->  U1["Main Group (compute/storage)"]
       A2["Project group 2 (Storage)"] -->  U1["Main Group (compute/storage)"]
       A3["Project group 3 (Storage)"] -->  U1["Main Group (compute/storage)"]
    end
    style main fill:#f0f9ff,stroke:#3182ce,stroke-width:2px,color:#1e3a8a

Collaborative Project

Sponsors in a collaboration want to combine their resources into a single account for shared resource use to be able to tackle larger projects. All members of the collaborating groups must be added to the umbrella group to access the resources. Since they will be secondary members of the umbrella group they must specify both the account and the qos in Slurm job resource requests. A single sponsor is responsible for the umbrella group and must approve all requests to add members to the umbrella group. The sponsor can designate other collaborating sponsors as managers of the umbrella group.

   flowchart TD
   subgraph collab ["Collaborative Umbrella"]
       direction LR
       A1["Group 1 (Storage)"] --> |Reallocate Compute| U1["Umbrella Group</br>(Compute)"]
       A2["Group 2 (Storage)"] --> |Reallocate Compute| U1["Umbrella Group</br>(Compute)"]
       A3["Group 3 (Storage)"] --> |Reallocate Compute| U1["Umbrella Group</br>(Compute)"]
   end
   style collab fill:#f0f9ff,stroke:#3182ce,stroke-width:2px,color:#1e3a8a