Policies
From UF HPC Wiki
Contents |
Account Expiration
Account passwords expire after six months. If, after six months from your password expiring, you have not reset it, your account will be removed from the system.
Account passwords can be reset from the Account Creation Page.
No Interactive Jobs on Submit
The host "submit" (submit.hpc.ufl.edu) is the login host and primary gateway to the cluster. It provides a software environment essentially identical to that found on the cluster nodes and is intended as a platform for
- submitting jobs to the batch queues
- compiling and linking executables (i.e. building code)
- managing files
Because of the importance of this host to a large number of users, it must not be used for testing or running user programs under any circumstances. There are other facilities for this (see below). Users found running jobs interactively on submit will lose access to the cluster for thirty (30) days. If a second offense occurs, the user's account will be permanently disabled.
No personal or class-related work
The cluster is strictly for faculty-sponsored research and is not to be used by students for class assignments.
Data is NOT backed up
No data - not even home directories - is backed up. Please copy any data which you cannot afford to lose to your group's or department's storage on a regular basis. We make every effort to maintain the consistency and integrity of the cluster's file systems. However, it is inevitable that we will, at some point, lose data. Don't let it be yours.
All Job I/O should occur in the scratch areas
The home directory file system (/home) is not designed to withstand the load of hundreds of jobs performing I/O simultaneously and will become unresponsive under such circumstances. The scratch file systems (/scratch/ufhpc and /scratch/crn) are designed and intended for this purpose. Therefore, all job I/O should take place on the scratch file systems.
No Archiving of Data
The data storage facilities of the HPC Center are not to be used as a repository or archive for old data or data from other sites. The storage on the cluster exists for the sole purpose of supporting current projects and calculations. Once you have the results you need and the data has been analyzed, it should be deleted from the cluster. If you need to save copies, you must do so on your own or your department's systems.
Code Development
If you need to develop code (i.e. the standard edit, build, test cycle), there are several machines on which you can do so and run short interactive tests. They are
- test04 (8 Cores, 16 GB RAM)
- test05 (8 Cores, 16 GB RAM)
Gridusers Mailing list
All account holders will be subscribed to the Gridusers mailing list. This list is in place for so that users can be notified of events that occur to the cluster that would affect their job submissions.
