Kamiak Usage Policies and Guidelines
These policies and guidelines may be revised periodically by the CIRC advisory board.
By using resources associated with the Kamiak Cluster, you agree to the following:
- You agree to protect your access credentials in full accordance with Executive Policy #18, http://public.wsu.edu/~forms/HTML/EPM/EP18_User_ID_and_Password.htm. This policy strictly forbids the sharing of credentials with any other person, including colleagues and graduate assistants, or using your credentials within scripts or programs to automate login. You agree to report any known or suspected security breach or misuse of your access credentials immediately.
- You agree to respect intellectual property rights, observe confidentiality agreements, and comply with all applicable laws. Activities that appear to violate any laws may be reported to the proper authorities for investigation.
- Sponsors and Investors are responsible for properly vetting users working under their auspices and for the behavior of these users. You agree that Sponsors/Investors associated with your account are entitled to regulate, limit, suspend, or terminate your access.
- You agree that violations of Kamiak policies can result in loss of access to resources.
- You agree to acknowledge the use of Kamiak in publications. To make tracking acknowledgement easier, we suggest including the wording, “This research used resources from the Center for Institutional Research Computing at Washington State University.”
The following guidelines for using Kamiak have been agreed on by the CIRC advisory board:
- Kamiak resources are to be used primarily for research. They can be used for instruction only with prior approval from the system administrator. More information will be available as policies develop for alternative uses.
- Kamiak does not meet the standards of NIST 800-171, DoD 5220.22-M, HIPAA, EAR, or ITAR, and should not be used to process, store, or transmit information governed by these regulations. Users that process, store, or transmit data governed by the NIH Genomic Data Sharing Policy agree to comply with the “NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy”, and will adhere to computer security practices, including restricted-access file permission settings, that ensure that only authorized individuals can gain access to data files.
- All jobs must be run on compute resources and should be submitted to an appropriate job queue. Running jobs on any non-compute node is prohibited.
- Temporary scratch storage space is provided to all users as needed for their jobs. Scratch directories are subject to automatic deletion, without notice, when their time limit of two weeks expires.
- A “backfill” job queue is accessible to all Kamiak users and allows individuals without access to sponsored nodes to submit jobs. Jobs submitted to the backfill queue will be scheduled for execution on nodes with unused compute cycles and will be executed in accordance with the queueing policies that are established. Owners of sponsored nodes have priority on those nodes. Therefore, jobs submitted to the backfill queue may be preempted if the sponsor of the compute node on which a backfill job is running submits their own job. Users are responsible for ensuring that their jobs are designed with appropriate check-pointing in place in order to be able to restart efficiently in the event of preemption.
- Because Kamiak is a shared resource, you should try to gauge your needs accurately and avoid oversubscribing or undersubscribing in your requests for resources (nodes, CPUs, RAM or scratch storage). Users that repeatedly overuse or attempt to circumvent scheduling policies may have their access revoked.
- Investor nodes whose warranty has expired will remain in service in CIRC’s HPC clusters at the owners discretion, so long as they are maintained in a functional state by the owner and there are sufficient resources in the data center facility to support them. The node’s owner will be responsible for providing any needed funds for replacement parts, and CIRC will coordinate their purchase and installation. Decommissioned nodes will be returned to the owner, if they so choose, along with the chassis enclosure if enough nodes are returned to fill it.
- Licensed software may only be installed on CIRC HPC clusters if the license permits its use for research on multiple computers across a network. Users are responsible for ensuring that any software they install or request to be installed on CIRC HPC clusters abides by license agreements.
- Users shall comply with requests by CIRC staff regarding job submission and resource usage that are needed to prevent interruption or loss of service of the HPC cluster.
By accepting this agreement you accept the following limitations:
- User data on home and lab folders is backed up to tape twice a year. Additional backups beyond that are the responsibility of the user.
- All users and PI lab accounts receive a no-cost storage allocation of 100GB and 500GB respectively. Additional lab account storage can be rented on an annual basis through the CIRC service center. Lab account storage that exceeds the capacity of current storage rentals will be made read-only for one year and then archived to tape.
- Accounts that are not used for more than a year are subject to deletion. Access to Kamiak will end six months after you have left the university. If you wish access to continue, you must negotiate your status with Kamiak and with the owner of any storage you are using.
- Using Kamiak resources and services is at your own risk. The Kamiak support group will try to maintain a functional research computing resource but there are no guarantees that resources or services will be available at all times, that they will suit every purpose, or that data will never be lost or corrupted.
- Periodically, access to Kamiak will be unavailable for scheduled maintenance, upgrades or benchmarking. Notification of these events will be provided.
- Access to Kamiak may be unavailable without notification if hardware, software or other issues necessitate immediate maintenance for correction.