Skip to content
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

Include host scope for container joins based on IP. #577

Merged
merged 3 commits into from
Oct 21, 2015
Merged

Conversation

tomwilkie
Copy link
Contributor

Part of #520 - can explain false edges between containers on different hosts, but the bug has been seen between containers on the same host, and this shouldn't affect that.

@tomwilkie tomwilkie force-pushed the 520-edge-bug branch 3 times, most recently from 2f90fbc to f0fb6e3 Compare October 20, 2015 15:27
c.RLock()
defer c.RUnlock()

ips := append(c.container.NetworkSettings.SecondaryIPAddresses,
c.container.NetworkSettings.IPAddress)

This comment was marked as abuse.

@peterbourgon
Copy link
Contributor

LGTM.

@tomwilkie
Copy link
Contributor Author

Crap; there is actually a good reason not to use the id generators - they embed the logic for whether a scope is appended or not, and really are only for use within the probe.

Lets see if we can factor this out.

@tomwilkie
Copy link
Contributor Author

MakeEndpointNodeIDAlwaysWithScope seems a little verbose; any better suggestions?

@peterbourgon
Copy link
Contributor

MakeScopedEndpointNodeID

or the general form

Make [Scoped] Topology Node ID

@tomwilkie
Copy link
Contributor Author

Okay done. Hopefully this should all pass now.

tomwilkie added a commit that referenced this pull request Oct 21, 2015
Include host scope for container joins based on IP.
@tomwilkie tomwilkie merged commit 1e22629 into master Oct 21, 2015
@tomwilkie tomwilkie deleted the 520-edge-bug branch October 21, 2015 10:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants