...
For data that meets OURRstore requirements (relatively static, STEM related, not clinical nor regulated), archiving to OURRstore is a very cost effective option to get resilient, long-term, offsite copies for little extra money (just media and shipping costs). Other options include the UAMS campus Research NAS or cloud storage. USB or bare drives are also an option, but not recommended, as they are quite error prone if not stored and managed properly.
| Info |
|---|
If you are unfamiliar with the object storage terms that ROSS documents use, we recommend reading the Access to the Research Object Store System (ROSS) article on this wiki for an overview. |
Costs for using ROSS
The College of Medicine (COM) Associate Dean of Research, in consultation with an advisory group at UAMS, recommended charging $70 per TB for the use of ROSS, good for the 5 year life of the storage as an up-front payment. This is less than half the current replacement plus maintenance cost for the underlying hardware ($159 per TB). If one wants replicated storage (i.e. one copy in Little Rock, one copy in Fayetteville), the cost would be double, or $140 per TB for the pair of copies.
...
| Warning |
|---|
Until pricing changes, users should be prepared for the $70 per TB per copy up front pricing set by the COM. Although we are not collecting fees at the moment, retroactive fee collection could begin after the ARCC steering committee settles on the fee schedule. Any storage in use at the time that ARCC sets the fee schedule would be charged the lower of the $70 fee imposed by COM, or the new fees set by ARCC for 5 years of storage. , retaining the remainder of the 5 year life. Additional storage would be charged at the fee schedule set by ARCC. |
Restrictions on data that can be stored on ROSS
...
The server-side encryption can either be turned on at the namespace level, where all buckets in a namespace are required to be encrypted, or on the bucket level for namespaces that do not have encryption required. If you want namespace level encryption, please inform the HPC admins when requesting a namespace. The encryption choice must be made at namespace or bucket creation time, and cannot be changed afterwards. (One can copy data from an unencrypted bucket to an encrypted one, then destroy the unencrypted bucket.)
Requesting access to ROSS
| Info |
|---|
| Before requesting access to ROSS, in addition to reading this article, please also read the Access to the Research Object Store System (ROSS) article on this wiki. |
To initiate access to ROSS for a new personal or group (e.g. project, lab, department) namespace, please send a request via e-mail to HPCAdmin@uams.edu. In your request, please indicate approximately how much space you intend to use in ROSS for the requested namepace. The HPC Admins will use this information in setting the initial quotas. You will be allowed to request increases in quota if needed. We would also appreciate a brief description of what you will be using the storage for.
If you wish to access an existing group namespace as an object user, please contact the namespace administrator for that namespace and ask to be added as an object user for that namespace.
Using ROSS
ROSS supports multiple object protocols. The most common is S3, followed by Swift (from the Open Stack family). Although ROSS can support the NFS protocol, our experiments show that the native NFS support is slower for many use cases than other options that simply emulate a POSIX file system using object protocols. ROSS can also support HDFS (used in Hadoop clusters) and a couple of Dell/EMC proprietary protocols (ATMOS and CAS); however, we have not tested any of these other protocols, hence the HPC Admins could only offer limited support for these other options. The primary protocols that the HPC Admins support are S3 and Swift. We have more experience with S3.
...