Skip to content

You can submit ordinary Slurm batch scripts to run on cloud machines. projectEureka starts the machines for each job, tracks their estimated cost under the project, and removes them when the job ends.

  • You are a member of the project.
  • Slurm commands work on the login node only. Open Terminal in the project side bar: it opens a shell on the login node in a new browser tab. Slurm commands are not available inside desktop or app sessions.
  1. In the Terminal, write a batch script with #SBATCH lines, for example job.sh.
  2. Submit it with sbatch -p <project> job.sh. The partition (-p) names the projectEureka project the job runs in. -A <project> also works when no partition is set. srun submits one job and waits for it. ccqsub is also accepted.
  3. Follow it with squeue, scontrol show job <id>, sacct, and sinfo. Cancel it with scancel <id>. squeue, sbatch, scancel, sacct, and sinfo are login-node Slurm commands. They are not eureka subcommands.
  4. With no -o, output goes to slurm-<job id>.out in the folder you submitted from.
  • A single-node job runs on its own machine. Multi-node, MPI, and array jobs run in a small Slurm cluster started for that job.
  • -c, --mem, and --gres/--gpus choose the machine size.
  • -t sets the run time limit. A value above the project max is rejected. With no -t, the project or system default applies. At the limit the job is stopped and shows TIMEOUT. See Set time limits.
  • A job that exits with a nonzero code shows Failed.
  • While an admin is pausing the environment, a queued job shows Held: environment paused. If the admin kept the queue held after resume, it shows Held (kept after resume) until an admin releases it. The Jobs page has no Held filter: held jobs stay in Active with that Held: … state. Paused launcher sessions are listed on Launchers > Paused. See Pause and resume the environment.
  • A job runs as the person who submitted it, even when the project has a project user.
  • Nodes shown in sinfo is set in Project Settings.

Jobs in the side bar lists jobs in the project, in Table View or List View. The table shows user, name, id, type, state, start time, duration, nodes, cores, GPUs, memory, and project. Choose My Active Jobs or My Completed Jobs. Project Owners and system admins can also choose All Active Jobs and All Completed Jobs. There is no Held filter.

Google Cloud

Jobs page in Table View with My Active Jobs, listing a job's user, name, type, state, start time, duration, nodes, cores, memory, and project

Set time limits · How costs are tracked · How projectEureka works