Re: [openstack-dev] [cinder][nova] about re-image the volume

On 09/04, Sean McGinnis wrote: > On Mon, Apr 09, 2018 at 07:00:56PM +0100, Duncan Thomas wrote: > > Hopefully this flow means we can do rebuild root filesystem from > > snapshot/backup too? It seems rather artificially limiting to only do > > restore-from-image. I'd expect restore-from-snap to be

Re: [openstack-dev] [cinder][nova] about re-image the volume

On 4/9/2018 1:00 PM, Duncan Thomas wrote: Hopefully this flow means we can do rebuild root filesystem from snapshot/backup too? It seems rather artificially limiting to only do restore-from-image. I'd expect restore-from-snap to be a more common use case, personally. Hmm, now you've got me

Re: [openstack-dev] [cinder][nova] about re-image the volume

On Mon, Apr 09, 2018 at 07:00:56PM +0100, Duncan Thomas wrote: > Hopefully this flow means we can do rebuild root filesystem from > snapshot/backup too? It seems rather artificially limiting to only do > restore-from-image. I'd expect restore-from-snap to be a more common > use case, personally. >

Re: [openstack-dev] [cinder][nova] about re-image the volume

Hopefully this flow means we can do rebuild root filesystem from snapshot/backup too? It seems rather artificially limiting to only do restore-from-image. I'd expect restore-from-snap to be a more common use case, personally. On 9 April 2018 at 09:51, Gorka Eguileor wrote: >

Re: [openstack-dev] [cinder][nova] about re-image the volume

On 4/9/2018 3:51 AM, Gorka Eguileor wrote: As I see it, the process would look something like this: - Nova detaches volume using OS-Brick - Nova calls Cinder re-image passing the node's info (like we do when attaching a new volume) - Cinder would: - Ensure only that node is connected to

Re: [openstack-dev] [cinder][nova] about re-image the volume

On 06/04, Matt Riedemann wrote: > On 4/6/2018 5:09 AM, Matthew Booth wrote: > > I think you're talking at cross purposes here: this won't require a > > swap volume. Apart from anything else, swap volume only works on an > > attached volume, and as previously discussed Nova will detach and > >

Re: [openstack-dev] [cinder][nova] about re-image the volume

On 4/6/2018 5:09 AM, Matthew Booth wrote: I think you're talking at cross purposes here: this won't require a swap volume. Apart from anything else, swap volume only works on an attached volume, and as previously discussed Nova will detach and re-attach. Gorka, the Nova api Matt is referring to

Re: [openstack-dev] [cinder][nova] about re-image the volume

On 6 April 2018 at 09:31, Gorka Eguileor wrote: > On 05/04, Matt Riedemann wrote: >> On 4/5/2018 3:15 AM, Gorka Eguileor wrote: >> > But just to be clear, Nova will have to initialize the connection with >> > the re-imagined volume and attach it again to the node, as in all

Re: [openstack-dev] [cinder][nova] about re-image the volume

On 05/04, Matt Riedemann wrote: > On 4/5/2018 3:15 AM, Gorka Eguileor wrote: > > But just to be clear, Nova will have to initialize the connection with > > the re-imagined volume and attach it again to the node, as in all cases > > (except when defaulting to downloading the image and dd-ing it to

Re: [openstack-dev] [cinder][nova] about re-image the volume

On 4/5/2018 3:15 AM, Gorka Eguileor wrote: But just to be clear, Nova will have to initialize the connection with the re-imagined volume and attach it again to the node, as in all cases (except when defaulting to downloading the image and dd-ing it to the volume) the result will be a new volume

Re: [openstack-dev] [cinder][nova] about re-image the volume

On 04/04, Matt Riedemann wrote: > On 4/2/2018 6:59 AM, Gorka Eguileor wrote: > > I can only see one benefit from implementing this feature in Cinder > > versus doing it in Nova, and that is that we can preserve the volume's > > UUID, but I don't think this is even relevant for this use case, so

Re: [openstack-dev] [cinder][nova] about re-image the volume

On 4/2/2018 6:59 AM, Gorka Eguileor wrote: I can only see one benefit from implementing this feature in Cinder versus doing it in Nova, and that is that we can preserve the volume's UUID, but I don't think this is even relevant for this use case, so why is it better to implement this in Cinder

Re: [openstack-dev] [cinder][nova] about re-image the volume

On 29/03, Sean McGinnis wrote: > > This is the spec [0] about rebuild the volumed backed server. > > The question raised in the spec is about how to bandle the root volume. > > Finally,in Nova team,we think that the cleanest / best solution to this is > > to > > add a volume action API to

Re: [openstack-dev] [cinder][nova] about re-image the volume

On 3/29/2018 8:36 PM, Matt Riedemann wrote: On 3/29/2018 6:50 PM, Sean McGinnis wrote: May we can add a "Reimaging" state to the volume? Then Nova could poll for it to go from that back to Available? That would be fine with me, and maybe similar to how 'extending' and 'retyping' work for

Re: [openstack-dev] [cinder][nova] about re-image the volume

On 3/29/2018 6:50 PM, Sean McGinnis wrote: May we can add a "Reimaging" state to the volume? Then Nova could poll for it to go from that back to Available? That would be fine with me, and maybe similar to how 'extending' and 'retyping' work for an attached volume? Nova wouldn't wait for the

Re: [openstack-dev] [cinder][nova] about re-image the volume

> > > > >Ideally, from my perspective, Nova would take care of the detach/attach > >portion > >and Cinder would only need to take care of imaging the volume. > > Agree. :) And yeah, I pointed this out in the nova spec for volume-backed > rebuild also. I think nova can basically handle this like

Re: [openstack-dev] [cinder][nova] about re-image the volume

On 3/29/2018 9:28 AM, Sean McGinnis wrote: I do not think changing the revert to snapshot implementation is appropriate here. There may be some cases where this can get the desired result, but there is no guarantee that there is a snapshot on the volume's base image state to revert to. It also

Re: [openstack-dev] [cinder][nova] about re-image the volume

> This is the spec [0] about rebuild the volumed backed server. > The question raised in the spec is about how to bandle the root volume. > Finally,in Nova team,we think that the cleanest / best solution to this is to > add a volume action API to cinder for re-imaging the volume.Once that is

[openstack-dev] [cinder][nova] about re-image the volume

Hi,all This is the spec [0] about rebuild the volumed backed server.The question raised in the spec is about how to bandle the root volume.Finally,in Nova team,we think that the cleanest / best solution to this is to add a volume action API to cinder for re-imaging the volume.Once that