UMRCP requests will come in on a single ticket which we call ticket zero. The following is an overview of all the steps for the maximum amount of resources that a PI can request.

• The total award for an HPC account can be 80,000 core hours. This can be split in any ration between Great Lakes and Armis2.
• Turbo is allotted 10TB total. If the user wishes to split their award between a non-sensitive and sensitive volume then they also have the ability to adjust the ratio so that the sum of each volume is 10TB. Each Turbo volume includes replication and snapshots. 
  • If a PI has an existing volume less than 10T the volume will be increased to 10T. If the volume is above 10T the UMRCP will cover the first 10T.
• Data Den is allotted 100TB.
  • If a PI has an existing volume it will be increased to 100T. If the volume is above 100T the UMRCP will cover the fist 100T. 

Here is the workflow for a UMRCP request: 

[

• PIs will submit a request for UMRCP resources and can request up to 5 options using web portal.  This will create a master ticket for the request.  This will be known as ticket zero.  It consists of the following request information:

  • Great Lakes HPC account
  • Armis2 HPC account
  • Turbo non-sensitive volume
  • Turbo sensitive volume
  • Data Den volume

• The process of creating ticket zero will also create up to four MCommunity groups: 

  • One <arcts>-<pi_uniqname>-<admins> admin group
  • Up to three user groups for the storage volumes. These group names will be shown in the information on ticket zero. 
    • They will generally have the names (you will need to check the UMNRCP form for the exact volume names):
      • <school>-<volume_name>-<turbo> (non-sensitive and/or sensitive)
      • <school>-<volume_name>-<dataden>

• The first step will be to confirm eligibility for new requests.   **Do not worry about this step at this time.  Brock is working to resolve questionable requests. ** Start with requests that are by Assistant, Associate, and Full Professors and set any ticket status on questionable tickets to <Scheduled> in TDx, to signify a need to review. 

• Ticket zero may have one or more requests for HPC resources. The ticket will automatically create a ticket task for each HPC request. ***Assign the ticket tasks to ITS-ARCTS-hpc. ***\
  • The information in the ticket task is copied in whole and submitted to the slurm_ops database. This information is known as a blob. 
  • The accounts get created on the cluster(s) requested. A `0` is added to the end of the PIs uniqname to indicate the account is part of the UMRCP. 
  • Once the blobs have been inserted into the slurm_ops database and accounts have been created the tasks on the ticket can be closed and the PI updated on the status of those resources. 
  • If you are to respond to the requestor on ticket zero you can use the pre-formatted responses fond on the following like. Make sure to update the sections shown in bold:
    • https://docs.google.com/document/d/1P86ESuC4brBtcD7HQQAm75hJ3mmdWD0YU389bLifrtw/edit

Detailed instructions on creating HPC accounts can be found here:

• Creating UMRCP HPC accounts

The Storage team and it's friends are responsible for multiple steps in the workflow:

1. Delegating AD Group creation for new volumes and associated tasks
2. Creating SRS records for new volumes and associated tasks. 
3. Creating the new volumes, pull requests for mounts on ARC resources, /etc/group entries for ARC resources. 

• Ticket zero may also have up to three storage requests: non-sensitive Turbo, sensitive Turbo, and Data Den. The tasks for this are NOT pre-created by UMRCP portal, at this time, because there are variances if it's an existing storage user or a new storage user.  

There are several steps that are required to fulfill a storage request for the UMRCP. They can be divided into new user requests and existing user requests. These can be differentiated on the UMRCP request in the title of the ticket.  We keep track of all of the tickets in various parts of the workflow here.  As tickets enter the first step and move from step to step, they should be recorded on that spreadsheet.

https://docs.google.com/spreadsheets/d/1Z1hT0rVDOVRMTgAI4hFjWSbiI37fd_bFQvDbUaHzxG8/edit#gid=0

Each has their own requirements and are documented in the following pages:

• UMRCP New Storage User
• UMRCP Existing Storage User

Detailed instructions for provisioning Turbo volumes please visit these pages:

• Creating Non-Sensitive Turbo volumes

• Creating Sensitive Turbo volumes