Story #18256

Design bottom-up configuration/discovery strategy

Added by Peter Amstutz about 2 months ago. Updated about 2 months ago.

Assigned To:
Target version:
Start date:
Due date:
% Done:


Estimated time:
Story points:


  • Investigate orchestration

Certain configuration steps have dependencies on configuration of other nodes, which requires orchestration rather than just top-down configuration.

e.g. need to know how to contact postgres

Javier: want bottom-up configuration, when services come up they contact the configuration server (consul?) to get the configuration & update the service entry.

Tom: "join" command (state?) to add a service to Arvados

Use pre-shared key / token for machines to identify themselves. Or nodes generate their own random ID and there's an approval step.

Tom: would be cool if nodes can self-configure which services they run

"Join" state gets a list of services that node with this unique ID should be running, can be changed on the fly.

Stephen: could have a discovery mode

Ward: restrict to private network

Javier: Controller should hold the central configuration


#1 Updated by Peter Amstutz about 2 months ago

  • Description updated (diff)

#2 Updated by Peter Amstutz about 2 months ago

  • Description updated (diff)
  • Subject changed from Better provision script to Design bottom-up configuration/discovery strategy

Also available in: Atom PDF