Summary
Provides a road map for administering storage at LSA, including a decision tree pointing to detailed support articles by topic.
Environment
- Data Den
- Globus
- Locker
- Turbo
LSA Research Storage
LSA Technology Services has partnered with U-M Information Technology Services (ITS) to offer storage for regular and sensitive research data at no cost with the LSA Research Storage Funding Model. LSA's storage model allows for 10TB of Turbo research storage covered through the University of Michigan Research Computing Package (UMRCP) and up to an additional 90TB covered by LSA. Partial allocations of this additional 90TB will be given as needed after consult with the HPC Storage team. LSA’s storage model also provides unlimited Data Den archival storage.
Generally, tenure-track, guest, and emeritus faculty, lecturers, and self-funded research scientists and post docs are eligible for UMRCP resources. PhD students may be eligible depending on the situation. Undergraduate and Masters students are not currently eligible, although they may be added to someone else's UMRCP resources. See the UMRCP Criteria for details.
Turbo volumes can be mounted on Great Lakes for non-sensitive data or on Armis2 for sensitive data, as well as on individual lab machines
The Service Request System (SRS) is used to create, display, monitor, and update administrative data about Research Storage. The Resource Management Portal (RMP) is used to display more detailed usage data about resources including both Research Storage and Research Computing, but does not allow updates other than to the lists of users allowed to access a given resource. Use SRS to add or remove shortcodes, adjust volume sizes, add or remove volume export lists and cluster mount points, and other storage-related requests. Use RMP to see up-to-date resource availability, consumption, and projected exhaustion, resource administrators and groups, individual user and account resource limits, and, for storage, mount paths and storage snapshots. See related article "Selecting between the Service Request System and the Resource Management Portal when managing research computing and storage services" for more detailed differentials.
Further documentation
This section provides pointers to detailed documentation for this topic and a non-exhaustive list of sample user requests.
Tier 1 Support, including Service Desk:
Here are some representative examples of issues that should be routed to Tier 2 support. Tier 2 may consult with or route to LSA unit support as appropriate.
- PI wants help in moving/monitoring/archiving/deleting storage
- PI wants an existing RCP/LSA Research Storage volume mounted on their workstations or lab server machines
- Will need to ensure the lsa-uniqname-turbo groups are added to Linux machines and the proper users added to those groups. Machines using AD should inherit those automatically.
- PI wants specific permissions set up on the volume, to restrict some directories to a subset of users, etc.
- PI has issues with permissions in Turbo and cannot change them due to default ACLs set on the volume (usually inheritance issues)
- PI already has other UMRCP services and needs to have Turbo and/or Data Den added
- UMRCP storage volumes are already set up but users are not able to access the volumes due to the Portal and/or AD groups not syncing properly with MCommunity groups
- PI says "I'm running my app in my lab and it is taking days to finish, I'd like another option"
- PI has a MiStorage volume and has not signed up for the UMRCP and does not respond to emails asking them to sign up
- PI has existing volume that needs to be covered by UMRCP (less likely now)
- PI was automatically enrolled in the UMRCP so is unable to sign up through the Portal and manual changes or additions to storage services are needed (less likely now)
External resources