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.
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
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
Added ReplicateVolumeTask in retype flow, which will check and
apply/remove replication feature on volume based on new type.
Change-Id: Id53b9cbdc90fd18290747cd6ed5dd6f4673294dd
Closes-Bug: #1680313
We currently update the volume's status when attaching
a readonly volume with 'rw' mode. Instead we should
update the attachment's attach status.
Change-Id: I0ec13b0af0e9aff0e5ff1a3e9f6e645f8ac0fe4d
Closes-Bug: #1687583
for fb and ckd volume, they require different versions of REST
API, because APIs supporting their features are added one by one
and not at the same time, so driver should separate them when
verifying REST version, otherwise it will make user need to upgrade
REST unnecessarily.
Change-Id: Ib42db3f06705212fe3b8f4cfcb625d8a5fb270b7
backport: Ocata
Closes-Bug: #1680379
testr is part of testrepository, we invoke testr through os-testr
in Cinder and testrepository is dpendency of os-testr, we don't
invoke testr directly, so don't need dependency testrepository.
Change-Id: Ieb0662b1ea35e12387dc12c2b2eec7c3880d9c3b
Checking this in __init__ means that error messages are
issued for a missing pywbem dependency in scenarios where
the driver class is loaded, like when building sample
configuration.
This should be done at check_for_setup_error rather than
__init__.
Change-Id: Ida6b8ca1a749465d3b073dd93b30b7be643076fb