AdvancedSlurm - Revision history

Nathanrwells: /* Bulk directory */

2025-08-20T15:43:29Z

Bulk directory

← Older revision		Revision as of 10:43, 20 August 2025
Line 273:		Line 273:
	===Bulk directory===		===Bulk directory===

	Bulk data storage may be provided at a cost of $45/TB/year billed monthly. ~~Due to the cost, directories will be~~ provided ~~when we are~~ contacted and provided with ~~payment~~ information.		Bulk data storage may be provided at a cost of $45/TB/year billed monthly. A bulk directory is provided once you have contacted Beocat systems administrators in a [https://support.ksu.edu/TDClient/30/Portal/Requests/ServiceDet?ID=44 TDX Ticket] and provided us with the appropriate billing information through your accounting department. We do not allow payments to be made through personal bank accounts or checks, bulk directories require a monthly billable account.

	===Fast Scratch file system===		===Fast Scratch file system===

Nathanrwells: /* Manually configuring your ACLs */

2025-06-26T13:47:39Z

Manually configuring your ACLs

← Older revision		Revision as of 08:47, 26 June 2025
Line 463:		Line 463:
	If your group does not own any nodes, you can still request a group name and manage the participants yourself		If your group does not own any nodes, you can still request a group name and manage the participants yourself
	by emailing us at		by emailing us at
	~~beocathelp@ksu.edu~~ or contact Beocat staff through a [https://support.ksu.edu/TDClient/30/Portal/Requests/ServiceDet?ID=44 TDX Ticket]		or contact Beocat staff through a [https://support.ksu.edu/TDClient/30/Portal/Requests/ServiceDet?ID=44 TDX Ticket] or emailing us at beocat@cs.ksu.edu
	.		.
	If you want to share a directory with only a few people you can manage your ACLs using individual usernames		If you want to share a directory with only a few people you can manage your ACLs using individual usernames

Nathanrwells: /* Running from a sbatch Submit Script */

2025-06-26T13:46:48Z

Running from a sbatch Submit Script

← Older revision		Revision as of 08:46, 26 June 2025
Line 207:		Line 207:
	## quick note here. Jobs requesting 16 or fewer cores tend to get scheduled		## quick note here. Jobs requesting 16 or fewer cores tend to get scheduled
	## fairly quickly. If you need a job that requires more than that, you might		## fairly quickly. If you need a job that requires more than that, you might
	## benefit from ~~emailing us at beocathelp@ksu.edu or contact~~ Beocat staff through a [https://support.ksu.edu/TDClient/30/Portal/Requests/ServiceDet?ID=44 TDX Ticket]		## benefit from contacting Beocat staff through a [https://support.ksu.edu/TDClient/30/Portal/Requests/ServiceDet?ID=44 TDX Ticket]
	## to see how we can assist in getting your		## to see how we can assist in getting your
	## job scheduled in a reasonable amount of time. Default is		## job scheduled in a reasonable amount of time. Default is

Nathanrwells at 20:18, 23 June 2025

2025-06-23T20:18:45Z

← Older revision		Revision as of 15:18, 23 June 2025
Line 207:		Line 207:
	## quick note here. Jobs requesting 16 or fewer cores tend to get scheduled		## quick note here. Jobs requesting 16 or fewer cores tend to get scheduled
	## fairly quickly. If you need a job that requires more than that, you might		## fairly quickly. If you need a job that requires more than that, you might
	## benefit from emailing us at ~~beocat~~@cs.ksu.edu to see how we can assist in		## benefit from emailing us at beocathelp@ksu.edu or contact Beocat staff through a [https://support.ksu.edu/TDClient/30/Portal/Requests/ServiceDet?ID=44 TDX Ticket]
	## ~~getting your~~ job scheduled in a reasonable amount of time. Default is		## to see how we can assist in getting your
			## job scheduled in a reasonable amount of time. Default is
	##SBATCH --cpus-per-task=1		##SBATCH --cpus-per-task=1
	##SBATCH --cpus-per-task=12		##SBATCH --cpus-per-task=12
Line 462:		Line 463:
	If your group does not own any nodes, you can still request a group name and manage the participants yourself		If your group does not own any nodes, you can still request a group name and manage the participants yourself
	by emailing us at		by emailing us at
	~~beocat~~@cs.ksu.edu		beocathelp@ksu.edu or contact Beocat staff through a [https://support.ksu.edu/TDClient/30/Portal/Requests/ServiceDet?ID=44 TDX Ticket]
	.		.
	If you want to share a directory with only a few people you can manage your ACLs using individual usernames		If you want to share a directory with only a few people you can manage your ACLs using individual usernames

Daveturner: /* Securing your home directory with the setacls script */

2025-01-13T22:37:51Z

Securing your home directory with the setacls script

← Older revision		Revision as of 17:37, 13 January 2025
Line 395:		Line 395:
	sharing the directory '''test_directory''' in my /bulk/daveturner directory with Nathan.		sharing the directory '''test_directory''' in my /bulk/daveturner directory with Nathan.

	<syntaxhighlight ~~lang=bash~~>		<syntaxhighlight>
	cd /bulk/daveturner		Beocat> cd /bulk/daveturner
	mkdir test_directory		Beocat> mkdir test_directory
	setacls -r -w -u nathanrwells -d /bulk/daveturner/test_directory		Beocat> setacls -r -w -u nathanrwells -d /bulk/daveturner/test_directory

	Opening up base directory /bulk/daveturner with X execute permission only		Opening up base directory /bulk/daveturner with X execute permission only
Line 418:		Line 418:
	other --- ---		other --- ---
	</syntaxhighlight>		</syntaxhighlight>

			The '''getfacl''' run by the script now shows that user '''nathanrwells''' has
			read and write permissions to that directory and execute access to all directories
			leading up to it.

	====Manually configuring your ACLs====		====Manually configuring your ACLs====

Daveturner: /* Securing your home directory with the setacls script */

2025-01-13T22:34:45Z

Securing your home directory with the setacls script

@@ Line 392: / Line 392: @@
 The script will set everything up for you, telling you the commands it is executing along the way,
-then show the resulting ACLs at the end with the '''getfacl''' command.
+then show the resulting ACLs at the end with the '''getfacl''' command.  Below is an example of
 ====Manually configuring your ACLs====

Daveturner: /* Securing your home directory with the setacls script */

2025-01-13T22:28:52Z

Securing your home directory with the setacls script

← Older revision		Revision as of 17:28, 13 January 2025
Line 373:		Line 373:
	If you do not wish to share files or directories with other users, you do not need to do anything		If you do not wish to share files or directories with other users, you do not need to do anything
	as rwx access to others has already been removed.		as rwx access to others has already been removed.
	If you want to share files or directories you can either use the setacls script or configure		If you want to share files or directories you can either use the '''setacls''' script or configure
	the ACLs (Access Control Lists) manually.		the ACLs (Access Control Lists) manually.

Line 396:		Line 396:
	====Manually configuring your ACLs====		====Manually configuring your ACLs====

	If you want to manually configure the ACLs you can use the directions below to do what the setacls		If you want to manually configure the ACLs you can use the directions below to do what the '''setacls'''
	script would do for you.		script would do for you.
	You first need to provide the minimum execute access to your /homes		You first need to provide the minimum execute access to your /homes

Mozes: /* CUDA */

2024-05-02T20:22:18Z

CUDA

← Older revision		Revision as of 15:22, 2 May 2024
Line 28:		Line 28:
	* geforce_rtx_2080_ti		* geforce_rtx_2080_ti
	* geforce_rtx_3090		* geforce_rtx_3090
			* l40s
	* quadro_gp100		* quadro_gp100
	* rtx_a4000		* rtx_a4000
			* rtx_a6000

	== Parallel Jobs ==		== Parallel Jobs ==

Mozes: /* File Access */

2023-08-09T19:56:20Z

File Access

← Older revision		Revision as of 14:56, 9 August 2023
Line 254:		Line 254:
	Beocat has a variety of options for storing and accessing your files.		Beocat has a variety of options for storing and accessing your files.
	Every user has a home directory for general use which is limited in size, has decent file access performance. Those needing more storage may purchase /bulk subdirectories which have the same decent performance		Every user has a home directory for general use which is limited in size, has decent file access performance. Those needing more storage may purchase /bulk subdirectories which have the same decent performance
	but are not backed up~~. The /scratch filesystem provides a temporary space to store intermediary files that are needed for multiple jobs, or for files that are larger than your home directory~~. The /fastscratch file system is a zfs host with lots of NVME drives provide much faster		but are not backed up. The /fastscratch file system is a zfs host with lots of NVME drives provide much faster
	temporary file access. When fast IO is critical to the application performance, access to /fastscratch, the local disk on each node, or to a		temporary file access. When fast IO is critical to the application performance, access to /fastscratch, the local disk on each node, or to a
	RAM disk are the best options.		RAM disk are the best options.

Mozes: /* Local disk */

2023-08-09T19:55:39Z

Local disk

← Older revision		Revision as of 14:55, 9 August 2023
Line 295:		Line 295:
	to a file on the local disk, then you'll need to copy any files you want off the local disk before		to a file on the local disk, then you'll need to copy any files you want off the local disk before
	the job finishes since Slurm will remove all files in your job's directory on /tmp on completion		the job finishes since Slurm will remove all files in your job's directory on /tmp on completion
	of the job or when it aborts~~. When we get the scratch file system working with Lustre, it may~~		of the job or when it aborts. Use 'kstat -l -h' to see how much /tmp space is available on each node.
	~~end up being faster than accessing local disk so we will post the access rates for each~~. Use 'kstat -l -h'
	to see how much /tmp space is available on each node.

	<syntaxhighlight lang=bash>		<syntaxhighlight lang=bash>