0273652206
Now exists multiple inheritance when adding new interfaces in volume v3 clients, e.g., if we want to add show_volume_summary in volume v3 VolumesClient, we have to make volume.v3.VolumesClient inherit from both volume.v3.base_client.BaseClient and volume.v2. volumes_client.VolumesClient, and this situation will repeat everytime we add new interfaces in volume v3 clients based on v2 clients. This is to move volume.v3.base_client to volume, and if we want to add new interfaces based on a v2 client, we can make that v2 client inherit from volume.base_client.BaseClient to get microversion support, and then to make the new v3 client inherit from the v2 client, thus to avoid the multiple inheritance. Change-Id: I645ae35daebd924c4c4523163e5419cc050bb0ed
16 lines
633 B
YAML
16 lines
633 B
YAML
features:
|
|
- |
|
|
Move base_client from tempest.lib.services.volume.v3 to
|
|
tempest.lib.services.volume, so if we want to add new
|
|
interfaces based on a v2 client, we can make that v2
|
|
client inherit from volume.base_client.BaseClient to
|
|
get microversion support, and then to make the new v3
|
|
client inherit from the v2 client, thus to avoid the
|
|
multiple inheritance.
|
|
deprecations:
|
|
- |
|
|
Deprecate class BaseClient from volume.v3.base_client
|
|
and move it to volume.base_client.
|
|
``tempest.lib.services.volume.v3.base_client.BaseClient``
|
|
(new ``tempest.lib.services.volume.base_client.BaseClient``)
|