ca7f23d0d1
We're not going to expose the ability to swap volumes since that's a things humans should not generally use. From the API docs [1]: When updating volumeId, this API is typically meant to only be used as part of a larger orchestrated volume migration operation initiated in the block storage service via the os-retype or os-migrate_volume volume actions. Direct usage of this API to update volumeId is not recommended and may result in needing to hard reboot the server to update details within the guest such as block storage serial IDs. Furthermore, updating volumeId via this API is only implemented by certain compute drivers. We *do* want users to have the ability to change the delete on termination behavior though, so that's what we expose. [1] https://docs.openstack.org/api-ref/compute/?expanded=update-a-volume-attachment-detail#update-a-volume-attachment Change-Id: I50938e1237b4d298521b26a5f9cb90c018dfebaf Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
15 lines
536 B
Plaintext
15 lines
536 B
Plaintext
# The order of packages is significant, because pip processes them in the order
|
|
# of appearance. Changing the order has an impact on the overall integration
|
|
# process, which may cause wedges in the gate later.
|
|
pbr!=2.1.0,>=2.0.0 # Apache-2.0
|
|
|
|
cliff>=3.5.0 # Apache-2.0
|
|
iso8601>=0.1.11 # MIT
|
|
openstacksdk>=0.52.0 # Apache-2.0
|
|
osc-lib>=2.3.0 # Apache-2.0
|
|
oslo.i18n>=3.15.3 # Apache-2.0
|
|
python-keystoneclient>=3.22.0 # Apache-2.0
|
|
python-novaclient>=17.0.0 # Apache-2.0
|
|
python-cinderclient>=3.3.0 # Apache-2.0
|
|
stevedore>=2.0.1 # Apache-2.0
|