Project

General

Profile

Actions

Bug #13674

closed

[crunch-dispatch-slurm] Use hash instead of array for InstanceTypes config

Added by Tom Clegg over 6 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
-
Target version:
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 2 (0 open2 closed)

Related to Arvados - Idea #13648: [Epic] Use one cluster configuration file for all componentsResolvedActions
Blocks Arvados - Feature #13611: Nodemanager reads instance sizes from the system config file to avoid duplicationClosedActions
Actions

Also available in: Atom PDF