UMIACS - User contributions [en]

CyberRange

2026-09-02T14:59:10Z

Dyarnell:

To limit access for a set of resources in UMIACS we may protect the networks with a cyber range.

This is achieved using a bridging host that users can use to access the devices within the cyber range. The devices within the cyber range can have multiple networks including a network that provides access to out of band management devices. Devices within the cyber range do not have network access outside the cyber range. All data must be staged through the bridge hosts that provide access to the cyber ranges.

No computational intensive activities are to be executed on the bridge hosts and processes that will be killed to maintain the availability and access of the cyber range.

=Access=
To access cyber range bridge hosts in UMIACS you will need to be connected to the UMIACS network or UMD Global Protect.

Then you would need to ssh to the bridge host (eg. <code>ssh username@bridge_host.umiacs.umd.edu</code>) and provide your credentials and MFA to connect. Once you are logged in you can now jump to any internal host in the range over SSH. If you need to access a graphical interface see the Graphical Desktop Access section below.

If you need to stage data you can use the SSH jump host support. Here are some examples using <code>scp</code> or <code>rsync</code>.

* <code>scp -J user@bridge_host /path/to/local/file user@target_server:/path/to/destination/</code>
* <code>rsync -avz -e "ssh -J user@bridge_host" /path/to/local/folder/ user@target_server:/path/to/destination/</code>

=Temporary Storage=
If data needs to be tempoary stored on the bridge host it can be stored in <code>/scratch0</code>. This data is not backed up and should not be used as a primary copy of any data that is critical. If the space is fully allocated the Technical Staff reserve the right to clear out the space as necessary to support the activities of the cyber range.

=Network Services=
Network services like DNS, DHCP are provided by the bridging host to the internal cyber range networks.

=Remote Desktop Access=
Bridging host(s) provide remote desktop access locally that can be used with a simple SSH port forwarding tunnel. In a local terminal window you can run the following command providing your credentials and MFA.

<code>ssh -L 33389:localhost:3389 username@bridge_host.umiacs.umd.edu</code>

You can then use your local RDP client to connect to <code>bridge_host.umiacs.umd.edu:33389</code> and you will be logged into a console session on the bridging host. You can disconnect and re-connect to the console.

CyberRange

2026-09-02T14:53:32Z

Dyarnell:

To limit access for a set of resources in UMIACS we may protect the networks with a cyber range.

This is achieved using a bridging host that users can use to access the devices within the cyber range. The devices within the cyber range can have multiple networks including a network that provides access to out of band management devices. Devices within the cyber range do not have network access outside the cyber range. All data must be staged through the bridge hosts that provide access to the cyber ranges.

No computational intensive activities are to be executed on the bridge hosts and are subject to quit to maintain the availability and access of the cyber range.

=Access=
To access cyber range bridge hosts in UMIACS you will need to be connected to the UMIACS network or UMD Global Protect.

Then you would need to ssh to the bridge host (eg. <code>ssh username@bridge_host.umiacs.umd.edu</code>) and provide your credentials and MFA to connect. Once you are logged in you can now jump to any internal host in the range over SSH. If you need to access a graphical interface see the Graphical Desktop Access section below.

If you need to stage data you can use the SSH jump host support. Here are some examples using <code>scp</code> or <code>rsync</code>.

* <code>scp -J user@bridge_host /path/to/local/file user@target_server:/path/to/destination/</code>
* <code>rsync -avz -e "ssh -J user@bridge_host" /path/to/local/folder/ user@target_server:/path/to/destination/</code>

=Temporary Storage=
If data needs to be tempoary stored on the bridge host it can be stored in <code>/scratch0</code>. This data is not backed up and should not be used as a primary copy of any data that is critical. If the space is fully allocated the Technical Staff reserve the right to clear out the space as necessary to support the activities of the cyber range.

=Network Services=
Network services like DNS, DHCP are provided by the bridging host to the internal cyber range networks.

=Remote Desktop Access=
Bridging host(s) provide remote desktop access locally that can be used with a simple SSH port forwarding tunnel. In a local terminal window you can run the following command providing your credentials and MFA.

<code>ssh -L 33389:localhost:3389 username@bridge_host.umiacs.umd.edu</code>

You can then use your local RDP client to connect to <code>bridge_host.umiacs.umd.edu:33389</code> and you will be logged into a console session on the bridging host. You can disconnect and re-connect to the console.

CyberRange

2026-09-02T14:52:11Z

Dyarnell: /* Remote Desktop Access */

To limit access for a set of resources in UMIACS we may protect the networks with a cyber range.

This is achieved using a bridging host that users can use to access the devices within the cyber range. The devices within the cyber range can have multiple networks including a network that provides access to out of band management devices. Devices within the cyber range do not have network access outside the cyber range. All data must be staged through the bridge hosts that provide access to the cyber ranges.

=Access=
To access cyber range bridge hosts in UMIACS you will need to be connected to the UMIACS network or UMD Global Protect.

Then you would need to ssh to the bridge host (eg. <code>ssh username@bridge_host.umiacs.umd.edu</code>) and provide your credentials and MFA to connect. Once you are logged in you can now jump to any internal host in the range over SSH. If you need to access a graphical interface see the Graphical Desktop Access section below.

If you need to stage data you can use the SSH jump host support. Here are some examples using <code>scp</code> or <code>rsync</code>.

* <code>scp -J user@bridge_host /path/to/local/file user@target_server:/path/to/destination/</code>
* <code>rsync -avz -e "ssh -J user@bridge_host" /path/to/local/folder/ user@target_server:/path/to/destination/</code>

=Temporary Storage=
If data needs to be tempoary stored on the bridge host it can be stored in <code>/scratch0</code>. This data is not backed up and should not be used as a primary copy of any data that is critical. If the space is fully allocated the Technical Staff reserve the right to clear out the space as necessary to support the activities of the cyber range.

=Network Services=
Network services like DNS, DHCP are provided by the bridging host to the internal cyber range networks.

=Remote Desktop Access=
Bridging host(s) provide remote desktop access locally that can be used with a simple SSH port forwarding tunnel. In a local terminal window you can run the following command providing your credentials and MFA.

<code>ssh -L 33389:localhost:3389 username@bridge_host.umiacs.umd.edu</code>

You can then use your local RDP client to connect to <code>bridge_host.umiacs.umd.edu:33389</code> and you will be logged into a console session on the bridging host. You can disconnect and re-connect to the console.

CyberRange

2026-09-02T14:51:02Z

Dyarnell:

To limit access for a set of resources in UMIACS we may protect the networks with a cyber range.

This is achieved using a bridging host that users can use to access the devices within the cyber range. The devices within the cyber range can have multiple networks including a network that provides access to out of band management devices. Devices within the cyber range do not have network access outside the cyber range. All data must be staged through the bridge hosts that provide access to the cyber ranges.

=Access=
To access cyber range bridge hosts in UMIACS you will need to be connected to the UMIACS network or UMD Global Protect.

Then you would need to ssh to the bridge host (eg. <code>ssh username@bridge_host.umiacs.umd.edu</code>) and provide your credentials and MFA to connect. Once you are logged in you can now jump to any internal host in the range over SSH. If you need to access a graphical interface see the Graphical Desktop Access section below.

If you need to stage data you can use the SSH jump host support. Here are some examples using <code>scp</code> or <code>rsync</code>.

* <code>scp -J user@bridge_host /path/to/local/file user@target_server:/path/to/destination/</code>
* <code>rsync -avz -e "ssh -J user@bridge_host" /path/to/local/folder/ user@target_server:/path/to/destination/</code>

=Temporary Storage=
If data needs to be tempoary stored on the bridge host it can be stored in <code>/scratch0</code>. This data is not backed up and should not be used as a primary copy of any data that is critical. If the space is fully allocated the Technical Staff reserve the right to clear out the space as necessary to support the activities of the cyber range.

=Network Services=
Network services like DNS, DHCP are provided by the bridging host to the internal cyber range networks.

=Remote Desktop Access=
Bridging host(s) provide remote desktop access locally that can be used with a simple SSH port forwarding tunnel. In a local terminal window you can run the following command providing your credentials and MFA.

<code>ssh -L 33389:localhost:3389 username@bridge_host.umiacs.umd.edu</code>

You can then use your local RDP client to connect to <code>bridge_host.umiacs.umd.edu:33389</code> and you will be logged into a console session on the bridging host.

CyberRange

2026-09-02T14:49:56Z

Dyarnell:

To limit access for a set of resources in UMIACS we may protect the networks with a cyber range.

This is achieved using a bridging host that users can use to access the devices within the cyber range. The devices within the cyber range can have multiple networks including a network that provides access to out of band management devices. Devices within the cyber range do not have network access outside the cyber range.

=Access=
To access cyber range bridge hosts in UMIACS you will need to be connected to the UMIACS network or UMD Global Protect.

Then you would need to ssh to the bridge host (eg. <code>ssh username@bridge_host.umiacs.umd.edu</code>) and provide your credentials and MFA to connect. Once you are logged in you can now jump to any internal host in the range over SSH. If you need to access a graphical interface see the Graphical Desktop Access section below.

If you need to stage data you can use the SSH jump host support. Here are some examples using <code>scp</code> or <code>rsync</code>.

* <code>scp -J user@bridge_host /path/to/local/file user@target_server:/path/to/destination/</code>
* <code>rsync -avz -e "ssh -J user@bridge_host" /path/to/local/folder/ user@target_server:/path/to/destination/</code>

=Temporary Storage=
If data needs to be tempoary stored on the bridge host it can be stored in <code>/scratch0</code>. This data is not backed up and should not be used as a primary copy of any data that is critical. If the space is fully allocated the Technical Staff reserve the right to clear out the space as necessary to support the activities of the cyber range.

=Network Services=
Network services like DNS, DHCP are provided by the bridging host to the internal cyber range networks.

=Remote Desktop Access=
Bridging host(s) provide remote desktop access locally that can be used with a simple SSH port forwarding tunnel. In a local terminal window you can run the following command providing your credentials and MFA.

<code>ssh -L 33389:localhost:3389 username@bridge_host.umiacs.umd.edu</code>

You can then use your local RDP client to connect to <code>bridge_host.umiacs.umd.edu:33389</code> and you will be logged into a console session on the bridging host.

CyberRange

2026-09-01T20:45:24Z

Dyarnell:

To limit access for a set of resources in UMIACS we may protect the networks with a cyber range.

This is achieved using a bridging host that users can use to access the devices within the cyber range. The devices within the cyber range can have multiple networks including a network that provides access to out of band management devices. Devices within the cyber range do not have network access outside the cyber range.

=Access=
To access cyber range bridge hosts in UMIACS you will need to be connected to the UMIACS network or UMD Global Protect.

Then you would need to ssh to the bridge host (eg. <code>ssh username@bridge_host.umiacs.umd.edu</code>) and provide your credentials and MFA to connect. Once you are logged in you can now jump to any internal host in the range over SSH. If you need to access a graphical interface see the Graphical Desktop Access section below.

If you need to stage data you can use the SSH jump host support. Here are some examples using <code>scp</code> or <code>rsync</code>.

* <code>scp -J user@bridge_host /path/to/local/file user@target_server:/path/to/destination/</code>
* <code>rsync -avz -e "ssh -J user@bridge_host" /path/to/local/folder/ user@target_server:/path/to/destination/</code>

=Network Services=
Network services like DNS, DHCP are provided by the bridging host to the internal cyber range networks.

=Remote Desktop Access=
Bridging host(s) provide remote desktop access locally that can be used with a simple SSH port forwarding tunnel. In a local terminal window you can run the following command providing your credentials and MFA.

<code>ssh -L 33389:localhost:3389 username@bridge_host.umiacs.umd.edu</code>

You can then use your local RDP client to connect to <code>bridge_host.umiacs.umd.edu:33389</code> and you will be logged into a console session on the bridging host.

CyberRange

2026-09-01T20:44:18Z

Dyarnell:

To limit access for a set of resources in UMIACS we may protect the networks with a cyber range.

This is achieved using a bridging host that users can use to access the devices within the cyber range. The devices within the cyber range can have multiple networks including a network that provides access to out of band management devices. Devices within the cyber range do not have network access outside the cyber range.

=Access=
To access cyber range bridge hosts in UMIACS you will need to be connected to the UMIACS network or UMD Global Protect.

Then you would need to ssh to the bridge host (eg. <code>ssh username@bridge_host.umiacs.umd.edu</code>) and provide your credentials and MFA to connect. Once you are logged in you can now jump to any internal host in the range over SSH. If you need to access a graphical interface see the Graphical Desktop Access section below.

If you need to stage data you can use the SSH jump host support.

<code>scp -J user@bridge_host /path/to/local/file user@target_server:/path/to/destination/</code>
<code>rsync -avz -e "ssh -J user@bridge_host" /path/to/local/folder/ user@target_server:/path/to/destination/</code>

=Network Services=
Network services like DNS, DHCP are provided by the bridging host to the internal cyber range networks.

=Remote Desktop Access=
Bridging host(s) provide remote desktop access locally that can be used with a simple SSH port forwarding tunnel. In a local terminal window you can run the following command providing your credentials and MFA.

<code>ssh -L 33389:localhost:3389 username@bridge_host.umiacs.umd.edu</code>

You can then use your local RDP client to connect to <code>bridge_host.umiacs.umd.edu:33389</code> and you will be logged into a console session on the bridging host.

CyberRange

2026-09-01T20:35:16Z

Dyarnell: /* Remote Desktop Access */

CyberRange

2026-09-01T20:33:48Z

Dyarnell:

CyberRange

2026-09-01T20:29:44Z

Dyarnell:

CyberRange

2026-09-01T20:28:53Z

Dyarnell: Created page with "To limit access for a set of resources in UMIACS we may protect the networks with a cyber range. This is achieved using a bridging host that users can use to access the devices within the cyber range. The devices within the cyber range can have multiple networks including a network that provides access to out of band management devices."

S3Clients

2026-08-19T19:24:14Z

Dyarnell: /* mc */

Many popular S3 desktop clients can be used to access the [[OBJ | UMIACS Object Store]]. These tools complement the [[UMobj]] command line utilities and the built-in web interface by providing integration with the native file explorer on your desktop machine.

'''Note''': Many of these clients have features that are not supported by our Object Store in UMIACS. One prominent example of this is permissions. We suggest you instead manage permissions from the [https://obj.umiacs.umd.edu/obj built-in web application] for the Object Store.

=Graphical Clients=

==Cyberduck==
https://cyberduck.io

This is a free Windows and Mac S3 browser (it is however nagware that asks for a donation). It supports our S3 Object Store using the "S3 (Amazon Simple Storage Service)" drop down menu choice in the add bookmark dialog.

[[Image:Cyberduck.png|400px |alt=Setting up Object Store access in Cyberduck]]

The following fields are required:
* '''Server''' - This is your object store (<code>obj.umiacs.umd.edu</code>)
* '''Access Key ID''' - This is your access key as provided to you in the object store
* '''Password''' - This is your secret key as provided to you in the object store

You will be prompted for your secret key when you connect and may choose to save the password.

==WinSCP==
* https://winscp.net/eng/index.php

This is a free Windows file transfer application. It supports our S3 Object Store using the "Amazon S3" drop down menu choice under File protocol when logging in.

[[Image:WinSCPS3.png|400px |alt=Setting up Object Store access in WinSCP]]

The following fields are required:
* '''Host name''' - This is your object store (<code>obj.umiacs.umd.edu</code>)
* '''Access key ID''' - This is your access key as provided to you in the object store
* '''Secret access key''' - This is your secret key as provided to you in the object store

==Transmit==
* https://panic.com/transmit/
This is a paid file transfer application for Mac. It supports our S3 Object Store using the "S3" menu choice after clicking the plus sign to add a favorite.

[[Image:Transmit.png|400px |alt=Setting up Object Store access in Transmit]]

The following fields are required:
* '''Server''' - This is your object store (<code>obj.umiacs.umd.edu</code>)
* '''Access Key ID''' - This is your access key as provided to you in the object store
* '''Secret''' - This is your secret key as provided to you in the object store

These settings can be saved as a favorite for easy access. Transmit also allows you to mount your Obj buckets as local disks, which will support easy drag-and-drop of files.

=Command Line Clients=
==s3cmd==
Command line client for accessing S3-like services.
* https://s3tools.org/s3cmd

You need to configure a file like <code>~/.s3cfg</code> that looks like the following with your ACCESS_KEY and SECRET_KEY substituted.

<pre>
[default]
access_key = <ACCESS_KEY>
host_base = obj.umiacs.umd.edu
host_bucket = %(bucket)s.obj.umiacs.umd.edu
secret_key = <SECRET_KEY>
use_https = True
</pre>

==mc==
The AIStor Client (formerly known as the MinIO Client) is a comprehensive single binary (Go) command line client for cloud based storage services.
* https://www.min.io/download/aistor-client

You can run this client on supported UMIACS systems through adding it via our software [[Modules|module]].
<pre>module add mc</pre>

You will need to setup a cloud provider for Obj by running the following command (substituting in your actual ACCESS_KEY and SECRET_KEY for your personal account or [[OBJ#LabGroups | LabGroup]] in the [https://obj.umiacs.umd.edu/obj/user/ Object Store]). The <code>obj</code> example name is configurable and used to differentiate between multiple different cloud based storage systems that you configure.

===Alias===
<pre>
mc alias set obj https://obj.umiacs.umd.edu <ACCESS_KEY> <SECRET_KEY>
</pre>

You can see what host(s) you have configured with the command <code>mc config host ls</code>.

<pre>
$ mc alias list
...
obj
URL : https://obj.umiacs.umd.edu
AccessKey : (redacted)
SecretKey : (redacted)
API : s3v4
Path : auto
...
</pre>

You can then use the normal <code>mc</code> commands note that the alias name you have used is required to differentiate between the local file system.

===Buckets===
You can create a bucket <code>mc mb obj/my_bucket_name</code>. Buckets in the Object Store share a single name space and you will get a friendly error <code>Error response code BucketAlreadyExists.</code> which you will need to choose a different bucket name.

===Listing===
Listing keys inside a bucket.

<pre>
$ mc ls obj/iso/RedHat-E10
[2026-07-29 10:56:46 EDT] 0B EC-53 /
[2026-07-29 10:56:46 EDT] 9.7GiB EC-53 rhel-10.2-aarch64-dvd.iso
[2026-07-29 11:00:18 EDT] 10GiB EC-53 rhel-10.2-x86_64-dvd.iso
</pre>

===Copy===
Copying data into a bucket from the local file (eg. <code>rhel-10.0-x86_64-dvd.iso</code> in this case).

<pre>
$ mc cp rhel-10.0-x86_64-dvd.iso obj/iso/RedHat-E10
...-10.0-x86_64-dvd.iso: █████████████████████████████████████████████████████████████████████████ 100.0% 7.9 GiB 90 MiB/s
</pre>

===Mirror===
Often users will just want to mirror a local set of files. Note that it will mirror recursively the files in the directory but you will need to be explict if you about the destination path in this case to ensure that you get the directory created in the destination.

<pre>
$ ls -l test/
total 16
-rw-rw-r--. 1 dyarnell dyarnell 8688 Aug 19 15:17 cpuinfo
-rw-rw-r--. 1 dyarnell dyarnell 23 Aug 19 15:17 uptime
$ mc mirror /tmp/test obj/staff-test/test
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 0.0% 0 B 0 B/s
$ mc ls obj/staff-test/test/
[2026-08-19 15:18:45 EDT] 8.5KiB STANDARD cpuinfo
[2026-08-19 15:18:45 EDT] 23B STANDARD uptime
</pre>

===Find===
There is also the ability to search for file globs of specific files using the <code>find</code> sub-command for <code>mc</code>.

<pre>
$ mc find dyarnell/dyarnell_support --name "*.log"
dyarnell/dyarnell_support/mds_20170918/ceph-mds.objmds01.log
dyarnell/dyarnell_support/satellite.log
dyarnell/dyarnell_support/umiacs-49168.log
</pre>

The full AIStor Client documentation can be found here: https://docs.min.io/aistor/reference/cli/.

==rclone==
Command line client for accessing S3-like services and much more.
* https://rclone.org/downloads

We maintain rclone documentation on a separate page found [[Rclone | here]].

S3Clients

2026-08-19T19:23:28Z

Dyarnell: /* mc */

Many popular S3 desktop clients can be used to access the [[OBJ | UMIACS Object Store]]. These tools complement the [[UMobj]] command line utilities and the built-in web interface by providing integration with the native file explorer on your desktop machine.

'''Note''': Many of these clients have features that are not supported by our Object Store in UMIACS. One prominent example of this is permissions. We suggest you instead manage permissions from the [https://obj.umiacs.umd.edu/obj built-in web application] for the Object Store.

=Graphical Clients=

==Cyberduck==
https://cyberduck.io

This is a free Windows and Mac S3 browser (it is however nagware that asks for a donation). It supports our S3 Object Store using the "S3 (Amazon Simple Storage Service)" drop down menu choice in the add bookmark dialog.

[[Image:Cyberduck.png|400px |alt=Setting up Object Store access in Cyberduck]]

The following fields are required:
* '''Server''' - This is your object store (<code>obj.umiacs.umd.edu</code>)
* '''Access Key ID''' - This is your access key as provided to you in the object store
* '''Password''' - This is your secret key as provided to you in the object store

You will be prompted for your secret key when you connect and may choose to save the password.

==WinSCP==
* https://winscp.net/eng/index.php

This is a free Windows file transfer application. It supports our S3 Object Store using the "Amazon S3" drop down menu choice under File protocol when logging in.

[[Image:WinSCPS3.png|400px |alt=Setting up Object Store access in WinSCP]]

The following fields are required:
* '''Host name''' - This is your object store (<code>obj.umiacs.umd.edu</code>)
* '''Access key ID''' - This is your access key as provided to you in the object store
* '''Secret access key''' - This is your secret key as provided to you in the object store

==Transmit==
* https://panic.com/transmit/
This is a paid file transfer application for Mac. It supports our S3 Object Store using the "S3" menu choice after clicking the plus sign to add a favorite.

[[Image:Transmit.png|400px |alt=Setting up Object Store access in Transmit]]

The following fields are required:
* '''Server''' - This is your object store (<code>obj.umiacs.umd.edu</code>)
* '''Access Key ID''' - This is your access key as provided to you in the object store
* '''Secret''' - This is your secret key as provided to you in the object store

These settings can be saved as a favorite for easy access. Transmit also allows you to mount your Obj buckets as local disks, which will support easy drag-and-drop of files.

=Command Line Clients=
==s3cmd==
Command line client for accessing S3-like services.
* https://s3tools.org/s3cmd

You need to configure a file like <code>~/.s3cfg</code> that looks like the following with your ACCESS_KEY and SECRET_KEY substituted.

<pre>
[default]
access_key = <ACCESS_KEY>
host_base = obj.umiacs.umd.edu
host_bucket = %(bucket)s.obj.umiacs.umd.edu
secret_key = <SECRET_KEY>
use_https = True
</pre>

==mc==
The AIStor Client (formerly known as the MinIO Client) is a comprehensive single binary (Go) command line client for cloud based storage services.
* https://min.io/download

You can run this client on supported UMIACS systems through adding it via our software [[Modules|module]].
<pre>module add mc</pre>

You will need to setup a cloud provider for Obj by running the following command (substituting in your actual ACCESS_KEY and SECRET_KEY for your personal account or [[OBJ#LabGroups | LabGroup]] in the [https://obj.umiacs.umd.edu/obj/user/ Object Store]). The <code>obj</code> example name is configurable and used to differentiate between multiple different cloud based storage systems that you configure.

===Alias===
<pre>
mc alias set obj https://obj.umiacs.umd.edu <ACCESS_KEY> <SECRET_KEY>
</pre>

You can see what host(s) you have configured with the command <code>mc config host ls</code>.

<pre>
$ mc alias list
...
obj
URL : https://obj.umiacs.umd.edu
AccessKey : (redacted)
SecretKey : (redacted)
API : s3v4
Path : auto
...
</pre>

You can then use the normal <code>mc</code> commands note that the alias name you have used is required to differentiate between the local file system.

===Buckets===
You can create a bucket <code>mc mb obj/my_bucket_name</code>. Buckets in the Object Store share a single name space and you will get a friendly error <code>Error response code BucketAlreadyExists.</code> which you will need to choose a different bucket name.

===Listing===
Listing keys inside a bucket.

<pre>
$ mc ls obj/iso/RedHat-E10
[2026-07-29 10:56:46 EDT] 0B EC-53 /
[2026-07-29 10:56:46 EDT] 9.7GiB EC-53 rhel-10.2-aarch64-dvd.iso
[2026-07-29 11:00:18 EDT] 10GiB EC-53 rhel-10.2-x86_64-dvd.iso
</pre>

===Copy===
Copying data into a bucket from the local file (eg. <code>rhel-10.0-x86_64-dvd.iso</code> in this case).

<pre>
$ mc cp rhel-10.0-x86_64-dvd.iso obj/iso/RedHat-E10
...-10.0-x86_64-dvd.iso: █████████████████████████████████████████████████████████████████████████ 100.0% 7.9 GiB 90 MiB/s
</pre>

===Mirror===
Often users will just want to mirror a local set of files. Note that it will mirror recursively the files in the directory but you will need to be explict if you about the destination path in this case to ensure that you get the directory created in the destination.

<pre>
$ ls -l test/
total 16
-rw-rw-r--. 1 dyarnell dyarnell 8688 Aug 19 15:17 cpuinfo
-rw-rw-r--. 1 dyarnell dyarnell 23 Aug 19 15:17 uptime
$ mc mirror /tmp/test obj/staff-test/test
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 0.0% 0 B 0 B/s
$ mc ls obj/staff-test/test/
[2026-08-19 15:18:45 EDT] 8.5KiB STANDARD cpuinfo
[2026-08-19 15:18:45 EDT] 23B STANDARD uptime
</pre>

===Find===
There is also the ability to search for file globs of specific files using the <code>find</code> sub-command for <code>mc</code>.

<pre>
$ mc find dyarnell/dyarnell_support --name "*.log"
dyarnell/dyarnell_support/mds_20170918/ceph-mds.objmds01.log
dyarnell/dyarnell_support/satellite.log
dyarnell/dyarnell_support/umiacs-49168.log
</pre>

The full AIStor Client documentation can be found here: https://docs.min.io/aistor/reference/cli/.

==rclone==
Command line client for accessing S3-like services and much more.
* https://rclone.org/downloads

We maintain rclone documentation on a separate page found [[Rclone | here]].

DataCenter

2026-04-08T18:41:32Z

Dyarnell:

UMIACS maintains a set of Data Centers that hold computing infrastructures. All equipment within our Data Centers is managed by the UMIACS Technical Staff who will provision and provide a managed set of services or operating systems on all equipment.

[[Media:UMIACS_Data_Center_Node_and_Infrastructure_Lifecycle_Support_Policy.pdf|UMIACS Data Center Node and
Infrastructure Lifecycle Support Policy]]

DataCenter

2026-04-08T18:37:36Z

Dyarnell:

UMIACS maintains a set of Data Centers that hold computing infrastructures.

[[Media:UMIACS_Data_Center_Node_and_Infrastructure_Lifecycle_Support_Policy.pdf|UMIACS Data Center Node and
Infrastructure Lifecycle Support Policy]]

DataCenter

2026-04-08T18:37:18Z

Dyarnell:

UMIACS maintains a set of Data Centers that hold computing infrastructures.

* [[Media:UMIACS_Data_Center_Node_and_Infrastructure_Lifecycle_Support_Policy.pdf|UMIACS Data Center Node and
Infrastructure Lifecycle Support Policy]]

DataCenter

2026-04-08T18:37:10Z

Dyarnell:

DataCenter

2026-04-08T18:36:46Z

Dyarnell:

UMIACS maintains a set of Data Centers that hold computing infrastructures.

[[Media:UMIACS_Data_Center_Node_and_Infrastructure_Lifecycle_Support_Policy.pdf]]

DataCenter

2026-04-08T18:36:17Z

Dyarnell:

UMIACS maintains a set of Data Centers that hold computing infrastructures.

[Uploads: UMIACS_Data_Center_Node_and_Infrastructure_Lifecycle_Support_Policy.pdf]

File:UMIACS Data Center Node and Infrastructure Lifecycle Support Policy.pdf

2026-04-08T18:35:45Z

Dyarnell:

DataCenter

2026-04-08T18:35:34Z

Dyarnell: Created page with "UMIACS maintains a set of Data Centers that hold computing infrastructures."

UMIACS maintains a set of Data Centers that hold computing infrastructures.

ClassAccounts

2025-10-28T15:19:16Z

Dyarnell: /* Overview */

==Overview==
UMIACS supports classes for all of UMIACS/CSD via class accounts that can access the [[Nexus]] cluster. Faculty may request that a class be supported by following the instructions [[ClassAccounts/Manage | here]].

==Getting an account==
Your TA or instructor will request an account for you. Once this is done, you will be notified by email that you have an account is ready to use.

'''Any questions or issues with your account, storage, or cluster use must first be made through your TA or instructor.'''

==Using your account==
To access Nexus class resources in UMIACS you will need to be on the [https://itsupport.umd.edu/itsupport?id=kb_article_view&sysparm_article=KB0016076 '''UMD Global Protect VPN''']

Once notified that your account has been installed, you can [[SSH]] to <code>nexusclass.umiacs.umd.edu</code> with your UMD directory ID and passphrase to log in to a submission node.

If you store something in a local filesystem directory (/tmp, /scratch0) on one of the two submission nodes, you will need to connect to that same submission node to access it later. The actual submission nodes are:
* <code>nexusclass00.umiacs.umd.edu</code>
* <code>nexusclass01.umiacs.umd.edu</code>

==Cleaning up your account before the end of the semester==
Class accounts for a given semester are liable to be archived and deleted after that semester's completion as early as the following:
* Winter semesters: February 1st of same year
* Spring semesters: June 1st of same year
* Summer semesters: September 1st of same year
* Fall semesters: January 1st of next year

It is your responsibility to ensure you have backed up anything you want to keep from your class account's personal or group storage (below sections) prior to the relevant date.

==Personal Storage==
Your home directory has a quota of 30GB and is located at:
<pre>
/fs/classhomes/<username>
</pre>

You can request up to another 100GB of personal storage if you would like by '''having your TA or instructor [[HelpDesk | contact staff]]'''. This storage will be located at
<pre>
/fs/class-projects/<semester><year>/<coursecode>/<username>
</pre>

where <code><semester></code> is either "spring", "summer", "fall", or "winter", <code><year></code> is the current year e.g., "2025", <coursecode> is the class' course code as listed in UMD's [https://app.testudo.umd.edu/soc/ Schedule of Classes] in all lowercase e.g., "cmsc999z", and <code><username></code> is the username.

==Group Storage==
You can also request group storage by '''having your TA or instructor [[HelpDesk | contact staff]]''' to specify the usernames of the accounts that should be in the group. Only other class accounts in the same class can be added to the group. The quota will be 100GB multiplied by the number of accounts in the group and will be located at
<pre>
/fs/class-projects/<semester><year>/<coursecode>/<groupname>
</pre>

where <code><groupname></code> is composed of:
* the abbreviated course code as used in the username e.g., "c999z"
* the character "g"
* the number of the group (starting at 0 for the first group for the class requested to us) prepended with 0s to make the total group name 8 characters long

e.g., "c999zg00".

==Cluster Usage==
'''You may not run computational jobs on any submission node.''' You must [[SLURM/JobSubmission | schedule your jobs with the SLURM workload manager]]. You can also find out more with the public documentation for the [https://slurm.schedmd.com/quickstart.html SLURM Workload Manager].

Class accounts only have access to the following submission parameters in SLURM:
* <code>--partition</code> - <code>class</code>
* <code>--account</code> - <code>class</code>
* <code>--qos</code> - <code>default</code>, <code>medium</code>, and <code>high</code>

You must specify at least the partition parameter manually in any submission command you run. If you do not specify any QoS parameter, you will receive the QoS <code>default</code>.

You can view the resource limits for each QoS by running the command <code>show_qos</code>. The value in the MaxWall column is the maximum runtime you can run a single job for each QoS, and the values in the MaxTRES column are the maximum amount of CPU cores/GPUs/memory you can request for a single job using each QoS.

Please note that you will be restricted to 32 total CPU cores, 4 total GPUs, and 256GB total RAM across all jobs you have running at once. This can be viewed with the command <code>show_partition_qos</code>.

===Example===
Here is a basic example to schedule a interactive job running bash with a single GPU in the partition <code>class</code>, with the account <code>class</code>, running with the QoS of <code>default</code> and the default CPU/memory allocation/time limit for the partition.

<pre>
$ hostname
nexusclass00.umiacs.umd.edu

$ srun --partition=class --account=class --qos=default --gres=gpu:1 --pty bash
srun: Job time limit was unset; set to partition default of 60 minutes
srun: job 1333337 queued and waiting for resources
srun: job 1333337 has been allocated resources

$ hostname
tron14.umiacs.umd.edu

$ nvidia-smi -L
GPU 0: NVIDIA RTX A4000 (UUID: GPU-55f2d3b7-9162-8b02-50de-476a012c626c)
</pre>

===Available Nodes===
You can list the available nodes and their current state with the <code>show_nodes -p class</code> command. This list of nodes is not completely static as nodes may be pulled out of service to troubleshoot GPUs or other components.

<pre>
$ show_nodes -p class
NODELIST CPUS MEMORY AVAIL_FEATURES GRES STATE
tron06 16 126214 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron07 16 126214 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron08 16 126214 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron09 16 126214 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron10 16 126217 rhel8,x86_64,Zen,EPYC-7313P,Ampere gpu:rtxa4000:4 idle
tron11 16 126217 rhel8,x86_64,Zen,EPYC-7313P,Ampere gpu:rtxa4000:4 idle
tron12 16 126218 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron13 16 126214 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron14 16 126214 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron15 16 126214 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron16 16 126217 rhel8,x86_64,Zen,EPYC-7313P,Ampere gpu:rtxa4000:4 idle
tron17 16 126217 rhel8,x86_64,Zen,EPYC-7313P,Ampere gpu:rtxa4000:4 idle
tron18 16 126217 rhel8,x86_64,Zen,EPYC-7313P,Ampere gpu:rtxa4000:4 idle
tron19 16 126217 rhel8,x86_64,Zen,EPYC-7313P,Ampere gpu:rtxa4000:4 idle
tron20 16 126217 rhel8,x86_64,Zen,EPYC-7313P,Ampere gpu:rtxa4000:4 idle
tron21 16 126218 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron22 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron23 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron24 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron25 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron26 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron27 16 126214 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron28 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron29 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron30 16 126214 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron31 16 126214 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron32 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron33 16 126214 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron34 16 126217 rhel8,x86_64,Zen,EPYC-7313P,Ampere gpu:rtxa4000:4 idle
tron35 16 126214 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron36 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron37 16 126214 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron38 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron39 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron40 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron41 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron42 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron43 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron44 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron46 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron47 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron48 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron49 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron50 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron51 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron52 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron53 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron54 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron55 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron56 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron57 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron58 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron59 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron60 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron61 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
</pre>

You can also find more granular information about an individual node with the <code>scontrol show node</code> command.

<pre>
$ scontrol show node tron06
NodeName=tron06 Arch=x86_64 CoresPerSocket=16
CPUAlloc=0 CPUEfctv=16 CPUTot=16 CPULoad=0.08
AvailableFeatures=rhel8,x86_64,Zen,EPYC-7302P,Ampere
ActiveFeatures=rhel8,x86_64,Zen,EPYC-7302P,Ampere
Gres=gpu:rtxa4000:4
NodeAddr=tron06 NodeHostName=tron06 Version=23.02.6
OS=Linux 4.18.0-513.11.1.el8_9.x86_64 #1 SMP Thu Dec 7 03:06:13 EST 2023
RealMemory=126214 AllocMem=0 FreeMem=107174 Sockets=1 Boards=1
State=IDLE ThreadsPerCore=1 TmpDisk=0 Weight=340 Owner=N/A MCS_label=N/A
Partitions=class,scavenger,tron
BootTime=2024-01-29T09:35:12 SlurmdStartTime=2024-02-05T15:14:20
LastBusyTime=2024-02-16T15:59:38 ResumeAfterTime=None
CfgTRES=cpu=16,mem=126214M,billing=638,gres/gpu=4,gres/gpu:rtxa4000=4
AllocTRES=
CapWatts=n/a
CurrentWatts=0 AveWatts=0
ExtSensorsJoules=n/s ExtSensorsWatts=0 ExtSensorsTemp=n/s
</pre>

ClassAccounts

2025-10-28T15:06:09Z

Dyarnell: /* Getting an account */

==Overview==
UMIACS supports classes for all of UMIACS/CSD via special class accounts that can access the [[Nexus]] cluster. Faculty may request that a class be supported by following the instructions [[ClassAccounts/Manage | here]].

==Getting an account==
Your TA or instructor will request an account for you. Once this is done, you will be notified by email that you have an account is ready to use.

'''Any questions or issues with your account, storage, or cluster use must first be made through your TA or instructor.'''

==Using your account==
To access Nexus class resources in UMIACS you will need to be on the [https://itsupport.umd.edu/itsupport?id=kb_article_view&sysparm_article=KB0016076 '''UMD Global Protect VPN''']

Once notified that your account has been installed, you can [[SSH]] to <code>nexusclass.umiacs.umd.edu</code> with your UMD directory ID and passphrase to log in to a submission node.

If you store something in a local filesystem directory (/tmp, /scratch0) on one of the two submission nodes, you will need to connect to that same submission node to access it later. The actual submission nodes are:
* <code>nexusclass00.umiacs.umd.edu</code>
* <code>nexusclass01.umiacs.umd.edu</code>

==Cleaning up your account before the end of the semester==
Class accounts for a given semester are liable to be archived and deleted after that semester's completion as early as the following:
* Winter semesters: February 1st of same year
* Spring semesters: June 1st of same year
* Summer semesters: September 1st of same year
* Fall semesters: January 1st of next year

It is your responsibility to ensure you have backed up anything you want to keep from your class account's personal or group storage (below sections) prior to the relevant date.

==Personal Storage==
Your home directory has a quota of 30GB and is located at:
<pre>
/fs/classhomes/<username>
</pre>

You can request up to another 100GB of personal storage if you would like by '''having your TA or instructor [[HelpDesk | contact staff]]'''. This storage will be located at
<pre>
/fs/class-projects/<semester><year>/<coursecode>/<username>
</pre>

where <code><semester></code> is either "spring", "summer", "fall", or "winter", <code><year></code> is the current year e.g., "2025", <coursecode> is the class' course code as listed in UMD's [https://app.testudo.umd.edu/soc/ Schedule of Classes] in all lowercase e.g., "cmsc999z", and <code><username></code> is the username.

==Group Storage==
You can also request group storage by '''having your TA or instructor [[HelpDesk | contact staff]]''' to specify the usernames of the accounts that should be in the group. Only other class accounts in the same class can be added to the group. The quota will be 100GB multiplied by the number of accounts in the group and will be located at
<pre>
/fs/class-projects/<semester><year>/<coursecode>/<groupname>
</pre>

where <code><groupname></code> is composed of:
* the abbreviated course code as used in the username e.g., "c999z"
* the character "g"
* the number of the group (starting at 0 for the first group for the class requested to us) prepended with 0s to make the total group name 8 characters long

e.g., "c999zg00".

==Cluster Usage==
'''You may not run computational jobs on any submission node.''' You must [[SLURM/JobSubmission | schedule your jobs with the SLURM workload manager]]. You can also find out more with the public documentation for the [https://slurm.schedmd.com/quickstart.html SLURM Workload Manager].

Class accounts only have access to the following submission parameters in SLURM:
* <code>--partition</code> - <code>class</code>
* <code>--account</code> - <code>class</code>
* <code>--qos</code> - <code>default</code>, <code>medium</code>, and <code>high</code>

You must specify at least the partition parameter manually in any submission command you run. If you do not specify any QoS parameter, you will receive the QoS <code>default</code>.

You can view the resource limits for each QoS by running the command <code>show_qos</code>. The value in the MaxWall column is the maximum runtime you can run a single job for each QoS, and the values in the MaxTRES column are the maximum amount of CPU cores/GPUs/memory you can request for a single job using each QoS.

Please note that you will be restricted to 32 total CPU cores, 4 total GPUs, and 256GB total RAM across all jobs you have running at once. This can be viewed with the command <code>show_partition_qos</code>.

===Example===
Here is a basic example to schedule a interactive job running bash with a single GPU in the partition <code>class</code>, with the account <code>class</code>, running with the QoS of <code>default</code> and the default CPU/memory allocation/time limit for the partition.

<pre>
$ hostname
nexusclass00.umiacs.umd.edu

$ srun --partition=class --account=class --qos=default --gres=gpu:1 --pty bash
srun: Job time limit was unset; set to partition default of 60 minutes
srun: job 1333337 queued and waiting for resources
srun: job 1333337 has been allocated resources

$ hostname
tron14.umiacs.umd.edu

$ nvidia-smi -L
GPU 0: NVIDIA RTX A4000 (UUID: GPU-55f2d3b7-9162-8b02-50de-476a012c626c)
</pre>

===Available Nodes===
You can list the available nodes and their current state with the <code>show_nodes -p class</code> command. This list of nodes is not completely static as nodes may be pulled out of service to troubleshoot GPUs or other components.

<pre>
$ show_nodes -p class
NODELIST CPUS MEMORY AVAIL_FEATURES GRES STATE
tron06 16 126214 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron07 16 126214 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron08 16 126214 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron09 16 126214 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron10 16 126217 rhel8,x86_64,Zen,EPYC-7313P,Ampere gpu:rtxa4000:4 idle
tron11 16 126217 rhel8,x86_64,Zen,EPYC-7313P,Ampere gpu:rtxa4000:4 idle
tron12 16 126218 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron13 16 126214 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron14 16 126214 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron15 16 126214 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron16 16 126217 rhel8,x86_64,Zen,EPYC-7313P,Ampere gpu:rtxa4000:4 idle
tron17 16 126217 rhel8,x86_64,Zen,EPYC-7313P,Ampere gpu:rtxa4000:4 idle
tron18 16 126217 rhel8,x86_64,Zen,EPYC-7313P,Ampere gpu:rtxa4000:4 idle
tron19 16 126217 rhel8,x86_64,Zen,EPYC-7313P,Ampere gpu:rtxa4000:4 idle
tron20 16 126217 rhel8,x86_64,Zen,EPYC-7313P,Ampere gpu:rtxa4000:4 idle
tron21 16 126218 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron22 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron23 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron24 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron25 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron26 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron27 16 126214 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron28 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron29 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron30 16 126214 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron31 16 126214 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron32 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron33 16 126214 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron34 16 126217 rhel8,x86_64,Zen,EPYC-7313P,Ampere gpu:rtxa4000:4 idle
tron35 16 126214 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron36 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron37 16 126214 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron38 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron39 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron40 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron41 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron42 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron43 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron44 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron46 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron47 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron48 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron49 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron50 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron51 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron52 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron53 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron54 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron55 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron56 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron57 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron58 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron59 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron60 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron61 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
</pre>

You can also find more granular information about an individual node with the <code>scontrol show node</code> command.

<pre>
$ scontrol show node tron06
NodeName=tron06 Arch=x86_64 CoresPerSocket=16
CPUAlloc=0 CPUEfctv=16 CPUTot=16 CPULoad=0.08
AvailableFeatures=rhel8,x86_64,Zen,EPYC-7302P,Ampere
ActiveFeatures=rhel8,x86_64,Zen,EPYC-7302P,Ampere
Gres=gpu:rtxa4000:4
NodeAddr=tron06 NodeHostName=tron06 Version=23.02.6
OS=Linux 4.18.0-513.11.1.el8_9.x86_64 #1 SMP Thu Dec 7 03:06:13 EST 2023
RealMemory=126214 AllocMem=0 FreeMem=107174 Sockets=1 Boards=1
State=IDLE ThreadsPerCore=1 TmpDisk=0 Weight=340 Owner=N/A MCS_label=N/A
Partitions=class,scavenger,tron
BootTime=2024-01-29T09:35:12 SlurmdStartTime=2024-02-05T15:14:20
LastBusyTime=2024-02-16T15:59:38 ResumeAfterTime=None
CfgTRES=cpu=16,mem=126214M,billing=638,gres/gpu=4,gres/gpu:rtxa4000=4
AllocTRES=
CapWatts=n/a
CurrentWatts=0 AveWatts=0
ExtSensorsJoules=n/s ExtSensorsWatts=0 ExtSensorsTemp=n/s
</pre>

ClassAccounts

2025-10-02T14:13:46Z

Dyarnell: /* Using your account */

==Overview==
UMIACS supports classes for all of UMIACS/CSD via special class accounts that can access the [[Nexus]] cluster. Faculty may request that a class be supported by following the instructions [[ClassAccounts/Manage | here]].

==Getting an account==
Your TA or instructor will request an account for you. Once this is done, you will be notified by email that you have an account to redeem. If you have not received an email, please contact your TA or instructor. '''You must redeem the account within 7 days or else the redemption token will expire.''' If your redemption token does expire, please contact your TA or instructor to have it renewed.

Once you do redeem your account, you will need to wait until you get a confirmation email that your account has been installed. This is typically done once a day on days that the University is open for business.

'''Any questions or issues with your account, storage, or cluster use must first be made through your TA or instructor.'''

==Using your account==
To access Nexus class resources in UMIACS you will need to be on the [https://itsupport.umd.edu/itsupport?id=kb_article_view&sysparm_article=KB0016076 '''UMD Global Protect VPN''']

Once notified that your account has been installed, you can [[SSH]] to <code>nexusclass.umiacs.umd.edu</code> with your UMD directory ID and passphrase to log in to a submission node.

If you store something in a local filesystem directory (/tmp, /scratch0) on one of the two submission nodes, you will need to connect to that same submission node to access it later. The actual submission nodes are:
* <code>nexusclass00.umiacs.umd.edu</code>
* <code>nexusclass01.umiacs.umd.edu</code>

==Cleaning up your account before the end of the semester==
Class accounts for a given semester are liable to be archived and deleted after that semester's completion as early as the following:
* Winter semesters: February 1st of same year
* Spring semesters: June 1st of same year
* Summer semesters: September 1st of same year
* Fall semesters: January 1st of next year

It is your responsibility to ensure you have backed up anything you want to keep from your class account's personal or group storage (below sections) prior to the relevant date.

==Personal Storage==
Your home directory has a quota of 30GB and is located at:
<pre>
/fs/classhomes/<username>
</pre>

You can request up to another 100GB of personal storage if you would like by '''having your TA or instructor [[HelpDesk | contact staff]]'''. This storage will be located at
<pre>
/fs/class-projects/<semester><year>/<coursecode>/<username>
</pre>

where <code><semester></code> is either "spring", "summer", "fall", or "winter", <code><year></code> is the current year e.g., "2025", <coursecode> is the class' course code as listed in UMD's [https://app.testudo.umd.edu/soc/ Schedule of Classes] in all lowercase e.g., "cmsc999z", and <code><username></code> is the username.

==Group Storage==
You can also request group storage by '''having your TA or instructor [[HelpDesk | contact staff]]''' to specify the usernames of the accounts that should be in the group. Only other class accounts in the same class can be added to the group. The quota will be 100GB multiplied by the number of accounts in the group and will be located at
<pre>
/fs/class-projects/<semester><year>/<coursecode>/<groupname>
</pre>

where <code><groupname></code> is composed of:
* the abbreviated course code as used in the username e.g., "c999z"
* the character "g"
* the number of the group (starting at 0 for the first group for the class requested to us) prepended with 0s to make the total group name 8 characters long

e.g., "c999zg00".

==Cluster Usage==
'''You may not run computational jobs on any submission node.''' You must [[SLURM/JobSubmission | schedule your jobs with the SLURM workload manager]]. You can also find out more with the public documentation for the [https://slurm.schedmd.com/quickstart.html SLURM Workload Manager].

Class accounts only have access to the following submission parameters in SLURM:
* <code>--partition</code> - <code>class</code>
* <code>--account</code> - <code>class</code>
* <code>--qos</code> - <code>default</code>, <code>medium</code>, and <code>high</code>

You must specify at least the partition parameter manually in any submission command you run. If you do not specify any QoS parameter, you will receive the QoS <code>default</code>.

You can view the resource limits for each QoS by running the command <code>show_qos</code>. The value in the MaxWall column is the maximum runtime you can run a single job for each QoS, and the values in the MaxTRES column are the maximum amount of CPU cores/GPUs/memory you can request for a single job using each QoS.

Please note that you will be restricted to 32 total CPU cores, 4 total GPUs, and 256GB total RAM across all jobs you have running at once. This can be viewed with the command <code>show_partition_qos</code>.

===Example===
Here is a basic example to schedule a interactive job running bash with a single GPU in the partition <code>class</code>, with the account <code>class</code>, running with the QoS of <code>default</code> and the default CPU/memory allocation/time limit for the partition.

<pre>
$ hostname
nexusclass00.umiacs.umd.edu

$ srun --partition=class --account=class --qos=default --gres=gpu:1 --pty bash
srun: Job time limit was unset; set to partition default of 60 minutes
srun: job 1333337 queued and waiting for resources
srun: job 1333337 has been allocated resources

$ hostname
tron14.umiacs.umd.edu

$ nvidia-smi -L
GPU 0: NVIDIA RTX A4000 (UUID: GPU-55f2d3b7-9162-8b02-50de-476a012c626c)
</pre>

===Available Nodes===
You can list the available nodes and their current state with the <code>show_nodes -p class</code> command. This list of nodes is not completely static as nodes may be pulled out of service to troubleshoot GPUs or other components.

<pre>
$ show_nodes -p class
NODELIST CPUS MEMORY AVAIL_FEATURES GRES STATE
tron06 16 126214 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron07 16 126214 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron08 16 126214 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron09 16 126214 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron10 16 126217 rhel8,x86_64,Zen,EPYC-7313P,Ampere gpu:rtxa4000:4 idle
tron11 16 126217 rhel8,x86_64,Zen,EPYC-7313P,Ampere gpu:rtxa4000:4 idle
tron12 16 126218 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron13 16 126214 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron14 16 126214 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron15 16 126214 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron16 16 126217 rhel8,x86_64,Zen,EPYC-7313P,Ampere gpu:rtxa4000:4 idle
tron17 16 126217 rhel8,x86_64,Zen,EPYC-7313P,Ampere gpu:rtxa4000:4 idle
tron18 16 126217 rhel8,x86_64,Zen,EPYC-7313P,Ampere gpu:rtxa4000:4 idle
tron19 16 126217 rhel8,x86_64,Zen,EPYC-7313P,Ampere gpu:rtxa4000:4 idle
tron20 16 126217 rhel8,x86_64,Zen,EPYC-7313P,Ampere gpu:rtxa4000:4 idle
tron21 16 126218 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron22 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron23 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron24 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron25 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron26 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron27 16 126214 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron28 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron29 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron30 16 126214 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron31 16 126214 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron32 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron33 16 126214 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron34 16 126217 rhel8,x86_64,Zen,EPYC-7313P,Ampere gpu:rtxa4000:4 idle
tron35 16 126214 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron36 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron37 16 126214 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron38 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron39 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron40 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron41 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron42 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron43 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron44 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron46 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron47 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron48 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron49 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron50 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron51 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron52 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron53 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron54 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron55 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron56 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron57 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron58 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron59 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron60 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron61 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
</pre>

You can also find more granular information about an individual node with the <code>scontrol show node</code> command.

<pre>
$ scontrol show node tron06
NodeName=tron06 Arch=x86_64 CoresPerSocket=16
CPUAlloc=0 CPUEfctv=16 CPUTot=16 CPULoad=0.08
AvailableFeatures=rhel8,x86_64,Zen,EPYC-7302P,Ampere
ActiveFeatures=rhel8,x86_64,Zen,EPYC-7302P,Ampere
Gres=gpu:rtxa4000:4
NodeAddr=tron06 NodeHostName=tron06 Version=23.02.6
OS=Linux 4.18.0-513.11.1.el8_9.x86_64 #1 SMP Thu Dec 7 03:06:13 EST 2023
RealMemory=126214 AllocMem=0 FreeMem=107174 Sockets=1 Boards=1
State=IDLE ThreadsPerCore=1 TmpDisk=0 Weight=340 Owner=N/A MCS_label=N/A
Partitions=class,scavenger,tron
BootTime=2024-01-29T09:35:12 SlurmdStartTime=2024-02-05T15:14:20
LastBusyTime=2024-02-16T15:59:38 ResumeAfterTime=None
CfgTRES=cpu=16,mem=126214M,billing=638,gres/gpu=4,gres/gpu:rtxa4000=4
AllocTRES=
CapWatts=n/a
CurrentWatts=0 AveWatts=0
ExtSensorsJoules=n/s ExtSensorsWatts=0 ExtSensorsTemp=n/s
</pre>

ClassAccounts

2025-09-22T20:56:33Z

Dyarnell: /* Personal Storage */

==Overview==
UMIACS supports classes for all of UMIACS/CSD via special class accounts that can access the [[Nexus]] cluster. Faculty may request that a class be supported by following the instructions [[ClassAccounts/Manage | here]].

==Getting an account==
Your TA or instructor will request an account for you. Once this is done, you will be notified by email that you have an account to redeem. If you have not received an email, please contact your TA or instructor. '''You must redeem the account within 7 days or else the redemption token will expire.''' If your redemption token does expire, please contact your TA or instructor to have it renewed.

Once you do redeem your account, you will need to wait until you get a confirmation email that your account has been installed. This is typically done once a day on days that the University is open for business.

'''Any questions or issues with your account, storage, or cluster use must first be made through your TA or instructor.'''

==Using your account==
To access Nexus class resources in UMIACS you will need to be on the UMD Global Protect VPN.

Once notified that your account has been installed, you can [[SSH]] to <code>nexusclass.umiacs.umd.edu</code> with your assigned username and your UMD passphrase to log in to a submission node.

If you store something in a local filesystem directory (/tmp, /scratch0) on one of the two submission nodes, you will need to connect to that same submission node to access it later. The actual submission nodes are:
* <code>nexusclass00.umiacs.umd.edu</code>
* <code>nexusclass01.umiacs.umd.edu</code>

==Cleaning up your account before the end of the semester==
Class accounts for a given semester are liable to be archived and deleted after that semester's completion as early as the following:
* Winter semesters: February 1st of same year
* Spring semesters: June 1st of same year
* Summer semesters: September 1st of same year
* Fall semesters: January 1st of next year

It is your responsibility to ensure you have backed up anything you want to keep from your class account's personal or group storage (below sections) prior to the relevant date.

==Personal Storage==
Your home directory has a quota of 30GB and is located at:
<pre>
/fs/classhomes/<username>
</pre>

You can request up to another 100GB of personal storage if you would like by '''having your TA or instructor [[HelpDesk | contact staff]]'''. This storage will be located at
<pre>
/fs/class-projects/<semester><year>/<coursecode>/<username>
</pre>

where <code><semester></code> is either "spring", "summer", "fall", or "winter", <code><year></code> is the current year e.g., "2025", <coursecode> is the class' course code as listed in UMD's [https://app.testudo.umd.edu/soc/ Schedule of Classes] in all lowercase e.g., "cmsc999z", and <code><username></code> is the username.

==Group Storage==
You can also request group storage by '''having your TA or instructor [[HelpDesk | contact staff]]''' to specify the usernames of the accounts that should be in the group. Only other class accounts in the same class can be added to the group. The quota will be 100GB multiplied by the number of accounts in the group and will be located at
<pre>
/fs/class-projects/<semester><year>/<coursecode>/<groupname>
</pre>

where <code><groupname></code> is composed of:
* the abbreviated course code as used in the username e.g., "c999z"
* the character "g"
* the number of the group (starting at 0 for the first group for the class requested to us) prepended with 0s to make the total group name 8 characters long

e.g., "c999zg00".

==Cluster Usage==
'''You may not run computational jobs on any submission node.''' You must [[SLURM/JobSubmission | schedule your jobs with the SLURM workload manager]]. You can also find out more with the public documentation for the [https://slurm.schedmd.com/quickstart.html SLURM Workload Manager].

Class accounts only have access to the following submission parameters in SLURM:
* <code>--partition</code> - <code>class</code>
* <code>--account</code> - <code>class</code>
* <code>--qos</code> - <code>default</code>, <code>medium</code>, and <code>high</code>

You must specify at least the partition parameter manually in any submission command you run. If you do not specify any QoS parameter, you will receive the QoS <code>default</code>.

You can view the resource limits for each QoS by running the command <code>show_qos</code>. The value in the MaxWall column is the maximum runtime you can run a single job for each QoS, and the values in the MaxTRES column are the maximum amount of CPU cores/GPUs/memory you can request for a single job using each QoS.

Please note that you will be restricted to 32 total CPU cores, 4 total GPUs, and 256GB total RAM across all jobs you have running at once. This can be viewed with the command <code>show_partition_qos</code>.

===Example===
Here is a basic example to schedule a interactive job running bash with a single GPU in the partition <code>class</code>, with the account <code>class</code>, running with the QoS of <code>default</code> and the default CPU/memory allocation/time limit for the partition.

<pre>
$ hostname
nexusclass00.umiacs.umd.edu

$ srun --partition=class --account=class --qos=default --gres=gpu:1 --pty bash
srun: Job time limit was unset; set to partition default of 60 minutes
srun: job 1333337 queued and waiting for resources
srun: job 1333337 has been allocated resources

$ hostname
tron14.umiacs.umd.edu

$ nvidia-smi -L
GPU 0: NVIDIA RTX A4000 (UUID: GPU-55f2d3b7-9162-8b02-50de-476a012c626c)
</pre>

===Available Nodes===
You can list the available nodes and their current state with the <code>show_nodes -p class</code> command. This list of nodes is not completely static as nodes may be pulled out of service to troubleshoot GPUs or other components.

<pre>
$ show_nodes -p class
NODELIST CPUS MEMORY AVAIL_FEATURES GRES STATE
tron06 16 126214 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron07 16 126214 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron08 16 126214 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron09 16 126214 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron10 16 126217 rhel8,x86_64,Zen,EPYC-7313P,Ampere gpu:rtxa4000:4 idle
tron11 16 126217 rhel8,x86_64,Zen,EPYC-7313P,Ampere gpu:rtxa4000:4 idle
tron12 16 126218 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron13 16 126214 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron14 16 126214 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron15 16 126214 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron16 16 126217 rhel8,x86_64,Zen,EPYC-7313P,Ampere gpu:rtxa4000:4 idle
tron17 16 126217 rhel8,x86_64,Zen,EPYC-7313P,Ampere gpu:rtxa4000:4 idle
tron18 16 126217 rhel8,x86_64,Zen,EPYC-7313P,Ampere gpu:rtxa4000:4 idle
tron19 16 126217 rhel8,x86_64,Zen,EPYC-7313P,Ampere gpu:rtxa4000:4 idle
tron20 16 126217 rhel8,x86_64,Zen,EPYC-7313P,Ampere gpu:rtxa4000:4 idle
tron21 16 126218 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron22 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron23 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron24 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron25 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron26 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron27 16 126214 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron28 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron29 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron30 16 126214 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron31 16 126214 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron32 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron33 16 126214 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron34 16 126217 rhel8,x86_64,Zen,EPYC-7313P,Ampere gpu:rtxa4000:4 idle
tron35 16 126214 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron36 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron37 16 126214 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron38 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron39 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron40 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron41 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron42 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron43 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron44 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron46 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron47 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron48 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron49 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron50 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron51 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron52 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron53 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron54 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron55 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron56 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron57 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron58 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron59 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron60 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron61 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
</pre>

You can also find more granular information about an individual node with the <code>scontrol show node</code> command.

<pre>
$ scontrol show node tron06
NodeName=tron06 Arch=x86_64 CoresPerSocket=16
CPUAlloc=0 CPUEfctv=16 CPUTot=16 CPULoad=0.08
AvailableFeatures=rhel8,x86_64,Zen,EPYC-7302P,Ampere
ActiveFeatures=rhel8,x86_64,Zen,EPYC-7302P,Ampere
Gres=gpu:rtxa4000:4
NodeAddr=tron06 NodeHostName=tron06 Version=23.02.6
OS=Linux 4.18.0-513.11.1.el8_9.x86_64 #1 SMP Thu Dec 7 03:06:13 EST 2023
RealMemory=126214 AllocMem=0 FreeMem=107174 Sockets=1 Boards=1
State=IDLE ThreadsPerCore=1 TmpDisk=0 Weight=340 Owner=N/A MCS_label=N/A
Partitions=class,scavenger,tron
BootTime=2024-01-29T09:35:12 SlurmdStartTime=2024-02-05T15:14:20
LastBusyTime=2024-02-16T15:59:38 ResumeAfterTime=None
CfgTRES=cpu=16,mem=126214M,billing=638,gres/gpu=4,gres/gpu:rtxa4000=4
AllocTRES=
CapWatts=n/a
CurrentWatts=0 AveWatts=0
ExtSensorsJoules=n/s ExtSensorsWatts=0 ExtSensorsTemp=n/s
</pre>

ClassAccounts

2025-09-22T20:55:03Z

Dyarnell:

==Overview==
UMIACS supports classes for all of UMIACS/CSD via special class accounts that can access the [[Nexus]] cluster. Faculty may request that a class be supported by following the instructions [[ClassAccounts/Manage | here]].

==Getting an account==
Your TA or instructor will request an account for you. Once this is done, you will be notified by email that you have an account to redeem. If you have not received an email, please contact your TA or instructor. '''You must redeem the account within 7 days or else the redemption token will expire.''' If your redemption token does expire, please contact your TA or instructor to have it renewed.

Once you do redeem your account, you will need to wait until you get a confirmation email that your account has been installed. This is typically done once a day on days that the University is open for business.

'''Any questions or issues with your account, storage, or cluster use must first be made through your TA or instructor.'''

==Using your account==
To access Nexus class resources in UMIACS you will need to be on the UMD Global Protect VPN.

Once notified that your account has been installed, you can [[SSH]] to <code>nexusclass.umiacs.umd.edu</code> with your assigned username and your UMD passphrase to log in to a submission node.

If you store something in a local filesystem directory (/tmp, /scratch0) on one of the two submission nodes, you will need to connect to that same submission node to access it later. The actual submission nodes are:
* <code>nexusclass00.umiacs.umd.edu</code>
* <code>nexusclass01.umiacs.umd.edu</code>

==Cleaning up your account before the end of the semester==
Class accounts for a given semester are liable to be archived and deleted after that semester's completion as early as the following:
* Winter semesters: February 1st of same year
* Spring semesters: June 1st of same year
* Summer semesters: September 1st of same year
* Fall semesters: January 1st of next year

It is your responsibility to ensure you have backed up anything you want to keep from your class account's personal or group storage (below sections) prior to the relevant date.

==Personal Storage==
Your home directory has a quota of 30GB and is located at:
<pre>
/fs/classhomes/<semester><year>/<coursecode>/<username>
</pre>

where <code><semester></code> is either "spring", "summer", "fall", or "winter", <code><year></code> is the current year e.g., "2021", <coursecode> is the class' course code as listed in UMD's [https://app.testudo.umd.edu/soc/ Schedule of Classes] in all lowercase e.g., "cmsc999z", and <code><username></code> is the username mentioned in the email you received to redeem the account e.g., "c999z000".

You can request up to another 100GB of personal storage if you would like by '''having your TA or instructor [[HelpDesk | contact staff]]'''. This storage will be located at
<pre>
/fs/class-projects/<semester><year>/<coursecode>/<username>
</pre>

==Group Storage==
You can also request group storage by '''having your TA or instructor [[HelpDesk | contact staff]]''' to specify the usernames of the accounts that should be in the group. Only other class accounts in the same class can be added to the group. The quota will be 100GB multiplied by the number of accounts in the group and will be located at
<pre>
/fs/class-projects/<semester><year>/<coursecode>/<groupname>
</pre>

where <code><groupname></code> is composed of:
* the abbreviated course code as used in the username e.g., "c999z"
* the character "g"
* the number of the group (starting at 0 for the first group for the class requested to us) prepended with 0s to make the total group name 8 characters long

e.g., "c999zg00".

==Cluster Usage==
'''You may not run computational jobs on any submission node.''' You must [[SLURM/JobSubmission | schedule your jobs with the SLURM workload manager]]. You can also find out more with the public documentation for the [https://slurm.schedmd.com/quickstart.html SLURM Workload Manager].

Class accounts only have access to the following submission parameters in SLURM:
* <code>--partition</code> - <code>class</code>
* <code>--account</code> - <code>class</code>
* <code>--qos</code> - <code>default</code>, <code>medium</code>, and <code>high</code>

You must specify at least the partition parameter manually in any submission command you run. If you do not specify any QoS parameter, you will receive the QoS <code>default</code>.

You can view the resource limits for each QoS by running the command <code>show_qos</code>. The value in the MaxWall column is the maximum runtime you can run a single job for each QoS, and the values in the MaxTRES column are the maximum amount of CPU cores/GPUs/memory you can request for a single job using each QoS.

Please note that you will be restricted to 32 total CPU cores, 4 total GPUs, and 256GB total RAM across all jobs you have running at once. This can be viewed with the command <code>show_partition_qos</code>.

===Example===
Here is a basic example to schedule a interactive job running bash with a single GPU in the partition <code>class</code>, with the account <code>class</code>, running with the QoS of <code>default</code> and the default CPU/memory allocation/time limit for the partition.

<pre>
$ hostname
nexusclass00.umiacs.umd.edu

$ srun --partition=class --account=class --qos=default --gres=gpu:1 --pty bash
srun: Job time limit was unset; set to partition default of 60 minutes
srun: job 1333337 queued and waiting for resources
srun: job 1333337 has been allocated resources

$ hostname
tron14.umiacs.umd.edu

$ nvidia-smi -L
GPU 0: NVIDIA RTX A4000 (UUID: GPU-55f2d3b7-9162-8b02-50de-476a012c626c)
</pre>

===Available Nodes===
You can list the available nodes and their current state with the <code>show_nodes -p class</code> command. This list of nodes is not completely static as nodes may be pulled out of service to troubleshoot GPUs or other components.

<pre>
$ show_nodes -p class
NODELIST CPUS MEMORY AVAIL_FEATURES GRES STATE
tron06 16 126214 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron07 16 126214 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron08 16 126214 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron09 16 126214 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron10 16 126217 rhel8,x86_64,Zen,EPYC-7313P,Ampere gpu:rtxa4000:4 idle
tron11 16 126217 rhel8,x86_64,Zen,EPYC-7313P,Ampere gpu:rtxa4000:4 idle
tron12 16 126218 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron13 16 126214 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron14 16 126214 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron15 16 126214 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron16 16 126217 rhel8,x86_64,Zen,EPYC-7313P,Ampere gpu:rtxa4000:4 idle
tron17 16 126217 rhel8,x86_64,Zen,EPYC-7313P,Ampere gpu:rtxa4000:4 idle
tron18 16 126217 rhel8,x86_64,Zen,EPYC-7313P,Ampere gpu:rtxa4000:4 idle
tron19 16 126217 rhel8,x86_64,Zen,EPYC-7313P,Ampere gpu:rtxa4000:4 idle
tron20 16 126217 rhel8,x86_64,Zen,EPYC-7313P,Ampere gpu:rtxa4000:4 idle
tron21 16 126218 rhel8,x86_64,Zen,EPYC-7302P,Ampere gpu:rtxa4000:4 idle
tron22 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron23 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron24 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron25 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron26 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron27 16 126214 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron28 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron29 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron30 16 126214 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron31 16 126214 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron32 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron33 16 126214 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron34 16 126217 rhel8,x86_64,Zen,EPYC-7313P,Ampere gpu:rtxa4000:4 idle
tron35 16 126214 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron36 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron37 16 126214 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron38 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron39 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron40 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron41 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron42 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron43 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron44 16 126218 rhel8,x86_64,Zen,EPYC-7302,Ampere gpu:rtxa4000:4 idle
tron46 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron47 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron48 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron49 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron50 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron51 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron52 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron53 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron54 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron55 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron56 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron57 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron58 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron59 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron60 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
tron61 48 255232 rhel8,x86_64,Zen,EPYC-7352,Ampere gpu:rtxa5000:8 idle
</pre>

You can also find more granular information about an individual node with the <code>scontrol show node</code> command.

<pre>
$ scontrol show node tron06
NodeName=tron06 Arch=x86_64 CoresPerSocket=16
CPUAlloc=0 CPUEfctv=16 CPUTot=16 CPULoad=0.08
AvailableFeatures=rhel8,x86_64,Zen,EPYC-7302P,Ampere
ActiveFeatures=rhel8,x86_64,Zen,EPYC-7302P,Ampere
Gres=gpu:rtxa4000:4
NodeAddr=tron06 NodeHostName=tron06 Version=23.02.6
OS=Linux 4.18.0-513.11.1.el8_9.x86_64 #1 SMP Thu Dec 7 03:06:13 EST 2023
RealMemory=126214 AllocMem=0 FreeMem=107174 Sockets=1 Boards=1
State=IDLE ThreadsPerCore=1 TmpDisk=0 Weight=340 Owner=N/A MCS_label=N/A
Partitions=class,scavenger,tron
BootTime=2024-01-29T09:35:12 SlurmdStartTime=2024-02-05T15:14:20
LastBusyTime=2024-02-16T15:59:38 ResumeAfterTime=None
CfgTRES=cpu=16,mem=126214M,billing=638,gres/gpu=4,gres/gpu:rtxa4000=4
AllocTRES=
CapWatts=n/a
CurrentWatts=0 AveWatts=0
ExtSensorsJoules=n/s ExtSensorsWatts=0 ExtSensorsTemp=n/s
</pre>

SSHFileTransferProtocol

2025-06-25T17:59:53Z

Dyarnell:

SSH File Transfer Protocol ([http://en.wikipedia.org/wiki/SSH_file_transfer_protocol SFTP]) is a network protocol used to securely transfer and manage files on remote systems. SFTP is layered on top of the [[SSH]] protocol, and is preferred over [[FTP]] as a method of remote file transfer.

'''Warning:''' running interactive programs in your shell initialization files, such as starting another shell, causes SFTP to fail. See [[Shell]] on how to correctly change the shell you are using.

==Connecting to an SFTP Server==
Under [[RHEL | Red Hat Enterprise Linux (RHEL)]], [[Ubuntu]], and macOS, the following command from a terminal will connect a client computer to a remote host.

<pre>sftp bkirz@$HOSTNAME.umiacs.umd.edu </pre>
Replace $HOSTNAME with the name of the host you are trying to connect.

For Windows hosts please refer to [[WinSCP]] which is a SFTP compatible file transfer program. It is per-installed on UMIACS supported Windows hosts.

==Further Information==
More information about SFTP can be found at [http://www.openssh.org/ http://www.openssh.org/].

Accounts/UMD

2025-06-20T13:57:15Z

Dyarnell:

Before [[Accounts#Request_a_UMIACS_account | requesting a UMIACS account]], any new prospective UMIACS account holder needs to have a UMD directory ID. This is to allow them to [https://itsupport.umd.edu/itsupport?id=kb_article_view&sysparm_article=KB0016076 connect to UMD's GlobalProtect VPN] to be delegated access to our networked resources after their account install is completed.

Existing UMD students, faculty, and staff should already have directory IDs. For external collaborators, at other institutions or otherwise, faculty members will need to request affiliate appointments for them. An overview of the different types of affiliate appointments can be found [https://itsupport.umd.edu/itsupport?id=kb_article_view&sysparm_article=KB0012328#mcetoc_1hjletjg132 here]. To actually request an appointment, fill out [https://wiki.umiacs.umd.edu/umiacs/images/6/6d/Affiliate_Data_Collection_Form_Blank2.pdf this form] and send it to [mailto:umiacs-payroll@umiacs.umd.edu umiacs-payroll@umiacs.umd.edu].

If the person the appointment is being requested for already has a UMIACS account, please be sure to request their directory ID be the same as their UMIACS username, if the ID is available.

Once the person gets their appointment and thus their directory ID, they can fill out the UMIACS account request form (if new) or [[HelpDesk | contact technical staff]] to get access to their existing UMIACS account again (if existing). If filling out the new UMIACS account request form, please let the person know they should use their directory ID as the requested UMIACS username.