Bootstrap automatically using shared secret #35
Labels
No labels
action
check-aws
action
discussion-needed
action
for-external-contributors
action
for-newcomers
action
more-info-needed
action
need-funding
action
triage-required
kind
correctness
kind
ideas
kind
improvement
kind
performance
kind
testing
kind
usability
kind
wrong-behavior
prio
critical
prio
low
scope
admin-api
scope
background-healing
scope
build
scope
documentation
scope
k8s
scope
layout
scope
metadata
scope
ops
scope
rpc
scope
s3-api
scope
security
scope
telemetry
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#35
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Use a shared secret and (a DHT / something??), instead of relying on Consul or fixed boostrap addresses.
Better node discovery between garage nodesto Bootstrap automatically using shared secretShould we close this issue?
Not sure. Basically the idea of this issue is to make Garage run automatically on any kind of network and not need the administrator to manage connections between nodes. It could work like Syncthing: just copy-paste a node ID into another node, and the two nodes will manage to do NAT traversal and other stuff to manage to connect to one another. In the case of Garage, nodes could just know the shared secret (= rpc_secret), and from there have a signaling mechanism to find other nodes of the cluster and automatically connect. However the mechanism in Syncthing uses a centralized bootstrap server to find other nodes, not sure we want to do that.