Ask Your Question

Revision history [back]

I saw the same behavior when shrinking a VM, and when I chatted with one of our lead developers he reviewed the code and said that is expected behavior. The question I had from my customer was if my file system was full (100%) and I did the re-size downward what happens to my data ? So in this case this is what was wanted by my customer. I also found this link its almost a year old but might be helpful.

http://lists.openstack.org/pipermail/openstack-dev/2013-April/007478.html

I would agree with you and not let them do it until the code gets better.

I saw the same behavior when shrinking a VM, and when I chatted with one of our lead developers he reviewed the code and said that is expected behavior. The question I had from my customer was if my file system was full (100%) and I did the re-size downward what happens to my data ? So in this case this is what was wanted by my customer. I also found this link its almost a year old but might be helpful.

When a resize request is issued, the current running state of the VM is saved and paused. The definition of the VM is then regenerated using the information for the new flavor. The CPU and RAM will always be changed. A check is done on the disk size. If the size of the disk in the new flavor is greater then the size in the old flavor the disk is resized. If the new flavor's disk is smaller, the disk isn't resized and remains the size of the original flavor. The API and dashboard will report the new size based upon the new flavor but the actual disk will remain the original larger size.

http://lists.openstack.org/pipermail/openstack-dev/2013-April/007478.html

I would agree with you and not let them do it until the code gets better.

or report the outcome of the re-size.