[openstack-dev] [nova] Updating a volume attachment
andrey.mp at gmail.com
Fri Feb 12 14:32:36 UTC 2016
We've tried to write and implement similar spec .
And someone have tried to implement it .
You can see comments in it.
 - https://review.openstack.org/#/c/234269/
 - https://review.openstack.org/#/c/259518/
On Thu, Feb 11, 2016 at 8:20 PM, Shoham Peller
<shoham.peller at stratoscale.com> wrote:
> 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
> Also, IMHO it's a better user-experience if users can use a single API call
> instead of detach API call, poll for the detachment, re-attach the volume,
> and poll again for the attachment if they want to powerup the VM.
> The bdm DB updating, can happen from nova-api, without IRC'ing a compute
> node, and thus return only when the request has been completed fully.
> Don't you agree it's needed, even when detaching a boot volume is possible?
> On Thu, Feb 11, 2016 at 7:04 PM, Andrea Rosa <andrea.rosa at hpe.com> wrote:
>> 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  we have for Mitaka
>> (ref. detach boot volume).
>> Unfortunately the spec was not part of the high-priority list and it
>> didn't get implemented but we are going to propose it again for Newton.
>> Andrea Rosa
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev