If you are familiar with supercomputing on Sol or Agave/Phoenix, Aloe will feel quite similar. However, due to the security requirements and technological differncesdifferences, there are several differences changes between general-use systems like Sol and HIPPA complement systems like Aloe.
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Internet Access is Restricted
...
While Sol and Agave/Phoenix have very large scratch filesystems for high IO computing, Aloe does not. Computing directly from your Home directory or project space is perfectly acceptable as these are designed to be computed on used for computing in this environment. If you have a job that benefits from fast disk access, then you can use the per-job ephemeral storage located at /tmp for faster results.
See ##Ignore for now Using /tmp in Aloe for more information.
Private Slurm Data
Many aspects of the Slurm scheduler have been marked as private and are not viewable to users. For example, you may see the message: slurm_load_partitions: Access/permission denied when viewing slurm information, such as the squeue or myjobs commands. This is not an error; this is expected behavior. This message can be ignored as it does not limit you from viewing information about your jobs and only restricts viewing overall information about partitions, which has been intentionally restricted.
Non-Accessible Compute Nodes
You are not able to SSH directly to a compute node, even if you have a job running on it. You will receive the error: Access denied by pam_slurm_adopt: you have no active jobs on this node. This is expected behavior.
...
Downloading files is restricted to using Globus
Uploading files is discouraged. Use See using Globus
The job composer has been disabled
The Active Jobs will only display your jobs regardless of the filter
A status page is not available at this time
There is no way to submit support tickets via the web portal. Instead, email asre-support@asu.edu
...