Clay Gerrard b19dc1ddec Always fix devices with multiple part-replica assignments ... I've found that given a sufficiently bad replica2part2dev table we can accidently not entirely fix palcement when more than two replicas of a part are assigned to the duplicate devices. It shows up most on > 3 replica rings when you have two *different* devices both holding two replicas. But you can see it on a three replica ring when all three replicas are assigned to the same device. Change-Id: Ieb213c1a259815a2ed657291242919cda568c7b5		2016-02-01 16:19:08 -08:00
..
account	Modify functional tests to use ostestr/testr	2015-12-15 22:30:44 +00:00
cli	Renamed variable for better code readability	2016-01-29 22:49:16 +01:00
common	Always fix devices with multiple part-replica assignments	2016-02-01 16:19:08 -08:00
container	Container-Sync to iterate only over synced containers	2016-01-06 16:46:31 +02:00
obj	Merge "Validate X-Timestamps"	2016-01-22 05:50:01 +00:00
proxy	Merge "Remove a print statement from tests"	2016-01-28 02:37:15 +00:00
test_locale	monkeypatch thread for keystoneclient	2015-11-03 16:36:19 +01:00
__init__.py	Deleted comment about part power in FakeRing	2016-01-19 20:01:08 +00:00