...
| Warning |
|---|
Until pricing changes, users should be prepared for the $70 per TB per copy 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. |
Restrictions on data that can be stored on ROSS
There are few restrictions on the types of data that can be stored on ROSS. Almost anything is allowed, as long as the data storage complies with rules and regulations.
Keep in mind that any campuses that are participants in ARCC, and by extension, the Arkansas Research Platform (ARP), have access to ROSS. Unlike the UAMS Research NAS, which is locked down behind UAMS firewalls hence only accessible inside the UAMS Campus, ROSS is located in the ARCC Science DMZ, accessible by a number of campuses, both within Arkansas and potentially beyond. As such, it is inappropriate to store in ROSS fully identified patient (PHI) or personal (PII) data, as it could be a violation of UAMS HIPAA or FERPA policies. ROSS does have the ability to restrict access to buckets and to do server-side, data-at-rest encryption, but these capabilities have not been evaluated as to whether or not they are sufficient for HIPAA or FERPA compliance. For now, ROSS should not be used for data that is regulated by HIPAA, FERPA, or any other governmental regulation. De-identified human subject data is allowed.
In addition, by using ROSS, you agree that you are complying with any rules or restrictions place by your IRB protocol on data you store in ROSS.
| Warning |
|---|
Do not use ROSS for regulated data (e.g. data that must comply with HIPAA, FERPA, or other rules). If your data is sensitive, please turn on server side encryption. You are responsible for complying with any applicable IRB protocol. |
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
If
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.
...