Project

General

Profile

Actions
Copy link

Bug #8817

closed

[API] Review the semantic of max_compute_nodes and slurm configuration

Added by Nico César almost 10 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
-
Story points:
-

Description

#8758 revealed that max_compute_nodes in application.yml (API server) can be misaligned with NodeName=compute[0-XX] in the slurm configuration.

We should reach a consensus to have a unique number to make it easier for the SysAdmin work.

Actions
Copy link
 #1

Updated by Brett Smith almost 10 years ago

Nico Cesar wrote:

We should reach a consensus to have a unique number to make it easier for the SysAdmin work.

Sorry, I'm not sure I know what you mean by "unique number."

Looking ahead to Crunch v2 a bit--I don't think we can teach SLURM to read the API server's configuration. We could maybe teach API server to figure out the available node numbers by reading the SLURM configuration, but I'm gonna be a little hesitant to do that until we're a little further along with Crunch v2 and know more about how we want to integrate with existing SLURM configurations.

Actions
Copy link
 #2

Updated by Peter Amstutz about 6 years ago

  • Status changed from New to Closed
Actions
Copy link

Also available in: Atom PDF