Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Request

To request a class PIRG on Talapas send an email to racs@uoregon.edu

Include the following information:

  • PIRG name - usually the class name, e.g. erth363

  • PIRG PI - instructor of the class and responsible for student compute activity and storage costs

  • PIRG members - provide an export of the class roster from Canvas including StudentDuckID, StudentFirstName, Student,LastName (95# is not necessary)

  • Storage requirements - 2TB is the default capacity provisioned, see https://hpcf.uoregon.edu/content/business-model for information on storage tiers

  • Billing index - invoices are emailed monthly providing a summary usage in the PIRG compute (SU) and storage consumption. Note: charge back is suspended until further notice

Reservations

slurm reservations will ensure resources are available on the cluster for the class at a given time. Useful during:

  • lecture for live coding examples where students are expected to follow along

  • lab when students to have a dedicated time to work

Reservation Behaviors worth noting:

  1. Jobs that do not specify the correct partition containing the allocated nodes in the reservation will queue (PD) until killed when the reservation ends or are deleted by the user

  2. Jobs submitted to the reservation before the StartTime will fail with a clear message in OOD, “requested reservation is invalid”

  3. Jobs requesting more cores than the reservation provides fail with a clear error message in OOD

  4. Jobs requesting  more memory than the reservation provides will queue (PD) until killed when the reservation ends or deleted by the user

    1. Other jobs requesting memory available in the reservation are launched successfully

  5. Jobs are launched successfully even when requesting more time than reservation duration

  6. Jobs are killed once the reservation ends

 Behaviors 1 and 4 are troublesome because OOD does not display the reason the job is queued. In a terminal window the command squeue will report the status of the queue.

Student data

Data on Talapas does not have a backup copy. Data is retained for 90 days after the end of the term unless otherwise instructed.

  • No labels