Usage of satori

Security

• All access to satori must use SSH encryption.
  SSH telnet clients are available for unix, Mac and PC
  • Unix: SSH (Secure Shell) version 1.2.30 from the University mirror site
  • PC: Tera Term Pro v2.3 for MS-Windows products
  • Mac: NiftyTelnet for Macintosh
• Access to satori is restricted to the IP address given at user registration time. Access from ALL other addresses is blocked.
• Users must inform appropriate staff if they have reason to believe the security of the facility has been compromised or is at risk.
  
  SSH installation details

Home directories

satori has two types of disc connection, SCSI and HiPPI. The HiPPI connected discs are much faster but have a blocksize of 1MByte which is unsuitable for small files (such as program source, etc.). Each user has a home directory on the SCSI file system (/home/users/group/username) with a link (/home/users/group/username/data) to a directory on the HiPPI file system (/data/users/group/username). Users should choose the appropriate file system for their files based on size and access speed requirements.

Queueing System

satori is a real memory machine. In order to achieve the greatest throughput jobs need to be scheduled to ensure that they don't enter a state of contention for main memory. This is achieved by setting an interactive cpu time-limit of 300 seconds. All longer jobs must be submitted to a batch queue for processing. There are seven queues set up for use by University users.

• express
  This is the express queue. It has the highest priority of any queue and is usable by all users. It has a time-limit of 1000 seconds and a size-limit of 1GByte. It is intended for short jobs such as compiles or test runs of large jobs.
• uom_1hr
  uom_4hr
  These queues are designed for small, quick jobs. Both queues have a size-limit of 256MByte and time-limits of 4000 and 15000 seconds respectively. Both queues have the same running priority but queued jobs on uom_1hr are started before queued jobs from uom_4hr. The two queues share a total run-limit of 4 jobs and a per-user run-limit of 2.
• uom_day
  uom_week
  These are the normal queues. They have a size-limit of 1GB and time-limits of 1 day and 1 week respectively. As with the above pair they have the same running priority (lower than the above) and jobs from uom_day are started before jobs from uom_week. The queues share a total run-limit of 2 jobs and a per-user run-limit of 1.
• uom_large
  This is an unlimited queue. Jobs of any size or duration can be run on this queue, although only one job at a time will be run and jobs from this queue have the lowest execution priority.
• uom_long
  This is an unlimited time queue for small jobs (less than 256 MByte memory). Jobs from this queue run at a lower priority than all except uom_large.

In addition to the queueing system, satori uses an additional means to control resources called Resource Sharing Groups. These control memory and cpu allocation. The major effects for UofM users is that since they are only guarenteed half the machine, external jobs can cause UofM jobs to be swapped out, and the uom_large queue isn't guarenteed any space hence all other jobs can cause jobs on this queue to be swapped out. As a slight compensation, jobs on both uom_large and uom_long have a guarenteed memory resident time so they won't be swapped out too soon after being swapped in.

E-mail

satori is not intended to be a general purpose system. It cannot receive e-mail from outside. The system can however send mail and all users should set a .forward file to point to their usual e-mail address so that any e-mail generated by the system will be redirected.

Manuals

The online manuals are only available from within the university. They can be found at http://www.hpc.unimelb.edu.au/nec/glblcont.html Please note that these are copyright and it is an offence (under the usual fair-use provisos) to print (i.e. copy) them.