6 Commits

Include renames

Author	SHA1	Message	Date
Tom Wilkie	4e29dba5cd	Make Gossip DNS reject gossip messages if clockskew > tombstoneTimeout / 2	2015-07-20 13:12:07 +00:00
Tom Wilkie	1a4b38a10c	Don't delete all the non-tombstone entries every 10mins!	2015-07-20 12:03:46 +00:00
Matthias Radestock	66473e6021	refactor: return slice instead of pointer to slice from tombstone()	2015-07-20 12:37:54 +01:00
Tom Wilkie	66e58937ca	Make nameserver.checkAndPanic look for dups, call it more often.	2015-07-17 10:19:25 +00:00
Tom Wilkie	73210b6a70	Make sure DNS Gossip converges correctly. ... - Abide by gossip interface (return nil, not empty gossip) so gossip converges! - Make sure we don't say an old entry version is new to us; add some more tests. - Add dns test for 3 (or N) hosts - Extend mock gossip router to ensure reconsumption off diffs yield nil - Don't increment version when re-adding existing entry.	2015-07-15 15:54:52 +00:00
Tom Wilkie	8b061fd555	Gossip-based DNS embedded in the router. ... - Nameserver holds a sorted list of (hostname, peer, container id, ip) tuples. - Entries are gossiped using topology gossip / broadcast - only new/updated entries are propogated as expected. - Entries for a given peer are removed when the connection to the peer is lost. - Entries are tombstoned when containers die. Tombstones are kept for 10mins, as they do not need to survive partition, only gossip propagation delay.	2015-07-14 16:00:38 +00:00