-
Notifications
You must be signed in to change notification settings - Fork 712
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
Tag containers with WeaveDNS hostnames. #394
Conversation
c0352a9
to
2623670
Compare
@@ -26,27 +29,37 @@ const ( | |||
// overlay -- though I'm not sure what that would look like in practice right | |||
// now. | |||
type Weave struct { | |||
url string | |||
url string | |||
scope string |
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
2623670
to
5a86014
Compare
@peterbourgon PTAL |
if entry.Tombstone > 0 { | ||
continue | ||
} | ||
nodeid := report.MakeContainerNodeID(w.hostID, entry.ContainerID) |
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
Are we sure it's OK to make an HTTP call from the probe to the Weave router with every Tag and Report, i.e. once per publish interval? |
5a86014
to
e9fad61
Compare
Yes I'm pretty confident this is safe; everything we're querying is in memory, and the weave routers deals with many more QPS on other interfaces (ie DNS). Lets put it another way: I'm more confident this is safe than the amount of queries we do on the docker daemon! |
👍 |
Tag containers with WeaveDNS hostnames.
No description provided.