e6be9a3edf
The Cinder v1 API was removed in Queens [1]. Its replacement, the v2 API, has existed since Grizzly [2]. More importantly, the v1 commands are implemented using python-cinderclient but support for the v1 API was removed from python-cinderclient in Train [3], meaning none of these have worked since then. Clearly if no one has noticed or cared in the 6 years or so since that happened, it's safe to say we can delete these commands. [1]3e91de956e[2]75ca60f619[3]2189e5702bChange-Id: Ibe1cd6461d2cb78826467078aa17272f171746aa Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
36 lines
1.3 KiB
YAML
36 lines
1.3 KiB
YAML
---
|
|
upgrade:
|
|
- |
|
|
Support for the Block Storage (Cinder) v1 API has been officially removed
|
|
as it had been broken for some time. If you haven't noticed then you likely
|
|
don't need to do anything. However, in the unlikely event that your cloud
|
|
is using the Block Storage v1 API - or incorrectly advertises the Block
|
|
Storage v1 API - consider overriding the API version to use v2 as this
|
|
behaves very similarly. It may also be necessary to set an endpoint
|
|
override for the Block Storage API if your clouds service catalog is not
|
|
configured correctly. For example:
|
|
|
|
.. code-block:: yaml
|
|
|
|
example:
|
|
regions:
|
|
- name: regionOne
|
|
values:
|
|
block_storage_endpoint_override: 'https://blockstorage.api.cloud.example/'
|
|
volume_api_version: 2
|
|
|
|
If using a public cloud provider, there may also be a profile already
|
|
published that sets these. These are listed in the `Vendor Support`__
|
|
doc. For example:
|
|
|
|
.. code-block:: yaml
|
|
|
|
example:
|
|
profile: rackspace
|
|
|
|
Alternatively, consider use versions of OSC < 3.19 and python-cinderclient
|
|
< 5.0 (both Stein), since these were the last versions to fully support
|
|
Cinder v1.
|
|
|
|
.. __: https://docs.openstack.org/openstacksdk/latest/user/config/vendor-support.html
|