Open Stack

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 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?

Shoham

On Thu, Feb 11, 2016 at 7:04 PM, Andrea Rosa <andrea.rosa at hpe.com> wrote:
>
> 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 high-priority list and it
> didn't get implemented but we are going to propose it again for Newton.
>
> Regards
> --
> Andrea Rosa
>
> [1]
>
http://specs.openstack.org/openstack/nova-specs/specs/mitaka/approved/detach-boot-volume.html
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160211/032e4de7/attachment.html>