Fix swiftdir option and usage of storage policy aliases
If swift-recon/swift-get-nodes/swift-object-info is used with the
swiftdir option they will read rings from the given directory; however
they are still using /etc/swift/swift.conf to find the policies on the
current node.
This makes it impossible to maintain a local swift.conf copy (if you
don't have write access to /etc/swift) or check multiple clusters from
the same node.
Until now swift-recon was also not usable with storage policy aliases,
this patch fixes this as well.
Reviewed: https:/ /review. openstack. org/344693 /git.openstack. org/cgit/ openstack/ swift/commit/ ?id=2410b616bba 2d68914c2c00e95 b2f7c30f391e1b
Committed: https:/
Submitter: Jenkins
Branch: master
commit 2410b616bba2d68 914c2c00e95b2f7 c30f391e1b
Author: Christian Schwede <email address hidden>
Date: Wed Jul 20 09:51:24 2016 +0000
Fix swiftdir option and usage of storage policy aliases
If swift-recon/ swift-get- nodes/swift- object- info is used with the swift.conf to find the policies on the
swiftdir option they will read rings from the given directory; however
they are still using /etc/swift/
current node.
This makes it impossible to maintain a local swift.conf copy (if you
don't have write access to /etc/swift) or check multiple clusters from
the same node.
Until now swift-recon was also not usable with storage policy aliases,
this patch fixes this as well.
Closes-Bug: 1577582 2e4420739eacd1e 5b454af2ae3
Closes-Bug: 1604707
Closes-Bug: 1617951
Co-Authored-By: Alistair Coles <email address hidden>
Co-Authored-By: Thiago da Silva <email address hidden>
Change-Id: I13188d42ec19e3