forked from dcos/dcos-net
-
Notifications
You must be signed in to change notification settings - Fork 0
Merge with main #1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
This file contains hidden or 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
IPSet Netlink Protocol splits big sets into several netlink messages. First message contains all metadata about a set, but just a part of all entries. Following messages contains only remaining entries.
Add support for big sets in the ipset mgr.
Bump Lashup
Move from Lager to Logger
Leverage exponential backoff with requests to Mesos
Add syntax_tools, compiler, and backoff as runtime deps
Mesos listener is honest now again when asked if it is a leader or not
Wait till agents become active before fanning out Mesos tasks
Bump Lashup
Task update leads to two DNS zone updates
DC/OS overlay networks should be compared by-value
Remove support for set mode from dcos dns
Move common logic from dcos_net_mesos to new behavior, so it can be re-used in l4lb later.
L4lb manager receives update from mesos leader. Load balancer doesn't have to check reachability of nodes because it always have consistent state.
Operator Streaming API in L4LB
Codified networking run book
Also, - make the script compatible with DC/OS >= 2.0 - fix indentation - make it use jq only if it is available
Save netstat output
Wrap the "main" logic into a `main` function that allows for easier use via `curl <url> | bash` should a user desire to do so.
Revert "Merge pull request #189 from dcos/urbanserj/l4lb"
Make runbook a bit more sysadmin friendly
Instead of staticly setting the weight to `1` always, set it only to `1` when in a `running` state. `killing` and any other state will be set to `0` to prevent new connections from being sent to the backend, but still allow existing connections through.
When a task is unhealthy, we should not sever conenctions by removing it from the VIP. Instead set the weight to 0 to prevent new connections, while allowing existing connections.
Handle TASK_KILLING state for loadbalancing
Adds testing that the different backend selection and manupulation functions work with and without the weight being specified. Confirms that if an agent populates a VIP using the old code that the new code won't crash.
Fwd vip weight regression
Since the network runbook can be used as a lite "bundle" capture more data.
runbook: capture more data
runbook: capture vxlan state and nclock
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.
No description provided.