Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • ONT_pilot_gitlab ONT_pilot_gitlab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 13
    • Issues 13
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Wiki
    • Wiki
  • External wiki
    • External wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ESB
  • ONT_pilot_gitlabONT_pilot_gitlab
  • Issues
  • #100

Closed
Open
Created Oct 25, 2020 by Cedric Laczny@cedric.lacznyOwner

Rewriting of slurm.yaml files to match new UL HPC SLURM configurations

The master document, in some way: https://hpc.uni.lu/download/slides/2020-ULHPC-user-guide.pdf

The partitions can stay as they are, but the qos need to be adjusted accordingly 😞 The rules with a walltime > 02-00:00:00 will need to be moved to qos: long. What is yet a bit unclear to me, is how many long jobs can be launched per user. According to the master document, it would be only a single one 😱

A quick look revealed assembly_lr_canu to be the only affected rule - at least in the master branch.

Assignee
Assign to
Time tracking