yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #80924
[Bug 1841514] Re: VMware: disk_io_limits settings are not reflected when resize
Reviewed: https://review.opendev.org/680296
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=326f84566340684c9f9e49fd3e3f03ab3a90a435
Submitter: Zuul
Branch: master
commit 326f84566340684c9f9e49fd3e3f03ab3a90a435
Author: Akira KAMIO <akamio@xxxxxxxxxxxxx>
Date: Thu Sep 5 13:35:47 2019 +0900
VMware: disk_io_limits settings are not reflected when resize
When resize and resize-revirt excute, setting disk_io_limits of
target flavor. But using VMware driver, disk_io_limits does not
changed.
On VMware driver, setting disk_io_limits when attach disk.
But, original is not setting it when resize. So add force
detach/attach disk when resize. Specifically, the original
_resize_disk() didn't anything if flavor.root_gb has not
changed. This is because we need to apply the change of
disk_io_limits to the virtual machine anytime.
Change-Id: I98f00257c38d95423bc926f3aa6a7b39dc84012e
Closes-bug: #1841514
** Changed in: nova
Status: In Progress => Fix Released
--
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/1841514
Title:
VMware: disk_io_limits settings are not reflected when resize
Status in OpenStack Compute (nova):
Fix Released
Bug description:
Description
===========
We found that disk_io_limits settings are not reflected when resize using vmware driver.
Steps to reproduce
==================
* I did command resize using CLI or horizon
* then VM status VERIFY_RESIZE with no problem
* then I did command resize-confirm
* It looks like it worked
* But when I check vCenter, IOPS has not changed
Expected result
===============
* IOPS settings are configured for the resized VM
Actual result
=============
* IOPS settings are not configured for the resized VM
Environment
===========
1. Exact version of OpenStack you are running.
* Community OpenStack Mitaka
2. Which hypervisor did you use?
* VMware
3. Which networking type did you use?
* Neutron ML2 Driver For VMWare vCenter DVS
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1841514/+subscriptions
References