Bug 1649256
| Summary: | [RFE] Add an option to rebuild root cinder volume that was created from image during instance's rebuild | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Alex Stupnikov <astupnik> |
| Component: | openstack-cinder | Assignee: | Rajat Dhasmana <rdhasman> |
| Status: | CLOSED MIGRATED | QA Contact: | Yosi Ben Shimon <ybenshim> |
| Severity: | medium | Docs Contact: | RHOS Documentation Team <rhos-docs> |
| Priority: | high | ||
| Version: | 18.0 (Zed) | CC: | astupnik, dasmith, eglynn, eharney, gcharot, jhakimra, kchamart, ltoscano, lyarwood, sbauza, sgordon, udesale, vromanso, yocha, yrabl |
| Target Milestone: | Alpha | Keywords: | FutureFeature, Triaged |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2024-01-05 11:29:26 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1657696, 1657697, 1847516, 2070445 | ||
|
Description
Alex Stupnikov
2018-11-13 09:23:51 UTC
I would like to clarify description a bit, sorry about ambiguous description. There are two scenarios when we may want to rebuild a root cinder volume: - instance is rebuilt; - instance is rebuilt with new source image. I believe that both should be addressed. BR, Alex. May I ask you about possible workarounds for this issue? Is it possible to re-build cinder volume that is used as instance's root volume somehow? (In reply to Alex Stupnikov from comment #2) > May I ask you about possible workarounds for this issue? Is it possible to > re-build cinder volume that is used as instance's root volume somehow? No it isn't, which is the principal limitation here. We need cinder to expose an api to re-image an existing volume. We've had discussions about this in the past, and the objections I recall have been: * maintaining driver-specific optimisations * driver-specific limitations wrt snapshots It's possible that in certain cases the only practical way to re-image a cinder volume may be to mount it and copy the image data back over it, which would obviously be slow. However, cinder would still need to be the service to do this, not least because it's the only service which knows if there's a faster option. If we had this api, enabling it in Nova would be relatively simple. (In reply to Matthew Booth from comment #3) > (In reply to Alex Stupnikov from comment #2) > > May I ask you about possible workarounds for this issue? Is it possible to > > re-build cinder volume that is used as instance's root volume somehow? > > No it isn't, which is the principal limitation here. We need cinder to > expose an api to re-image an existing volume. We've had discussions about > this in the past, and the objections I recall have been: > > * maintaining driver-specific optimisations > * driver-specific limitations wrt snapshots > > It's possible that in certain cases the only practical way to re-image a > cinder volume may be to mount it and copy the image data back over it, which > would obviously be slow. However, cinder would still need to be the service > to do this, not least because it's the only service which knows if there's a > faster option. > > If we had this api, enabling it in Nova would be relatively simple. There is currently work underway to add a re-image API to Cinder: https://git.openstack.org/cgit/openstack/cinder-specs/tree/specs/stein/add-volume-re-image-api.rst https://review.openstack.org/#/q/topic:bp/add-volume-re-image-api |