Public bug reported:
===========
When you use cinder volume-type to limit iops on the frontend work as expected
when you create a instance however if you resize the volume the IOPS limit is
not updating on the instance.
Steps to reproduce
==================
1.Create a Volume-type with Associated QoS Spec
2.Create a Qos Spec with frontend and specs total_iops_sec_per_gb=3
3.associate this QoS to Volume Type
4.Create a new instance with a 100GB volume these new volume type you will
notice in KVM the following configuration.
<iotune>
<total_iops_sec>300</total_iops_sec>
</iotune>
5.stop the instance
6.cinder extend <Volume> 300
7.start the instance
Expected result
===============
After the instance is started KVM should update the total_iops_sec to
<total_iops_sec>900</total_iops_sec>
Actual result
=============
the total_iops_sec keeps with the original configuration when the computer was
provisioned.
Environment
===========
1.Openstack Train
2.KVM
2. NFS
** Affects: nova
Importance: Undecided
Status: New
--
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/1949224
Title:
Nova is not updating IOPS configuration if you perform a volume resize
on cinder
Status in OpenStack Compute (nova):
New
Bug description:
===========
When you use cinder volume-type to limit iops on the frontend work as
expected when you create a instance however if you resize the volume the IOPS
limit is not updating on the instance.
Steps to reproduce
==================
1.Create a Volume-type with Associated QoS Spec
2.Create a Qos Spec with frontend and specs total_iops_sec_per_gb=3
3.associate this QoS to Volume Type
4.Create a new instance with a 100GB volume these new volume type you will
notice in KVM the following configuration.
<iotune>
<total_iops_sec>300</total_iops_sec>
</iotune>
5.stop the instance
6.cinder extend <Volume> 300
7.start the instance
Expected result
===============
After the instance is started KVM should update the total_iops_sec to
<total_iops_sec>900</total_iops_sec>
Actual result
=============
the total_iops_sec keeps with the original configuration when the computer
was provisioned.
Environment
===========
1.Openstack Train
2.KVM
2. NFS
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1949224/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
