Project

General

Profile

Actions

Feature #19593

open

Ability to deploy the same arvados-server package to all nodes, all nodes can handle certain types of requests

Added by Peter Amstutz over 1 year ago. Updated about 2 months ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
Deployment
Target version:
Story points:
-
Release:
Release relationship:
Auto

Description

Nodes should register with a central (something) for service discovery.

Assuming the database is visible to all nodes, all nodes should be able to handle controller/API requests.

Assuming the keep storage (S3 or filesystem) is visible to all nodes, all nodes should be able to handle Keep requests

Workbench / workbench 2 are available on all nodes.

Need a solution to collect logs centrally so that debugging isn't impossible.

Services that are stateful / must not run more than one instance at a time:

  • arvados-dispatch-cloud
  • keep-balance
  • git server (should be deprecated & removed)
  • webshell?

Related issues

Related to Arvados Epics - Idea #18685: Synchronize configuration on multi-node clusterNewActions
Actions #1

Updated by Peter Amstutz over 1 year ago

  • Description updated (diff)
  • Subject changed from Ability to deploy the same arvados-server package to all nodes, and use arvados config to control which services are run to Ability to deploy the same arvados-server package to all nodes, all nodes can handle certain types of requests
Actions #2

Updated by Peter Amstutz over 1 year ago

  • Related to Idea #18685: Synchronize configuration on multi-node cluster added
Actions #3

Updated by Peter Amstutz about 1 year ago

  • Release set to 60
Actions #4

Updated by Peter Amstutz about 2 months ago

  • Target version set to Future
Actions

Also available in: Atom PDF