SLURM VNC interactive jobs - Revision history

Wwarr@uab.edu at 22:55, 24 June 2021

2021-06-24T22:55:33Z

← Older revision		Revision as of 22:55, 24 June 2021
Line 1:		Line 1:
	~~==Notice==~~		'''Notice:''' It is now possible to access a VNC-like desktop environment from our [[Open_OnDemand\|Open OnDemand]] web portal.
	'''~~This page contains outdated information.~~''' ~~While the method outlined here should still work, the easiest way~~ to access a VNC-like desktop ~~on Cheaha is to use the~~ [[Open_OnDemand\|Open OnDemand]] web portal ~~to create and access an Interactive HPC Desktop job through your web browser~~.

	==Using VNC session ==		==Using VNC session ==

Wwarr@uab.edu: Added note about preferring Open OnDemand

2021-06-24T22:51:17Z

Added note about preferring Open OnDemand

← Older revision		Revision as of 22:51, 24 June 2021
Line 1:		Line 1:
			==Notice==
			'''This page contains outdated information.''' While the method outlined here should still work, the easiest way to access a VNC-like desktop on Cheaha is to use the [[Open_OnDemand\|Open OnDemand]] web portal to create and access an Interactive HPC Desktop job through your web browser.

	==Using VNC session ==		==Using VNC session ==
	Please refer to our [[Setting_Up_VNC_Session\|VNC setup guide]] to start a VNC session with Cheaha login node. After getting your VNC desktop, you can get a compute node resource using the '''sinteractive''' command. A '''sinteractive''' session launched through VNC won't get terminated even if your SSH or VNC window is closed. Of course, it will get terminated after specified run-time is reached.		Please refer to our [[Setting_Up_VNC_Session\|VNC setup guide]] to start a VNC session with Cheaha login node. After getting your VNC desktop, you can get a compute node resource using the '''sinteractive''' command. A '''sinteractive''' session launched through VNC won't get terminated even if your SSH or VNC window is closed. Of course, it will get terminated after specified run-time is reached.

Tanthony@uab.edu: /* Interactive Resources */

2016-03-01T20:11:09Z

Interactive Resources

← Older revision		Revision as of 20:11, 1 March 2016
Line 10:		Line 10:
	Interactive jobs are requested with the sinteractive command (please use your correct email address in place of the ''$USER@uab.edu'' string if you do not have an @uab.edu email address):		Interactive jobs are requested with the sinteractive command (please use your correct email address in place of the ''$USER@uab.edu'' string if you do not have an @uab.edu email address):
	<pre>		<pre>
	sinteractive -N1 --time=120 --mail-user $USER@uab.edu --mail-type begin,end,fail		sinteractive --nodes=1 --time=120 --mail-user=$USER@uab.edu --mail-type=begin,end,fail
	</pre>		</pre>

	This command requests 1 node (24 cores) with entire allocation of RAM on the node for 120 minutes (2 hours). The command will wait until the resource is reserved by the scheduler and send you an email when the resource is available. The email alert can be useful during periods of heavy cluster demand when interactive resources reservations may have significant wait times.		This command requests 1 node (24 cores) with entire allocation of RAM on the node for 120 minutes (2 hours). The command will wait until the resource is reserved by the scheduler and send you an email when the resource is available. The email alert can be useful during periods of heavy cluster demand when interactive resources reservations may have significant wait times.

Tanthony@uab.edu: /* Interactive Resources */

2016-03-01T19:47:20Z

Interactive Resources

← Older revision		Revision as of 19:47, 1 March 2016
Line 4:		Line 4:
	= Interactive Resources =		= Interactive Resources =

	After you login to Cheaha the command-line interface that you see is running on the login node. Most of your light interactive prep-work to submit a compute job to the scheduler can be carried out on this ~~head~~ node. If you have a heavier workload to prepare for a batch job (eg. compiling code or other manipulations of data) or your compute application requires interactive control, you should request a dedicated interactive node for this work.		After you login to Cheaha the command-line interface that you see is running on the login node. Most of your light interactive prep-work to submit a compute job to the scheduler can be carried out on this login node. If you have a heavier workload to prepare for a batch job (eg. compiling code or other manipulations of data) or your compute application requires interactive control, you should request a dedicated interactive node for this work.

	Interactive resources are requested by submitting an "interactive" job to the scheduler. Interactive jobs will provide you a command line on a compute resource that you can use just like you would the command line on the ~~head~~ node. The difference is that the scheduler has dedicated the requested resources to your job and you can run your interactive commands without having to worry about impacting other users on the ~~head~~ node.		Interactive resources are requested by submitting an "interactive" job to the scheduler. Interactive jobs will provide you a command line on a compute resource that you can use just like you would the command line on the login node. The difference is that the scheduler has dedicated the requested resources to your job and you can run your interactive commands without having to worry about impacting other users on the login node.

	Interactive jobs are requested with the sinteractive command (please use your correct email address in place of the ''$USER@uab.edu'' string if you do not have an @uab.edu email address):		Interactive jobs are requested with the sinteractive command (please use your correct email address in place of the ''$USER@uab.edu'' string if you do not have an @uab.edu email address):

Tanthony@uab.edu: /* Using VNC session */

2016-03-01T19:46:46Z

Using VNC session

← Older revision		Revision as of 19:46, 1 March 2016
Line 1:		Line 1:
	==Using VNC session ==		==Using VNC session ==
	Please refer to our [[Setting_Up_VNC_Session\|VNC setup guide]] to start a VNC session with Cheaha ~~head~~ node. After getting your VNC desktop, you can get a compute node resource using the '''sinteractive''' command. A '''sinteractive''' session launched through VNC won't get terminated even if your SSH or VNC window is closed. Of course, it will get terminated after specified run-time is reached.		Please refer to our [[Setting_Up_VNC_Session\|VNC setup guide]] to start a VNC session with Cheaha login node. After getting your VNC desktop, you can get a compute node resource using the '''sinteractive''' command. A '''sinteractive''' session launched through VNC won't get terminated even if your SSH or VNC window is closed. Of course, it will get terminated after specified run-time is reached.


	= Interactive Resources =		= Interactive Resources =

Tanthony@uab.edu: /* Interactive Resources */

2016-03-01T18:18:58Z

Interactive Resources

← Older revision		Revision as of 18:18, 1 March 2016
Line 11:		Line 11:
	Interactive jobs are requested with the sinteractive command (please use your correct email address in place of the ''$USER@uab.edu'' string if you do not have an @uab.edu email address):		Interactive jobs are requested with the sinteractive command (please use your correct email address in place of the ''$USER@uab.edu'' string if you do not have an @uab.edu email address):
	<pre>		<pre>
	sinteractive -N1 --time=120 --mail-user $~~user~~@uab.edu --mail-type begin,end,fail		sinteractive -N1 --time=120 --mail-user $USER@uab.edu --mail-type begin,end,fail
	</pre>		</pre>

	This command requests 1 node (24 cores) with entire allocation of RAM on the node for 120 minutes (2 hours). The command will wait until the resource is reserved by the scheduler and send you an email when the resource is available. The email alert can be useful during periods of heavy cluster demand when interactive resources reservations may have significant wait times.		This command requests 1 node (24 cores) with entire allocation of RAM on the node for 120 minutes (2 hours). The command will wait until the resource is reserved by the scheduler and send you an email when the resource is available. The email alert can be useful during periods of heavy cluster demand when interactive resources reservations may have significant wait times.

Tanthony@uab.edu: First draft

2016-03-01T18:13:51Z

First draft

← Older revision		Revision as of 18:13, 1 March 2016
Line 1:		Line 1:
	==Using VNC session ==		==Using VNC session ==
	Please refer to our [[Setting_Up_VNC_Session\|VNC setup guide]] to start a VNC session with Cheaha head node. After getting your VNC desktop, you can get a compute node resource using the '''sinteractive''' command. A '''sinteractive''' session launched through VNC won't get terminated even if your SSH or VNC window is closed. Of course, it will get terminated after specified run-time is reached.		Please refer to our [[Setting_Up_VNC_Session\|VNC setup guide]] to start a VNC session with Cheaha head node. After getting your VNC desktop, you can get a compute node resource using the '''sinteractive''' command. A '''sinteractive''' session launched through VNC won't get terminated even if your SSH or VNC window is closed. Of course, it will get terminated after specified run-time is reached.


			= Interactive Resources =

			After you login to Cheaha the command-line interface that you see is running on the login node. Most of your light interactive prep-work to submit a compute job to the scheduler can be carried out on this head node. If you have a heavier workload to prepare for a batch job (eg. compiling code or other manipulations of data) or your compute application requires interactive control, you should request a dedicated interactive node for this work.

			Interactive resources are requested by submitting an "interactive" job to the scheduler. Interactive jobs will provide you a command line on a compute resource that you can use just like you would the command line on the head node. The difference is that the scheduler has dedicated the requested resources to your job and you can run your interactive commands without having to worry about impacting other users on the head node.

			Interactive jobs are requested with the sinteractive command (please use your correct email address in place of the ''$USER@uab.edu'' string if you do not have an @uab.edu email address):
			<pre>
			sinteractive -N1 --time=120 --mail-user $user@uab.edu --mail-type begin,end,fail
			</pre>

			This command requests 1 node (24 cores) with entire allocation of RAM on the node for 120 minutes (2 hours). The command will wait until the resource is reserved by the scheduler and send you an email when the resource is available. The email alert can be useful during periods of heavy cluster demand when interactive resources reservations may have significant wait times.

Tanthony@uab.edu at 17:54, 1 March 2016

2016-03-01T17:54:08Z

← Older revision		Revision as of 17:54, 1 March 2016
Line 1:		Line 1:
	= Using VNC session ==		==Using VNC session ==
	Please refer to our [[Setting_Up_VNC_Session\|VNC setup guide]] to start a VNC session with Cheaha head node. After getting your VNC desktop, you can get a compute node resource using the '''sinteractive''' command. A '''sinteractive''' session launched through VNC won't get terminated even if your SSH or VNC window is closed. Of course, it will get terminated after specified run-time is reached.		Please refer to our [[Setting_Up_VNC_Session\|VNC setup guide]] to start a VNC session with Cheaha head node. After getting your VNC desktop, you can get a compute node resource using the '''sinteractive''' command. A '''sinteractive''' session launched through VNC won't get terminated even if your SSH or VNC window is closed. Of course, it will get terminated after specified run-time is reached.

Tanthony@uab.edu: page started

2016-03-01T17:53:53Z

page started

New page

= Using VNC session ==
Please refer to our [[Setting_Up_VNC_Session|VNC setup guide]] to start a VNC session with Cheaha head node. After getting your VNC desktop, you can get a compute node resource using the '''sinteractive''' command. A '''sinteractive''' session launched through VNC won't get terminated even if your SSH or VNC window is closed. Of course, it will get terminated after specified run-time is reached.