OS Change - Revision history

Mozes: /* OS Change */

2024-06-24T13:33:32Z

OS Change

← Older revision		Revision as of 08:33, 24 June 2024
Line 1:		Line 1:
	== OS Change ==		== OS Change ==
	On April 1 2024, we be switched our Operating System from CentOS 7 to Rocky Linux 9.		On April 1 2024, we switched our Operating System from CentOS 7 to Rocky Linux 9.

	If you had compiled your own software under CentOS (with or without our modules) you will likely need to recompile it to use it with the new operating system.		If you had compiled your own software under CentOS (with or without our modules) you will likely need to recompile it to use it with the new operating system.

Mozes: /* OS Change */

2024-06-23T20:38:24Z

OS Change

← Older revision		Revision as of 15:38, 23 June 2024
Line 1:		Line 1:
	== OS Change ==		== OS Change ==
	~~Soon~~ we~~'ll~~ be ~~switching~~ our Operating System from CentOS 7 to Rocky Linux 9. If you are utilizing software that we provide via the <tt>module</tt> command, it would be a good idea to access the testbed and verify that we have the tools which you need. If they are not there, you should let us know what you need.		On April 1 2024, we be switched our Operating System from CentOS 7 to Rocky Linux 9.

	~~One big thing that I'm not sure we've made abundantly clear enough, is that if~~ you ~~have~~ compiled your own software (with or without our modules) you will likely need to recompile it to use it with the new operating system.		If you had compiled your own software under CentOS (with or without our modules) you will likely need to recompile it to use it with the new operating system.

	~~=== Accessing the testbed ===~~
	~~We have provided two new head nodes <tt>helios</tt> and <tt>clymene</tt>.~~

	~~Once you have logged into beocat, you can access them with ssh. e.g. <tt>ssh helios</tt>~~

	They will be setup much the same way as our previous head nodes were, with access to the module command. The modules we have available under Rocky Linux 9 are available as a searchable list [https://modules.beocat.ksu.edu/rocky9/ here]

	To submit jobs to the new operating system, we have provided a new constraint so that you are able to request the OS variant. CentOS 7 hosts have the feature <tt>os_el7</tt>, while the Rocky Linux 9 hosts provide the feature <tt>os_el9</tt>.

	~~You would use the following in a job script to tell the scheduler that you would like the new OS:~~

	~~<syntaxhighlight lang=bash>~~
	~~#SBATCH -C os_el9~~
	~~</syntaxhighlight>~~

	~~We have an OpenOnDemand version of the testbed available at https://ondemand-dev.beocat.ksu.edu~~

	=== Using old software ===		=== Using old software ===
Line 36:		Line 19:
	# that we will not or cannot provide under our new operating system.		# that we will not or cannot provide under our new operating system.

	~~singularity~~ exec /opt/beocat/containers/beocat_centos-7.9.sif /bin/bash -l <<EOF		apptainer exec /opt/beocat/containers/beocat_centos-7.9.sif /bin/bash -l <<EOF
	${@}		${@}
	EOF		EOF
	</syntaxhighlight>		</syntaxhighlight>
	If you would prefer, you could put the <tt>~~singularity~~ exec</tt> lines in your script, with the commands you would like to run between the <tt><<EOF</tt> and <tt>EOF</tt> sections.		If you would prefer, you could put the <tt>apptainer exec</tt> lines in your script, with the commands you would like to run between the <tt><<EOF</tt> and <tt>EOF</tt> sections.

	There will be no good way to utilize these tools with multi-node jobs, so it would be a good idea to migrate away from the CentOS 7 tools as soon as possible.		There will be no good way to utilize these tools with multi-node jobs, so it would be a good idea to migrate away from the CentOS 7 tools as soon as possible.

Mozes at 21:12, 4 March 2024

2024-03-04T21:12:52Z

← Older revision		Revision as of 16:12, 4 March 2024
Line 9:		Line 9:
	Once you have logged into beocat, you can access them with ssh. e.g. <tt>ssh helios</tt>		Once you have logged into beocat, you can access them with ssh. e.g. <tt>ssh helios</tt>

	They will be setup much the same way as our previous head nodes were, with access to the module command. The modules we have available under Rocky Linux 9 are available as a searchable list [~~here~~ https://modules.beocat.ksu.edu/rocky9/]		They will be setup much the same way as our previous head nodes were, with access to the module command. The modules we have available under Rocky Linux 9 are available as a searchable list [https://modules.beocat.ksu.edu/rocky9/ here]

	To submit jobs to the new operating system, we have provided a new constraint so that you are able to request the OS variant. CentOS 7 hosts have the feature <tt>os_el7</tt>, while the Rocky Linux 9 hosts provide the feature <tt>os_el9</tt>.		To submit jobs to the new operating system, we have provided a new constraint so that you are able to request the OS variant. CentOS 7 hosts have the feature <tt>os_el7</tt>, while the Rocky Linux 9 hosts provide the feature <tt>os_el9</tt>.

Mozes at 00:38, 19 February 2024

2024-02-19T00:38:50Z

← Older revision		Revision as of 19:38, 18 February 2024
Line 1:		Line 1:
	== OS Change ==		== OS Change ==
	Soon we'll be switching our Operating System from CentOS 7 to Rocky Linux 9. If you are utilizing software that we provide via the <tt>module</tt> command, it would be a good idea to access the testbed and verify that we have the tools which you need. If they are not there, you should let us know what you need.		Soon we'll be switching our Operating System from CentOS 7 to Rocky Linux 9. If you are utilizing software that we provide via the <tt>module</tt> command, it would be a good idea to access the testbed and verify that we have the tools which you need. If they are not there, you should let us know what you need.

			One big thing that I'm not sure we've made abundantly clear enough, is that if you have compiled your own software (with or without our modules) you will likely need to recompile it to use it with the new operating system.

	=== Accessing the testbed ===		=== Accessing the testbed ===

Mozes: /* OS Change */

2024-02-19T00:36:31Z

OS Change

← Older revision		Revision as of 19:36, 18 February 2024
Line 16:		Line 16:
	#SBATCH -C os_el9		#SBATCH -C os_el9
	</syntaxhighlight>		</syntaxhighlight>

			We have an OpenOnDemand version of the testbed available at https://ondemand-dev.beocat.ksu.edu

	=== Using old software ===		=== Using old software ===

Mozes: /* OS Change */

2024-02-11T15:04:28Z

OS Change

← Older revision		Revision as of 10:04, 11 February 2024
Line 1:		Line 1:
	== OS Change ==		== OS Change ==
	Soon we'll be switching our Operating System from CentOS 7 to Rocky Linux 9.		Soon we'll be switching our Operating System from CentOS 7 to Rocky Linux 9. If you are utilizing software that we provide via the <tt>module</tt> command, it would be a good idea to access the testbed and verify that we have the tools which you need. If they are not there, you should let us know what you need.

	=== Accessing the testbed ===		=== Accessing the testbed ===

Mozes: /* Using old software */

2024-02-11T15:01:47Z

Using old software

← Older revision		Revision as of 10:01, 11 February 2024
Line 37:		Line 37:
	</syntaxhighlight>		</syntaxhighlight>
	If you would prefer, you could put the <tt>singularity exec</tt> lines in your script, with the commands you would like to run between the <tt><<EOF</tt> and <tt>EOF</tt> sections.		If you would prefer, you could put the <tt>singularity exec</tt> lines in your script, with the commands you would like to run between the <tt><<EOF</tt> and <tt>EOF</tt> sections.

			There will be no good way to utilize these tools with multi-node jobs, so it would be a good idea to migrate away from the CentOS 7 tools as soon as possible.

Mozes: Created page with "== OS Change == Soon we'll be switching our Operating System from CentOS 7 to Rocky Linux 9. === Accessing the testbed === We have provided two new head nodes `helios` and `clymene`. Once you have logged into beocat, you can access them with ssh. e.g. `ssh helios` They will be setup much the same way as our previous head nodes were, with access to the module command. The modules we have available under Rocky Linux 9 are available as a searchable l..."

2024-02-11T15:00:03Z

Created page with "== OS Change == Soon we'll be switching our Operating System from CentOS 7 to Rocky Linux 9. === Accessing the testbed === We have provided two new head nodes <tt>helios</tt> and <tt>clymene</tt>. Once you have logged into beocat, you can access them with ssh. e.g. <tt>ssh helios</tt> They will be setup much the same way as our previous head nodes were, with access to the module command. The modules we have available under Rocky Linux 9 are available as a searchable l..."

New page

== OS Change ==
Soon we'll be switching our Operating System from CentOS 7 to Rocky Linux 9.

=== Accessing the testbed ===
We have provided two new head nodes <tt>helios</tt> and <tt>clymene</tt>.

Once you have logged into beocat, you can access them with ssh. e.g. <tt>ssh helios</tt>

They will be setup much the same way as our previous head nodes were, with access to the module command. The modules we have available under Rocky Linux 9 are available as a searchable list [here https://modules.beocat.ksu.edu/rocky9/]

To submit jobs to the new operating system, we have provided a new constraint so that you are able to request the OS variant. CentOS 7 hosts have the feature <tt>os_el7</tt>, while the Rocky Linux 9 hosts provide the feature <tt>os_el9</tt>.

You would use the following in a job script to tell the scheduler that you would like the new OS:

<syntaxhighlight lang=bash>
#SBATCH -C os_el9
</syntaxhighlight>

=== Using old software ===
Below is a script that will execute a container with all of the public software we provide under CentOS 7 from the head nodes. There may be versions of GPU-related packages missing.
<syntaxhighlight lang=bash>
#!/bin/bash
# This script is a wrapper for our CentOS 7 based container.
# You would use it something like this:
# sbatch -C os_el9 /opt/beocat/containers/beocat_centos-7.9.wrapper.sh ./R-hello_world.sh

# Note that you would need to provide an appropriate path for the script to to execute
# under the contained environnment (either a full path or a relative path), and the script
# would need to be executable.

# This is meant to be a stopgap measure for those that may be reliant on older software
# that we will not or cannot provide under our new operating system.

singularity exec /opt/beocat/containers/beocat_centos-7.9.sif /bin/bash -l <<EOF
${@}
EOF
</syntaxhighlight>
If you would prefer, you could put the <tt>singularity exec</tt> lines in your script, with the commands you would like to run between the <tt><<EOF</tt> and <tt>EOF</tt> sections.