Managing Research Computing allocations using the Resource Management Portal

Summary

How to view and update Research Computing Storage allocations using the Resource Management Portal (RMP) tool.

Environment

The RMP manages research computing allocations on the following systems:

  • Great Lakes
  • Armis 2

The RMP will allow you to show most information about a Research Computing Storage allocation (detailed below), but will not allow any changes except for updates to the lists of users allowed to access the allocation.

Directions

Accessing an existing Project

  1. Navigate to the Resource Management Portal (RMP) 
  2. Select the project from the list of project cards shown.  (You can toggle between card and list view using the icons immediately above and to the right of the project display.) Usually a project is named with the PI uniqname, but course and lab projects exist as well.
  3. On the project page that appears, the left pane shows all compute and storage resources allocated to the project.  Project Overview returns to the project page from any subordinate page.
  4. The right pane shows a card for each resource allocated to the project; for each research computing resource, the root computing account for the PI is shown, usually of the form uniqname_root.  The pane also shows a Project Admins and a Support Teams card listing all users and groups with administrative control over the volume, respectively; users may be added and removed from the former.  Projects->All Projects at the top returns to the list of projects page.

Accessing and Modifying a Research Computing Allocation (Great Lakes and Armis2)

  1. Click the root account you'd like to access.  Each PI, course, or lab has a single root account.
  2. Information shown includes
    • CPU and GPU limits shared by all subaccounts of the root account.  These are cluster-level limits imposed by the cluster operators.
    • The amount and percentage of  the maximum limit of /scratch storage space used by all subaccounts
    • The count and percentage of the maximum limit of all files created by all subaccounts
    • A list of all subaccounts of the PI root account.  Subaccounts ending in the digit zero represent RCP allocations, others are PI- or lab-funded.  For the latter, the limit period (monthly, annual, etc.) and funds remaining for that period are shown, along with CPU/GPU limits for that subaccount.  RCP accounts show the number of remaining core-hour credits.
    • Clicking the subaccount reveals a subaccount pane which shows
  3. Click the subaccount you'd like to access.  There can be many subaccounts for each root account.  Information shown for each subaccount includes:
    • The subaccount limits in more detail
    • The core-hour credits currently remaining in the subaccount, along with a rate conversion table converting those credits into core-hours for each partition.  Resources in different partitions are charged at different rates based on the differential capabilities of resources located in those partitions.
    • A list of users with limits different from the subaccount limit.  Such users can be added and removed by sending an email to arc-support@umich.edu giving the desired user-level limits to be imposed on each user added.
    • A list of users with no separate user-level limits.  Such users are subject to the account-level limits and can be added and removed directly from this pane. 
    • Finally, the Financials tab shows the funding sources and percentage contributed by each to the subaccount.

Note:  accounts should be set up with a $100 per month default limit.  Although it is possible to configure an account with no account- or user-level limits, this is not wise. 

Any modifications made in RMP will become visible in about an hour.

External Resources

Resource Management Portal (ARC documentation)

Print Article