| 1 |
--- |
| 2 |
fixes: |
| 3 |
- | |
| 4 |
NetApp driver `bug #2117263 |
| 5 |
<https://bugs.launchpad.net/cinder/+bug/2117263>`_: Fixed |
| 6 |
the issue where the driver does not account for storage limits when |
| 7 |
provisioning volumes. |
| 8 |
features: |
| 9 |
- | |
| 10 |
The NetApp driver now supports the capability "total_volumes" and the |
| 11 |
default filter function is updated to filter the backends once the pool |
| 12 |
reaches maximum number of volumes which is 1024 and is due to the |
| 13 |
limitations from ONTAP FlexVolume. |
| 14 |
|
| 15 |
The "total_volumes" can be used in netapp driver backend stanza to restrict |
| 16 |
the number of volumes per pool, like in below example we are restricting |
| 17 |
maximum number of volumes per a pool to 10. |
| 18 |
Example: filter_function="capabilities.total_volumes < 10" |
| 19 |
|
| 20 |
Note: The admin needs to configure the scheduler_default_filters to include |
| 21 |
the DriverFilter as well under [DEFAULT] stanza as part of cinder.conf, |
| 22 |
please refer [1] for the default filter list. |
| 23 |
|
| 24 |
[1] https://docs.openstack.org/cinder/latest/configuration/block-storage/samples/cinder.conf.html |