Project

General

Profile

Actions

Feature #5926

closed

[API] MAX_SLOTS should be a configuration value (app/models/node.rb)

Added by Ward Vandewege almost 9 years ago. Updated almost 9 years ago.

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

Subtasks 1 (0 open1 closed)

Task #5929: review 5926-parameterize-max-slotsResolvedTom Clegg05/06/2015Actions
Actions #1

Updated by Ward Vandewege almost 9 years ago

  • Status changed from New to In Progress
  • Story points set to 0.5
Actions #2

Updated by Ward Vandewege almost 9 years ago

  • Assigned To set to Ward Vandewege
Actions #3

Updated by Tom Clegg almost 9 years ago

at 0358074

Might be worth mentioning in config comment something like: "After this limit is reduced, any existing nodes with slot number >= new limit will not be counted against the new limit. IOW, the new limit won't be strictly enforced until those higher-numbered nodes go down."

I think it would be simpler (and better for testing) to use Rails.configuration.max_compute_nodes twice instead of copying it to a class variable and using that twice. But LGTM either way. Thanks.

Actions #4

Updated by Ward Vandewege almost 9 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 0 to 100

Applied in changeset arvados|commit:e7e61999bf577b3ba5308c747dda4a0011516aa7.

Actions

Also available in: Atom PDF