When a CLI user specifies --os-volume api-version 3.66, the shell
will execute the appropriate shell code, but if the server only
supports < 3.66, the client is automatically downgraded and correctly
uses the pre-3.66 SnapshotManager.create() method.

In that case, the 'force' parameter, which is technically not allowed
in mv 3.66 (but which silently accepts a True value for backward
compatibility), will have a value of None, which the pre-3.66 code
happily passes to cinder as '"force": null' in the request body, and
which then fails the Block Storage API request-schema check.

Handle this situation by detecting a None 'force' value and setting
it to its pre-3.66 default value of False.

Change-Id: I3ad8283c2a9aaac58c8d2b50fa7ac86b617e5dd3
Closes-bug: #1995883

In Zed cycle, we have dropped the python 3.6/3.7[1] testing
and its support. Moving the py36 job to py38 based but to run on
ubuntu focal as c8s does not seems to have py38.
Also updating the python classifier also to reflect the same.

[1] https://governance.openstack.org/tc/reference/runtimes/zed.html

Change-Id: Ic26a360d2bb09fa6622d1acaa5021c5afbc70240

Add a release note prelude for the Yoga release.

Change-Id: Id601999762596713c94e7805a7d76dbcf31edf24

A new reimage API will be introduced on cinder API side with
change in depends on. This patch provides the CLI support for
the same by adding a reimage command.

Implements: blueprint add-volume-re-image-api

Change-Id: I37c254d4caf2f416e456ff6a78b5a4df4e08a176

When we run "cinder help" we can see that there is a --collect-timing
option:

  --collect-timing Collect per-API call timing information.

This is a keystone session option that we are not currently acting on
from a user perspective.

This patch adds support for this option, and we'll be able to see the
timing in a similar way as we do with OSC:

$ cinder --collect-timing api-version
+------+---------+---------+-------------+
| ID   | Status  | Version | Min_version |
+------+---------+---------+-------------+
| v3.0 | CURRENT | 3.66    | 3.0         |
+------+---------+---------+-------------+
+--------+------------------------------------------------+----------+
| method | url                                            | seconds  |
+--------+------------------------------------------------+----------+
| GET    | http://192.168.121.243/identity                | 0.003591 |
| POST   | http://192.168.121.243/identity/v3/auth/tokens | 0.016649 |
| GET    | http://192.168.121.243/volume/                 | 0.004012 |
| GET    | http://192.168.121.243/volume/                 | 0.004543 |
+--------+------------------------------------------------+----------+

The patch formats the "elapsed" time attribute into seconds and renames
the column to "seconds" to make it more user friendly similar to OSC.
If we didn't it would look like 0:00:00.003744

Closes-Bug: #1960337
Change-Id: Ia6b31794bf60a351007cc4476a76b9bcb76bf378

Includes prelude plus a note for change I524490aa988f.

Change-Id: I233faad57c9708cae9544c965fd0d94abdf6d684

Block Storage API mv 3.66 enables snapshots of in-use volumes
without requiring a 'force' flag.  For backward compatibility,
the API silently accepts force=true, even though the 'force' flag
is considered invalid for that call.  That behavior is replicated
in the client, where --force with a true value is silently accepted.
The --force option is not advertised in the shell and an option
value that doesn't evaluate to true raises an UnsupportedAttribute
error.  Similar behavior from the v3 Snapshot class, except it
raises a ValueError under similar circumstances.

Change-Id: I7408d0e3a5ed7f4cbcaf65cf3434ad60aaed511d

Remove all cinderclient.v2 classes, mostly incorporating them into
their v3 counterparts and updating the tests and test fixtures.

Depends-on: https://review.opendev.org/c/openstack/horizon/+/800814

Change-Id: I335db5c1799edb2273bf8bfc9e1bc9de404a4ba5