Thank you Andrey. I wasn't aware of that spec.
It indeed implements the same idea of updating the bdm, but it's not enough
in my opinion.
It is about updating the delete_on_termination parameter, which is great,
but the user should also be able to update the other parameters, such as
the disk_bus
Hello Shoham,
We've tried to write and implement similar spec [1].
And someone have tried to implement it [2].
You can see comments in it.
[1] - https://review.openstack.org/#/c/234269/
[2] - https://review.openstack.org/#/c/259518/
On Thu, Feb 11, 2016 at 8:20 PM, Shoham Peller
Hi,
Currently there is no way to update the volume-attachment bdm parameters,
i.e. the bus type or device name, without detaching and re-attaching the
volume, and supplying the new parameters. This is obviously not ideal, and
if the volume we want to update is the boot volume, detaching to update
Hi
On 11/02/16 16:51, Shoham Peller wrote:
> if the volume we want to update is the boot
> volume, detaching to update the bdm, is not even possible.
You might be interested in the approved spec [1] we have for Mitaka
(ref. detach boot volume).
Unfortunately the spec was not part of the
Thank you Andrea for your reply.
I know this spec and it is indeed a viable solution.
However, I think allowing users to update the attachment detail, rather
than detach and re-attach a volume for every change is more robust and more
convenient.
Also, IMHO it's a better user-experience if users
