diff options
| author | Dharini Chandrasekar <dharini.chandrasekar@intel.com> | 2016-10-20 00:00:19 +0000 |
|---|---|---|
| committer | Dharini Chandrasekar <dharini.chandrasekar@intel.com> | 2016-12-16 19:48:09 +0000 |
| commit | e79162423f4855c4bea601ec3e2175fd984a54ad (patch) | |
| tree | 47586ced283a8389f988a9610b1bf468458f6534 /releasenotes | |
| parent | 9b63cb5d00b26b6d8bf105ae306094775cacd8dc (diff) | |
| download | glance_store-e79162423f4855c4bea601ec3e2175fd984a54ad.tar.gz | |
Raise exc when using multi-tenant and swift+config
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>
Diffstat (limited to 'releasenotes')
| -rw-r--r-- | releasenotes/notes/multi-tenant-store-058b67ce5b7f3bd0.yaml | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/releasenotes/notes/multi-tenant-store-058b67ce5b7f3bd0.yaml b/releasenotes/notes/multi-tenant-store-058b67ce5b7f3bd0.yaml new file mode 100644 index 0000000..4d00269 --- /dev/null +++ b/releasenotes/notes/multi-tenant-store-058b67ce5b7f3bd0.yaml @@ -0,0 +1,9 @@ +--- +upgrade: + - If using Swift in the multi-tenant mode for storing + images in Glance, please note that the configuration + options ``swift_store_multi_tenant`` and + ``swift_store_config_file`` are now mutually exclusive + and cannot be configured together. If you intend to + use multi-tenant store, please make sure that you have + not set a swift configuration file. |