e79162423f
When Swift multi-tenant store is used along with the scheme ``swift+config`` (the scheme that identifies the need to use the swift config), a reference to use swift objects from the swift config file set using the option ``swift_store_config_file`` is made resulting in the storage url for an accessible object being created from a swift auth_address. So is the case when the scheme is ``swift``. This behavior is suitable for single-tenant swift store and not multi-tenant store. The solution is to ensure that if deploying multi-tenant swift store, prohibit setting of swift_store_config_file. This patch does this by ensuring that multi-tenant and swift_store_config_file are not configured to work together. TODO: When somebody changes to multi-tenant from single-tenant store, and they were using the swift config for single-tenant, the operator will not be able to access those images any longer. Logic to ensure that multi-tenant uses the swift conf file if there is a need to access an image that was created using single-tenant and swift+config could be introduced. UpgradeImpact DocImpact Closes-Bug: 1625075 Change-Id: I8b5c31541d3c501ad7c2520b463f881599f4a28e Co-Authored-By: Hemanth Makkapati <hemanth.makkapati@rackspace.com> Co-Authored-By: Dharini Chandrasekar <dharini.chandrasekar@intel.com> |
||
|---|---|---|
| .. | ||
| etc | ||
| functional | ||
| unit | ||
| __init__.py | ||
| base.py | ||
| fakes.py | ||
| utils.py | ||