> > > > >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 it does for shelve > today, and we'd do something like this: > > 1. disconnect the volume from the host > 2. create a new empty volume attachment for the volume and instance - this > is needed so the volume stays 'reserved' while we re-image it > 3. delete the old volume attachment > 4. call the new cinder re-image API > 5. once the volume is available (TODO: how would we know?)
May we can add a "Reimaging" state to the volume? Then Nova could poll for it to go from that back to Available? Since Nova is driving things, I would be hesitant to expect and assume that Cinder is appropriately configured to call back in to Nova. Or a notification? Or...? > 6. re-attach the volume by updating the attachment with the host connector, > connect on the host, and complete the attachment (marks the volume as in-use > again) > > -- > > Thanks, > > Matt > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
