[openstack-dev] [cinder] [nova] Do we need a "force" parameter in cinder "re-image" API?
sombrafam at gmail.com
Tue Oct 9 13:04:26 UTC 2018
If you are planning to re-image an image on a bootable volume then yes you
should use a force parameter. I have lost the discussion about this on PTG.
What is the main use cases? This seems to me something that could be
leveraged with the current revert-to-snapshot API, which would be even
better. The flow would be:
1 - create a volume from image
2 - create an snapshot
3 - do whatever you wan't
4 - revert the snapshot
Would that help in your the use cases?
Em seg, 8 de out de 2018 às 10:54, Sean McGinnis <sean.mcginnis at gmx.com>
> On Mon, Oct 08, 2018 at 03:09:36PM +0800, Yikun Jiang wrote:
> > In Denver, we agree to add a new "re-image" API in cinder to support
> > volume-backed server rebuild with a new image.
> > An initial blueprint has been drafted in , welcome to review it,
> > : )
> > [snip]
> > The "force" parameter idea comes from , means that
> > 1. we can re-image an "available" volume directly.
> > 2. we can't re-image "in-use"/"reserved" volume directly.
> > 3. we can only re-image an "in-use"/"reserved" volume with "force"
> > parameter.
> > And it means nova need to always call re-image API with an extra "force"
> > parameter,
> > because the volume status is "in-use" or "reserve" when we rebuild the
> > server.
> > *So, what's you idea? Do we really want to add this "force" parameter?*
> I would prefer we have the "force" parameter, even if it is something that
> always be defaulted to True from Nova.
> Having this exposed as a REST API means anyone could call it, not just Nova
> code. So as protection from someone doing something that they are not
> clear on the full implications of, having a flag in there to guard volumes
> are already attached or reserved for shelved instances is worth the very
> extra overhead.
> >  https://etherpad.openstack.org/p/nova-ptg-stein L483
> >  https://etherpad.openstack.org/p/cinder-ptg-stein-thursday-rebuild
> >  https://review.openstack.org/#/c/605317
> > 
> > Regards,
> > Yikun
> > ----------------------------------------
> > Jiang Yikun（Kero）
> > Mail: yikunkero at gmail.com
> > 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
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev