Bryan Boreham d2f0287fa3 Handle range wrap-around when checking for allocations ...

Ring wraps around at zero but Space doesn't know about this, so we
have to normalise ranges coming out of Ring.  In turn we may need to
split one range into two, across the end of the Ring.

2019-10-10 11:14:41 +00:00

..

paxos

Initialize Paxos quorum to 0 until this node needs to request consensus.

2016-04-11 11:42:24 +01:00

ring

Handle range wrap-around when checking for allocations

2019-10-10 11:14:41 +00:00

space

Clean up some tests that were not checking results

2017-03-21 11:38:35 +00:00

tracker

Export tracker.RemoveCommon and tracker.Merge

2018-06-04 14:08:24 +02:00

allocate.go

Add explanations of various claim and allocation fields

2017-02-13 17:31:02 +00:00

allocator_test.go

Don't use '_' as container ID in claim outside range

2017-06-07 16:38:19 +00:00

allocator.go

Handle range wrap-around when checking for allocations

2019-10-10 11:14:41 +00:00

claim.go

Check who previously owned an address claimed outside the range

2017-06-08 16:25:09 +00:00

http_test.go

Extern LocalRangeTracker interface with String method

2018-06-04 14:08:24 +02:00

http.go

ipam: Do not deref nil in GET /ipinfo/tracker if tracker doesn't exist

2018-09-21 13:29:03 +03:00

prime.go

Rename consense -> prime

2016-04-14 12:46:03 +01:00

status.go

Report count of active IP addresses in status

2016-10-20 14:04:41 +01:00

testutils_test.go

Fix invalid format in ipam/testutils_test.go

2018-03-12 11:04:41 +00:00