If we update volumes quota for any volume type to 100, lets say for lvmdriver-1, then this should not update total volume count to 100 as we also have other volume types where we have specified volume count to -1(-1 depicts infinite)
So, running "cinder quota-update --volume-type lvmdriver-1 --volumes 100 --" should not update total volumes to 100 as there are other volume types as well.
Updating volume quota on basis of one volume type does not make good sense, so I thought it to make invalid.
Please let me know if I could not answer your query here.
Thanks!!
Dear Craig,
Well I got your point.
But in case we have mulitple volume types then updating quota volumes for one volume type should not update total volume quota.
For ex, lets we have 3 volume types:
1. lvmdriver
2. sheel_type
3. type_private
Then "cinder quota-show" will show details of volumes per volume_type as shown below:
1. | volumes_lvmdriver-1 | -1| type_private | -1 |
2. | volumes_sheel_type | -1 |
3. | volumes_
If we update volumes quota for any volume type to 100, lets say for lvmdriver-1, then this should not update total volume count to 100 as we also have other volume types where we have specified volume count to -1(-1 depicts infinite)
So, running "cinder quota-update --volume-type lvmdriver-1 --volumes 100 --" should not update total volumes to 100 as there are other volume types as well.
Updating volume quota on basis of one volume type does not make good sense, so I thought it to make invalid.
Please let me know if I could not answer your query here.
Thanks!!