| 1 |
--- |
| 2 |
upgrade: |
| 3 |
- | |
| 4 |
VMware vmdk driver: The vmware vmdk driver had its get_volume_stats |
| 5 |
removed in a previous release due to a potential performance hit of 20% |
| 6 |
at a high load. The problem with reporting ``unknown`` back to the |
| 7 |
scheduler, is that it effectively removes cinder's ability to properly |
| 8 |
schedule based on capacity utilization. When this driver is enabled in a |
| 9 |
heterogenous environment without properly reporting utilization |
| 10 |
statistics, the scheduler's capacity filter will always allow this driver |
| 11 |
to service a provisioning request. Without reporting the backend stats, |
| 12 |
the capacity filter also can't determine the reserved_percentage as well |
| 13 |
as the max_over_subscription_ratio. To enable the collection of stats |
| 14 |
set ``vmware_enable_volume_stats`` to True in the driver section of |
| 15 |
cinder.conf. The default setting is False. Keep in mind that there may |
| 16 |
be a degradation in performance on the vcenter when enabling this setting. |
| 17 |
fixes: |
| 18 |
- | |
| 19 |
VMware vmdk driver: The collection of volume stats, which had been |
| 20 |
disabled, may now be turned on by using the ``vmware_enable_volume_stats`` |
| 21 |
configuration option. The default for this option is False (no |
| 22 |
stats collection). Be aware that enabling volume stats may cause |
| 23 |
performance issues under high load. |