Difference between revisions of "Development and Testing"

From UFRC
Jump to navigation Jump to search
Line 1: Line 1:
 
[[Category:Hardware]]
 
[[Category:Hardware]]
 
==Overview==
 
==Overview==
The test servers are available for software development and testing. If you need to develop code (i.e., the standard edit, build, test cycle) or test your workflows and scripts before submitting batch jobs, you should use these machines. The software environment on the test servers is kept consistent with that of the compute servers so you can run jobs and get an accurate idea of what resources are used.
+
If you need to develop code (i.e., the standard edit, build, test cycle) or test your workflows and scripts before submitting batch jobs, you should do it within an interactive developmental session under SLURM. The software environment on the nodes within the dev partition is kept consistent with that of the compute servers so you can run jobs and get an accurate idea of what resources are used.
  
Please remember that you are not allowed to run user applications on the login servers. Interactive work of any kind must be performed on a test machine. '''We ask that you limit the runtime of jobs on the test servers to thirty minutes or less.''' Note that violation of this policy may result in suspension of your UFRC account.
+
Please remember that you are not allowed to run user applications on the login servers. Interactive work of any kind must be performed in a developmental SLURM session.
  
 
==Access==
 
==Access==
Connect to the cluster (gator.rc.ufl.edu) and use the ssh command to access either of the test servers.
+
Connect to the cluster (ssh user@hpg2.rc.ufl.edu) and use SLURM to start a developmental session.
<pre>ssh dev1</pre> or <pre>ssh dev2</pre>
 
  
==Test Queue==
+
For example, to get a one-hour session with the default 1 processor core and 2gb of memory
There is a test queue you can use to test your job submission scripts. Please visit the [[Queues]] page for more information.
+
$ module load ufrc
 +
$ srundev --time=01:00:00
  
==Technical specifications==
+
The srundev command is a wrapper around the '<code>srun --partition=hpg2-dev --pty bash -i</code>' command.
Both dev1 and dev2 have the same technical specifications, as follows:
 
* Opteron 6378
 
* 2.4 GHz
 
* 64 cores
 
* 256 GB RAM
 
==HiPerGator 2.0==
 
Instructions for accessing HiPerGator 2.0 development nodes will be forthcoming soon.
 
  
The development node service will be handled via the SLURM scheduler and direct SSH access to the development nodes will not be available. This will allow Research Computing resources to be moved around as needed in order to facilitate development more thoroughly.
+
;Note: default time limit for the hpg2-dev partition is 00:10:00 (10 minutes). The maximum time limit in the dev partition is 12 hours.

Revision as of 21:54, 15 July 2016

Overview

If you need to develop code (i.e., the standard edit, build, test cycle) or test your workflows and scripts before submitting batch jobs, you should do it within an interactive developmental session under SLURM. The software environment on the nodes within the dev partition is kept consistent with that of the compute servers so you can run jobs and get an accurate idea of what resources are used.

Please remember that you are not allowed to run user applications on the login servers. Interactive work of any kind must be performed in a developmental SLURM session.

Access

Connect to the cluster (ssh user@hpg2.rc.ufl.edu) and use SLURM to start a developmental session.

For example, to get a one-hour session with the default 1 processor core and 2gb of memory

$ module load ufrc
$ srundev --time=01:00:00

The srundev command is a wrapper around the 'srun --partition=hpg2-dev --pty bash -i' command.

Note
default time limit for the hpg2-dev partition is 00:10:00 (10 minutes). The maximum time limit in the dev partition is 12 hours.