Open Stack

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 and device_type.

I've added the same comment on the spec itself.

However, seeing the spec both showed me that there is a relative agreement
about the necessity of that change, and the preferable way to update the
API.
The spec is currently abandoned. I will consult with Alexandre, who wrote
the spec, about restoring the spec and maybe expand it to answer for the
updating for other bdm parameters.

Thanks again,
Shoham

On Fri, Feb 12, 2016 at 4:32 PM, Andrey Pavlov <andrey.mp at gmail.com> wrote:
>
> 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
> <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
> > 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
> >
> >
__________________________________________________________________________
> > 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
> >
>
>
>
> --
> Kind regards,
> Andrey Pavlov.
>
> __________________________________________________________________________
> 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/20160213/b533cad1/attachment.html>