Now cinder will raise 400 if invalid filter
keys are specified, Update the corresponding
list APIs.
DocImpact
Depends-On: ff3d41b15abb2915de87830980147be51e5da971
Change-Id: I8419b374d7f743e7e9fc88e31c8c4f7d9470059b
XtremIO were two reading xtremio_array_busy_retry_count and
xtremio_array_busy_retry_interval from global CONF (that is - from
[DEFAULT] section) instead of using self.configuration (which will read
from [<backend_name>] section. This prevented users from setting those
values individually for each XtremIO backend. This commit fixes this.
Change-Id: I9eb5e7a11bff9002d8c25f41c4a35600656f64bd
Closes-Bug: 1680065
In Ceph driver there were two occurences of reading
rados_connection_interval and rados_connection_retries from global CONF
(that is - from [DEFAULT] section) instead of using self.configuration
(which will read from [<backend_name>] section. This prevented users
from setting those values individually for each Ceph backend. This
commit fixes this.
Change-Id: I1cd83ee54d5a94b312f0c84861c9d7929cae853f
Closes-Bug: 1680036
This patch adds generalized filtering support for these list APIs:
1. list volume
2. list backup
3. list snapshot
4. list group
5. list group-snapshot
6. list attachment
7. list message
8. get pools
DocImpact
APIImpact
Co-Authored-By: TommyLike <tommylikehu@gmail.com>
Change-Id: Icee6c22621489f93614f4adf071329d8d2115637
Partial: blueprint generalized-filtering-for-cinder-list-resource
The nova client (used by the InstanceLocalityFilter for example)
seems to have obscure config options (compared to other projects),
and seems it is buggy too. Fix this by introducing a [nova] section,
where the usual auth parameters can be put (auth_type, auth_url,
username, password, etc...), and deprecate the old options.
Also doesn't play with the Service Catalog, the authentication plugins
can handle it, use a Token authentication plugin when using
the user context, and removed the separate usage of the admin endpoint.
Change-Id: I55613793c8f525a36ac74636f47d7ab76f5c7e39
Closes-bug: #1686616
DocImpact: to use a Nova connection (e.g. for InstanceLocalityFilter),
one has to configure the [nova] section.
ScaleIO 1.32 is coming to EOL within Dell EMC. We will deprecate
support in Pike and remove support in a future release
Change-Id: Id3aa5163319b46b21ee5dcecb8559f8498d1f67e
Make subprocess.check_output() return strings
instead of bytes by adding universal_newlines.
This fixes the check_uptodate failure during
"tox -e pep8" in a py3 env.
This also sorts the config sections alphabetically.
Closes-Bug: #1688313
Change-Id: If8aaa0d552c5997194f43a38a6674cdfdd9fd15a
The API would log that a volume was created successfully
after successfully sending the async create request. This
patch updates the log message to more accurately state the
request was successfully sent.
Change-Id: I827c54c4ef4d7ad88722782482a39b4f29e322c9
Closes-Bug: #1678034
Oslo.config deprecated parameter enforce_type and change its
default value to True in Ifa552de0a994e40388cbc9f7dbaa55700ca276b0.
Remove the usage of it to avoid DeprecationWarning: "Using the
'enforce_type' argument is deprecated in version '4.0' and will be
removed in version '5.0': The argument enforce_type has changed its
default value to True and then will be removed completely."
Related--Bug: #1517839
Change-Id: I92f76fa44f71497c10d320a2823dc5ba623309f6
This applies an order to the v3 API reference documents.
The idea being how does a new user come into and use the API
and what APIs should they see first when getting started.
Naturally they need to know about versions and microversions
that are avaible. Then they might need to know about volume
types before creating a volume. Once they create a volume
and know the basics of working with volumes, they can start
to take some actions on volumes. After that it's just kind
of a random free for all of APIs and the only order applied
to the rest is sorting alphabetically by title.
Change-Id: I8956de3e6907582f7115430eb959813a13e87a49
Since the v2 API is deprecated, put it in the index after
the v3 API which is current, since as a user the first thing
I want to see is the currently supported API reference, not
the deprecated stuff I shouldn't be using anyway.
Change-Id: I760533ca693cb8f678a6031e07789cd68f11bc47
Use oslo_db to create index and add missing testcases
for migration script 091, 098 and 099, also eliminate
the deprecation warning.
Change-Id: I6163489ca0f59160e7d3bfd837b72995be17c059