Project

General

Profile

Actions

Idea #18685

open

Synchronize configuration on multi-node cluster

Added by Peter Amstutz almost 3 years ago. Updated 10 months ago.

Status:
New
Priority:
Normal
Assigned To:
-
Target version:
Start date:
Due date:
Story points:
-
Release:
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 open3 closed)

Related to Arvados Epics - Idea #18727: Avoid configuration skew between different services and hostsResolved03/01/202205/31/2022Actions
Related to Arvados - Feature #19377: [diagnostics] show health-check responseResolvedTom Clegg10/05/2022Actions
Related to Arvados - Bug #19215: improve multi-node installer experienceResolvedPeter Amstutz06/28/2022Actions
Related to Arvados - Feature #19564: AutoReloadConfig usable in productionIn ProgressTom CleggActions
Related to Arvados - Feature #19593: Ability to deploy the same arvados-server package to all nodes, all nodes can handle certain types of requestsNewActions
Related to Arvados Epics - Idea #18337: Easy entry into Arvados ecosystemNew01/01/202506/30/2025Actions
Actions #1

Updated by Tom Clegg almost 3 years ago

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

Updated by Peter Amstutz almost 3 years ago

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

Updated by Peter Amstutz almost 3 years ago

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

Updated by Peter Amstutz over 2 years ago

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

Updated by Peter Amstutz over 2 years ago

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

Updated by Peter Amstutz over 2 years ago

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

Updated by Peter Amstutz about 2 years ago

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

Updated by Peter Amstutz about 2 years ago

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

Updated by Peter Amstutz about 2 years ago

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

Updated by Peter Amstutz about 2 years ago

  • Description updated (diff)
Actions #11

Updated by Peter Amstutz about 2 years ago

  • Description updated (diff)
Actions #12

Updated by Peter Amstutz about 2 years ago

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

Updated by Peter Amstutz about 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 #14

Updated by Tom Clegg about 2 years ago

  • Related to Idea #18337: Easy entry into Arvados ecosystem added
Actions #15

Updated by Peter Amstutz almost 2 years ago

  • Start date changed from 10/01/2022 to 09/01/2023
  • Due date changed from 03/31/2023 to 12/31/2023
Actions #16

Updated by Peter Amstutz almost 2 years ago

  • Release set to 60
Actions #17

Updated by Peter Amstutz over 1 year ago

  • Start date changed from 09/01/2023 to 12/31/2023
  • Due date changed from 12/31/2023 to 03/31/2024
Actions #18

Updated by Peter Amstutz 12 months ago

  • Start date changed from 12/31/2023 to 01/31/2025
  • Due date changed from 03/31/2024 to 03/31/2025
Actions #19

Updated by Peter Amstutz 10 months ago

  • Target version set to Future
Actions #20

Updated by Peter Amstutz 10 months ago

  • Release changed from 60 to 28
Actions

Also available in: Atom PDF