Bug #13674
[crunch-dispatch-slurm] Use hash instead of array for InstanceTypes config
Start date:
Due date:
% Done:
0%
Estimated time:
Story points:
-
Release:
Release relationship:
Auto
Description
Catch up with change to Cluster configuration.
A hash is more ops-friendly (notably it accommodates storing the whole config natively in consul's kv store using keys like "InstanceTypes/m1.large/price") and aligns with the existing Nodemanager config format. It also makes it more obvious that the instance type name has to be unique.
During a transition period programs that read the cluster config file should accommodate both array and hash forms, so ops can migrate their config files without stopping the world.
Related issues
History
#1
Updated by Tom Clegg almost 4 years ago
- Related to Story #13648: [Epic] Use one cluster configuration file for all components added
#2
Updated by Tom Clegg almost 4 years ago
- Description updated (diff)
#3
Updated by Tom Clegg almost 4 years ago
- Status changed from New to In Progress
- Target version set to 2018-07-03 Sprint
13674-instance-types-hash @ 3ad42202c5e073c5b90383c8aa1075e8056ff1d9
- changes config from array to hash
- Go progs can still read config file that uses array form
#4
Updated by Tom Clegg almost 4 years ago
- Related to Feature #13611: Nodemanager reads instance sizes from the system config file to avoid duplication added
#5
Updated by Tom Clegg almost 4 years ago
- Related to deleted (Feature #13611: Nodemanager reads instance sizes from the system config file to avoid duplication)
#6
Updated by Tom Clegg almost 4 years ago
- Blocks Feature #13611: Nodemanager reads instance sizes from the system config file to avoid duplication added
#7
Updated by Tom Clegg almost 4 years ago
- Status changed from In Progress to Resolved
- Assigned To set to Tom Clegg
#8
Updated by Tom Morris almost 4 years ago
- Release set to 13