Project

General

Profile

Actions
Copy link

Story #18685

open

Synchronize configuration on multi-node cluster

Added by Peter Amstutz about 3 years ago. Updated about 2 years ago.

Status:
New
Priority:
Normal
Assigned To:
-
Target version:
-
Start date:
10/01/2022
Due date:
03/31/2023 (about 23 months late)
% Done:

0%

Estimated time:
Story points:
-
Release:
Postponed
Release relationship:
Auto

Description

Proposed command

"arvados-server push-config" which copies the config file to all the system nodes and restarts services.

Could also have a "arvados-server edit-config" which gets the config and then opens and editor and lets you make changes & pushes it after you save and exit.

  • Must have the ability to contact all the nodes

Related issues 6 (3 open — 3 closed)

Related to Arvados Epics - Story #18727: Avoid configuration skew between different services and hostsResolved03/01/202205/31/2022

Actions
Related to Arvados - Feature #19377: [diagnostics] show health-check responseResolvedTom Clegg10/05/2022

Actions
Related to Arvados - Bug #19215: improve multi-node installer experienceResolvedPeter Amstutz06/28/2022

Actions
Related to Arvados - Feature #19564: AutoReloadConfig usable in productionIn ProgressTom Clegg

Actions
Related to Arvados - Feature #19593: Ability to deploy the same arvados-server package to all nodes, all nodes can handle certain types of requestsNew

Actions
Related to Arvados Epics - Story #18337: Easy install via OS packageIn Progress12/01/202203/31/2023

Actions
Actions
Copy link
 #1

Updated by Tom Clegg about 3 years ago

  • Related to Story #18727: Avoid configuration skew between different services and hosts added
Actions
Copy link
 #2

Updated by Peter Amstutz about 3 years ago

  • Due date set to 08/31/2022
  • Start date set to 06/01/2022
Actions
Copy link
 #3

Updated by Peter Amstutz almost 3 years ago

  • Start date changed from 06/01/2022 to 05/01/2022
Actions
Copy link
 #4

Updated by Peter Amstutz almost 3 years ago

  • Due date changed from 08/31/2022 to 10/31/2022
  • Start date changed from 05/01/2022 to 07/01/2022
Actions
Copy link
 #5

Updated by Peter Amstutz over 2 years ago

  • Due date changed from 10/31/2022 to 12/31/2022
  • Start date changed from 07/01/2022 to 09/01/2022
Actions
Copy link
 #6

Updated by Peter Amstutz over 2 years ago

  • Due date changed from 12/31/2022 to 03/31/2023
  • Start date changed from 09/01/2022 to 12/01/2022
Actions
Copy link
 #7

Updated by Peter Amstutz over 2 years ago

  • Related to Feature #19377: [diagnostics] show health-check response added
Actions
Copy link
 #8

Updated by Peter Amstutz over 2 years ago

  • Start date changed from 12/01/2022 to 10/01/2022
Actions
Copy link
 #9

Updated by Peter Amstutz over 2 years ago

  • Related to Bug #19215: improve multi-node installer experience added
Actions
Copy link
 #10

Updated by Peter Amstutz over 2 years ago

  • Description updated (diff)
Actions
Copy link
 #11

Updated by Peter Amstutz over 2 years ago

  • Description updated (diff)
Actions
Copy link
 #12

Updated by Peter Amstutz over 2 years ago

  • Related to Feature #19564: AutoReloadConfig usable in production added
Actions
Copy link
 #13

Updated by Peter Amstutz over 2 years ago

  • Related to Feature #19593: Ability to deploy the same arvados-server package to all nodes, all nodes can handle certain types of requests added
Actions
Copy link
 #14

Updated by Tom Clegg over 2 years ago

  • Related to Story #18337: Easy install via OS package added
Actions
Copy link
 #15

Updated by Lucas Di Pentima about 2 years ago

  • Release set to 60
Actions
Copy link

Also available in: Atom PDF