Policies and Procedures

Responsible Use of Computing Policy

Use of ORC systems and resources requires agreement and compliance with Mason policy: #1301, Responsible Use of Computing.

ORC General SLA

ORC systems and services are provided on a 24/7 best effort basis,  with an expectation of 95% availability.  There is no guarantee of support outside of normal working hours, but staff may ad hoc be able to resolve issues in off-hours.

ARGO Use Policies and Procedures

All file stored on Argo must be restricted to materials directly required for research being carried out on Argo.
Compute jobs should perform all data output to the scratch filesystem

      1. The scratch file system, while highly redundant, is not backed up. We cannot restore any files that are accidentally overwritten or deleted.
      2. Scratch directory use is not limited by quota. Files older than 90 days are deleted from the scratch filesystem on the first of every month.
      3. The age threshold for the file purge may change depending on scratch capacity.
      1. Home directories are backed up.
      2. Home directories are limited to a quota of 50 GB, which is subject to change upon review.
      3. File sharing from home directories is not supported. If file sharing is required this should be done through a project directory, a group directory, or from an external location such as the ORC GitLab server.
      4. Home directories are mounted read-only on all compute nodes.
      1. Faculty members may request a project directory with a capacity of up to 1 TB for shared project use.
      2. Project directories are mounted read-only on the compute nodes
      3. Project directories are not backed up.
      1. The head nodes are not to be used to run production work. Any long-running or compute-intensive tasks should be run on a cluster node using SLURM via either sbatch or salloc.
      2. There are no GPU devices on the head nodes.
      1. Instructors must give a minimum of 2 weeks’ notice prior to the start of class.
      2. If class-specific software is required please allow an additional 2 weeks notice to allow for software installation.
      3. Software for instructional use may also be subject to our general software request policies.
      4. Students in the class will be required to take our new user tutorial unless they already have access to the cluster. We will be happy to provide a special presentation of the tutorial by arrangement for entire class sections.
      5. Submit privilege will be suspended after the end of the class period, exceptions may be provided upon instructor approval.
      1. The ORC may be able to install software on the cluster on request. subject to conditions:
      2. The license terms and conditions must be reviewed and approved by Mason's legal council. This includes any open source or "free" software as well as any paid commercial software.
      3. Approved requests for new software installation will be reviewed within 3 working days to evaluate the complexity of the request.
      4. An estimate of the time required for installation will be provided and regular updates on progress provided.
MEMORI Storage Policies

      1. Data stored in volumes provisioned from MEMORI will be subject to regularly scheduled backup.
      2. Storage is provided at a base rate of $50 per terabyte per year. Payment is due at the start of the fiscal year and may be prorated.
      3. A sliding cost scale may be negotiated for purchases over 5 terabytes.
      4. MEMORI is not currently approved for the storage of CUI or other sensitive data.
      1. Daily between 1 AM and 5 AM.
      1. 1 month of daily backups (30)
      2. 3 months of weekly backups (12)
      3. 6x monthly backups (6).

VM Hosting Policies

      1. VMs will be provided based on available resources.
      2. ORC staff will provide support for OS-level installation, patching, and user account setup.
      3. Users will have local administrative access and will be responsible for application-level software installation and patching.
      4. VM requests that include public access will be conditional on review and approval by the Mason IT Security Office.
      5. VMs may be monitored by the Mason IT Security Office.
      6. VMs may be suspended at the request of the Mason IT Security Office if serious security issues are discovered.