Project

General

Custom queries

Profile

Actions
Copy link

Feature #13611

closed

Nodemanager reads instance sizes from the system config file to avoid duplication

Added by Lucas Di Pentima almost 7 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assigned To:
-
Category:
Node Manager
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Story points:
2.0

Description

Both crunch-dispatch-slurm and nodemanager need to a list of configured node sizes. Currently, this information is duplicated in both the nodemanager config file as the master arvados config.yml. To eliminate duplication nodemanager should read the node size configurations, and possibly the rest of its configuration, from the master arvados config.yml.

Related issues 4 (0 open — 4 closed)

Related to Arvados - Story #13569: Add units tera / giga / mega / kilo for configurationsResolvedTom Clegg06/29/2018

Actions
Related to Arvados - Story #13648: [Epic] Use one cluster configuration file for all componentsResolved

Actions
Blocked by Arvados - Bug #13674: [crunch-dispatch-slurm] Use hash instead of array for InstanceTypes configResolvedTom Clegg

Actions
Blocked by Arvados - Story #13731: Design new nodemanager config data organization for cluster-wide configClosed08/13/2018

Actions
Actions
Copy link
 #2

Updated by Lucas Di Pentima almost 7 years ago

  • As described on https://dev.arvados.org/projects/arvados/wiki/Cluster_configuration, ProviderType attribute would be the same as the newly implemented instance_type on nodemanager. I think neither GoSDK nor dispatchcloud need to know about it, at least for now as the only user would be nodemanager.
  • Reading nodemanager’s cloud sizes from config.yml seems to be pretty straightforward.
  • Should we add a section about nodemanager’s specific configs on this story or leave that for another?
    • Cloud settings & credentials.
    • Daemon values (max nodes, poll time, dispatcher, etc).
    • Logging levels.
  • If going the hybrid path of having nodemanager’s config temporarily spread in 2 configuration files, should we ignore arvados-node-manager.ini’s cloud sizes?
  • Update nodemanager docs, possibly adding a migration guide.
Actions
Copy link

Also available in: Atom PDF