5a8cfd6e06d4ee7f47c5926c3859cbd6161c0d1a
4 Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
Maria Malyarova
|
008a037a36 |
Another amendment with missing parenthesis
TrivialFix Change-Id: Id44ae27bc39ea97be9eb092f8a99a06056b86392 |
||
|
Nguyen Hung Phuong
|
59bbe27fb0 |
Fix typos in Swift files
Change-Id: I34e0c9a888127704ac1910e73ddd14e27ebade13 |
||
|
Cedric Dos Santos
|
a8751ae557 |
Correct misspelled words
In some files I found misspelling words. bin/swift-reconciler-enqueue#l26 primarly => primarily swift/account/backend.py#l309 ommited => omitted swift/container/replicator.py#l158 successfull => successful test/unit/account/test_backend.py#1450 non_existant_policy_index => non_existent_policy_index test/unit/account/test_backend.py#1451 'test-non-existant-policy'=> 'test-non-existent-policy' test/unit/account/test_backend.py#1453 non_existant_policy_index => non_existent_policy_index Change-Id: I976236e3200a6fbdc20be464acff182b6cface81 |
||
|
Clay Gerrard
|
3fc4d6f91d |
Add container-reconciler daemon
This daemon will take objects that are in the wrong storage policy and move them to the right ones, or delete requests that went to the wrong storage policy and apply them to the right ones. It operates on a queue similar to the object-expirer's queue. Discovering that the object is in the wrong policy will be done in subsequent commits by the container replicator; this is the daemon that handles them once they happen. Like the object expirer, you only need to run one of these per cluster see etc/container-reconciler.conf. DocImpact Implements: blueprint storage-policies Change-Id: I5ea62eb77ddcbc7cfebf903429f2ee4c098771c9 |