ELSA3 Upgrade FAQ - Revision history

Admin: /* Is there an entire new cluster running for this test? */

2026-04-09T19:10:38Z

Is there an entire new cluster running for this test?

← Older revision		Revision as of 19:10, 9 April 2026
Line 74:		Line 74:
	* 1 GPU node with 4 x RTX 2080 GPUs		* 1 GPU node with 4 x RTX 2080 GPUs
	* 1 GPU node with 4 x RTX A5000 GPUs		* 1 GPU node with 4 x RTX A5000 GPUs
	* 1 GPU node with 4 x L40S GPUs		* 1 GPU node with 4 x L40S GPUs (may not always be available depending on L40S needs on the current cluster)
	* 1 Visualization node with an L40 GPU (new!) for graphics rendering		* 1 Visualization node with an L40 GPU (new!) for graphics rendering
	* 1 login node		* 1 login node

Admin: /* Are my files also available on this new cluster? */

2026-04-09T19:09:41Z

Are my files also available on this new cluster?

← Older revision		Revision as of 19:09, 9 April 2026
Line 40:		Line 40:

	===== Are my files also available on this new cluster? =====		===== Are my files also available on this new cluster? =====
	Yes. Your files in your home directory, /projects, /courses and ~~global /scratch~~ are available and are currently shared between the two clusters.		Yes. Your files in your home directory, /projects, and /courses and are available and are currently shared between the two clusters. Because of how the global /scratch system works, it won't be available until after the upgrade.

	===== Is there a new login for the ELSA3 test cluster? =====		===== Is there a new login for the ELSA3 test cluster? =====

Admin: /* Is there an entire new cluster running for this test? */

2026-04-09T19:08:07Z

Is there an entire new cluster running for this test?

← Older revision		Revision as of 19:08, 9 April 2026
Line 66:		Line 66:
	* ELSA VDI Desktop under Interactive Applications in Open OnDemand		* ELSA VDI Desktop under Interactive Applications in Open OnDemand
	* ARM nodes (these will be reimaged with Rocky Linux 9 over the summer)		* ARM nodes (these will be reimaged with Rocky Linux 9 over the summer)
			* Access to /scratch

	These will be available in a future test session or with the launch of the ELSA3 cluster in production		These will be available in a future test session or with the launch of the ELSA3 cluster in production

Admin: /* Is there an entire new cluster running for this test? */

2026-04-09T19:07:50Z

Is there an entire new cluster running for this test?

← Older revision		Revision as of 19:07, 9 April 2026
Line 63:		Line 63:
	===== Is there an entire new cluster running for this test? =====		===== Is there an entire new cluster running for this test? =====
	Yes, sort of. The test cluster should be full-featured except for those items listed below. The applications below are disabled in this test because it could cause issues with their equivalent applications in the current cluster. The disabled apps are:		Yes, sort of. The test cluster should be full-featured except for those items listed below. The applications below are disabled in this test because it could cause issues with their equivalent applications in the current cluster. The disabled apps are:
	WebMO website		* WebMO website
	ELSA VDI Desktop under Interactive Applications in Open OnDemand		* ELSA VDI Desktop under Interactive Applications in Open OnDemand
	ARM nodes (these will be reimaged with Rocky Linux 9 over the summer)		* ARM nodes (these will be reimaged with Rocky Linux 9 over the summer)

	These will be available in a future test session or with the launch of the ELSA3 cluster in production		These will be available in a future test session or with the launch of the ELSA3 cluster in production

Admin: /* When will ELSA3 launch into production? */

2026-04-09T19:07:04Z

When will ELSA3 launch into production?

← Older revision		Revision as of 19:07, 9 April 2026
Line 78:		Line 78:

	===== When will ELSA3 launch into production? =====		===== When will ELSA3 launch into production? =====
	~~I hope to switch over to the new ELSA3 version the week of~~ May ~~25th~~ (~~Memorial Day week~~). ~~Exact dates/times will be announced in~~ the ~~future. There is currently a planned~~ campus power outage on May 25th so I ~~am thinking of starting up~~ the ~~new cluster after~~ the ~~power returns. The switch over may take~~ up ~~to 2 days depending on how smooth~~ the ~~process goes (I'm hoping for just one day)~~.		ELSA will be upgraded on May 21 & 22nd (Commencement days). Because of the campus power outage on Sunday, May 24th and Memorial Day on Monday, May 25th, ELSA3 will be down until Tuesday, May 26th. I hope the have the system up and operational in the afternoon.

	===== What will happen to the current cluster? =====		===== What will happen to the current cluster? =====
	All the nodes will be moved over to the new ELSA3 cluster when it goes into production. The old cluster software will remain for a while, but will no longer be accessible to end-users. If something needs to be moved over later, I will still be able to access the old cluster configurations and software. Remember, all files in your /home, /projects, /courses and /scratch will be available to you on the new cluster.		All the nodes will be moved over to the new ELSA3 cluster when it goes into production. The old cluster software will remain for a while, but will no longer be accessible to end-users. If something needs to be moved over later, I will still be able to access the old cluster configurations and software. Remember, all files in your /home, /projects, /courses and /scratch will be available to you on the new cluster.

Admin: /* How long is the testing period of the first "cluster crunch"? */

2026-04-09T19:04:00Z

How long is the testing period of the first "cluster crunch"?

← Older revision		Revision as of 19:04, 9 April 2026
Line 53:		Line 53:
	When we move to production, these will be changed to the existing elsa.hpc.tcnj.edu and ondemand.hpc.tcnj.edu.		When we move to production, these will be changed to the existing elsa.hpc.tcnj.edu and ondemand.hpc.tcnj.edu.

	===== How long is the testing period of the ~~first~~ "cluster crunch"? =====		===== How long is the testing period of the second "cluster crunch"? =====
	You can login to the new cluster now and continue to use it through ~~Friday~~, ~~March 27th~~. At that point, I'll take the new cluster down to make any necessary changes, updates or tweaks~~. Another test period will be available in April~~.		You can login to the new cluster now and continue to use it through Sunday, May 3rd. At that point, I'll take the new cluster down to make any necessary changes, updates or tweaks before the final cut-over on May 21st & 22nd.

	===== What have you tested? =====		===== What have you tested? =====

Admin: /* How do I access the test cluster? */

2026-03-05T19:52:26Z

How do I access the test cluster?

← Older revision		Revision as of 19:52, 5 March 2026
Line 48:		Line 48:
	For the test, you can use these names to access the ELSA3 cluster test:		For the test, you can use these names to access the ELSA3 cluster test:
	Via SSH: Use elsa-test3.hpc.tcnj.edu, e.g. ssh ssivy@elsa-test3.hpc.tcnj.edu		Via SSH: Use elsa-test3.hpc.tcnj.edu, e.g. ssh ssivy@elsa-test3.hpc.tcnj.edu

	Via Web: https://ondemand-test3.hpc.tcnj.edu/		Via Web: https://ondemand-test3.hpc.tcnj.edu/

	When we move to production, these will be changed to the existing elsa.hpc.tcnj.edu and ondemand.hpc.tcnj.edu.		When we move to production, these will be changed to the existing elsa.hpc.tcnj.edu and ondemand.hpc.tcnj.edu.

Admin: /* How do I access the test cluster? */

2026-03-05T19:52:01Z

How do I access the test cluster?

← Older revision		Revision as of 19:52, 5 March 2026
Line 47:		Line 47:
	===== How do I access the test cluster? =====		===== How do I access the test cluster? =====
	For the test, you can use these names to access the ELSA3 cluster test:		For the test, you can use these names to access the ELSA3 cluster test:
	Via SSH: Use elsa-test3.hpc.tcnj.edu, e.g. ssh ssivy@elsa-test3.tcnj.edu		Via SSH: Use elsa-test3.hpc.tcnj.edu, e.g. ssh ssivy@elsa-test3.hpc.tcnj.edu
	Via Web: https://ondemand-test3.hpc.tcnj.edu/		Via Web: https://ondemand-test3.hpc.tcnj.edu/
	When we move to production, these will be changed to the existing elsa.hpc.tcnj.edu and ondemand.hpc.tcnj.edu.		When we move to production, these will be changed to the existing elsa.hpc.tcnj.edu and ondemand.hpc.tcnj.edu.

Admin: /* ELSA3 Upgrade/Testing Frequently Asked Questions */

2026-03-05T16:12:38Z

ELSA3 Upgrade/Testing Frequently Asked Questions

← Older revision		Revision as of 16:12, 5 March 2026
Line 29:		Line 29:
	===== Why do I need to test anything? =====		===== Why do I need to test anything? =====
	Like moving from one version of Windows to another or one version of MacOS to another, there are some changes that may cause issues with the existing software applications. While I have done some basic testing to make sure there aren't obvious issues with the applications, I am inviting you to also try out some of your applications and double-check my testing.		Like moving from one version of Windows to another or one version of MacOS to another, there are some changes that may cause issues with the existing software applications. While I have done some basic testing to make sure there aren't obvious issues with the applications, I am inviting you to also try out some of your applications and double-check my testing.

			===== Any gotchas I should worry about when testing? =====
			Mostly no. I've disabled the ELSA VDI Desktop because switching back and forth between the new cluster and the old cluster can cause issues. My only other suggestion is to be careful using Open OnDemand on both clusters at the same time. Since your /home directory is available, both will write info to it. Don't accidentally delete or cancel a job running on the wrong Open OnDemand. It won't work anyway and will confuse the other cluster's Open OnDemand. I would suggest using only one at a time and running them in a private/incognito browser window.

	===== I don't have time to do the testing. Can I have my students access the ELSA3 test cluster to do the testing instead? =====		===== I don't have time to do the testing. Can I have my students access the ELSA3 test cluster to do the testing instead? =====
Line 77:		Line 80:
	===== What will happen to the current cluster? =====		===== What will happen to the current cluster? =====
	All the nodes will be moved over to the new ELSA3 cluster when it goes into production. The old cluster software will remain for a while, but will no longer be accessible to end-users. If something needs to be moved over later, I will still be able to access the old cluster configurations and software. Remember, all files in your /home, /projects, /courses and /scratch will be available to you on the new cluster.		All the nodes will be moved over to the new ELSA3 cluster when it goes into production. The old cluster software will remain for a while, but will no longer be accessible to end-users. If something needs to be moved over later, I will still be able to access the old cluster configurations and software. Remember, all files in your /home, /projects, /courses and /scratch will be available to you on the new cluster.

	~~===== Any gotchas I should worry about when testing? =====~~
	Mostly no. I've disabled the ELSA VDI Desktop because switching back and forth between the new cluster and the old cluster can cause issues. My only other suggestion is to be careful using Open OnDemand on both clusters at the same time. Since your /home directory is available, both will write info to it. Don't accidentally delete or cancel a job running on the wrong Open OnDemand. It won't work anyway and will confuse the other cluster's Open OnDemand. I would suggest using only one at a time and running them in a private/incognito browser window.

Admin: /* Job or module command failed with "The following module(s) are unknown" error */

2026-03-05T14:05:39Z

Job or module command failed with "The following module(s) are unknown" error

← Older revision		Revision as of 14:05, 5 March 2026
Line 12:		Line 12:
	and replace it with one of these		and replace it with one of these

	<code>module add matlab/R2025a</code> ''or'' <code>module add matlab</code>		<code>module add matlab/R2025a</code> ''or'' <code>module add matlab</code>


	To see what modules are available, use the <code>module avail</code> command.		To see what modules are available, use the <code>module avail</code> command.

	Example:		Example: <code>module avail</code> ''or'' <code>module avail matlab</code>

	<code>module avail</code>

	<code>module avail matlab</code>

	== ELSA3 Upgrade/Testing Frequently Asked Questions ==		== ELSA3 Upgrade/Testing Frequently Asked Questions ==