yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #23814
[Bug 1370384] Re: Cannot expand root volume by EC2 API
@ftersin -- the current implementation of nova's resize supports disk
resize as part of the resize operation / workflow. That is; if you
resize the server to a flavor which has a larger disk, the resize
operation will handle it. IMHO this workflow is much cleaner and more
user friendly than a 6 step manual process outlined in the description.
With that in mind it's not clear to me why a 6 step manual process is
needed (as per description of this bug) -- is this for AWS parity?
If you feel we need to support the manual root disk resize (e.g. detach
root disk + snapshot... + reattach root disk) then to me this is grounds
for a blueprint and I would suggest you open a nova blueprint
(https://blueprints.launchpad.net/nova) for the requested functionality.
The current nova implementation does not currently handle root disk
detach (checked at API layer), nor does it handle root disk attach
(compute layer). With a few quick hacks I was able to make this work
w/libvirt KVM. However from a user perspective I believe we'd need to
think about how this would work / look; something similar to the
existing nova resize; or perhaps as an option in resize.
I'm going to close this as will not fix based on my above comments. If
you feel this is an incorrect state feel free to re-open.
Thanks
** Changed in: nova
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1370384
Title:
Cannot expand root volume by EC2 API
Status in OpenStack Compute (Nova):
Won't Fix
Bug description:
AWS provides a scenario to expand volumes of an instance (http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-expand-volume.html). It consist of:
1 Stop the instance
2 Create a snapshot of the volume
3 Create a new volume from the snapshot
4 Detach the old volum
5 Attach the new volume using the same device name
6 Start the instance
In Nova this works for non-root devices, but doesn't for a root
device.
Now in current version (Juno) since
https://review.openstack.org/#/c/75552/ was merged it's not able to
detach root volume at all.
$ nova volume-detach inst 02f60d80-47ee-47ed-a795-cb4d05f5103e
ERROR (Forbidden): Can't detach root device volume (HTTP 403) (Request-ID: req-e25134dc-1330-4fe1-9d21-abc274e75a1d)
Before this commit it was able, but it was unable to attach the root
volume back.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1370384/+subscriptions
References