Project

General

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 6 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Normal
Assigned To:
-
Category:
Node Manager
Target version:
-
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

Related to Arvados - Idea #13569: Add units tera / giga / mega / kilo for configurationsResolvedTom Clegg06/29/2018Actions
Related to Arvados - Idea #13648: [Epic] Use one cluster configuration file for all componentsResolvedActions
Blocked by Arvados - Bug #13674: [crunch-dispatch-slurm] Use hash instead of array for InstanceTypes configResolvedTom CleggActions
Blocked by Arvados - Idea #13731: Design new nodemanager config data organization for cluster-wide configClosed08/13/2018Actions
Actions
Copy link
 #1

Updated by Peter Amstutz almost 6 years ago

  • Description updated (diff)
Actions
Copy link
 #2

Updated by Lucas Di Pentima almost 6 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
 #3

Updated by Lucas Di Pentima almost 6 years ago

  • Related to Idea #13569: Add units tera / giga / mega / kilo for configurations added
Actions
Copy link
 #4

Updated by Tom Morris almost 6 years ago

  • Story points set to 2.0
Actions
Copy link
 #5

Updated by Tom Clegg almost 6 years ago

  • Related to Idea #13648: [Epic] Use one cluster configuration file for all components added
Actions
Copy link
 #6

Updated by Tom Clegg almost 6 years ago

  • Related to Bug #13674: [crunch-dispatch-slurm] Use hash instead of array for InstanceTypes config added
Actions
Copy link
 #7

Updated by Tom Clegg almost 6 years ago

  • Related to deleted (Bug #13674: [crunch-dispatch-slurm] Use hash instead of array for InstanceTypes config)
Actions
Copy link
 #8

Updated by Tom Clegg almost 6 years ago

  • Blocked by Bug #13674: [crunch-dispatch-slurm] Use hash instead of array for InstanceTypes config added
Actions
Copy link
 #9

Updated by Tom Morris almost 6 years ago

  • Target version changed from To Be Groomed to Arvados Future Sprints
Actions
Copy link
 #10

Updated by Tom Clegg almost 6 years ago

  • Blocked by Idea #13731: Design new nodemanager config data organization for cluster-wide config added
Actions
Copy link
 #11

Updated by Peter Amstutz over 4 years ago

  • Status changed from New to Closed
Actions
Copy link
 #12

Updated by Ward Vandewege almost 3 years ago

  • Target version deleted (Arvados Future Sprints)
Actions
Copy link

Also available in: Atom PDF