mDNS autoclustering #1
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Max Asnaashari <max.asnaashari@canonical.com>
Signed-off-by: Max Asnaashari <max.asnaashari@canonical.com>
Signed-off-by: Max Asnaashari <max.asnaashari@canonical.com>
|
@stgraber canonical/microcluster#37 should probably be merged first, as it might cause problems for larger clusters. |
|
Merging this as-is. I'll add the initial snap packaging and do some tests on this one later. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds a basic CLI (from microcluster) and adds hooks for auto-clustering.
When starting a daemon, we simultaneously broadcast our expected cluster address and name, while searching for join tokens from another potential peer. When we find a matching join token, we stop the mdns lookup/broadcast and join the cluster.
When bootstrapping, we will collect any currently available mdns records and create join tokens. We will then initiate a new broadcast with a map of tokens by cluster name. After 30 seconds, we will stop broadcasting this message.
Currently there's a hard limit of 30 cluster members per broadcast loop. This is because the mdns lookup uses a channel that requires a specified length for collecting results. I'll try to see if I can make this behave a bit nicer.