| 2017-08-31 09:32:32 |
Gorka Eguileor |
bug |
|
|
added bug |
| 2017-08-31 09:32:58 |
Gorka Eguileor |
description |
All NetApp drivers are incorrectly reporting "provisioned_capacity_gb", probably because provisioned capacity means something different on the NetApp storage arrays themselves.
Reported values are always actual physical used size [1][2][3][4], which is not correct as it should contain the maximum size that all volumes present in the backend could reach, total virtual size if you will.
Due to this over provisioning doesn't work as expected. A clear example is if you use thin provisioning with a 1.0 max_over_provisioning ratio, as you'll still be doing over provisioning.
[1] https://github.com/openstack/cinder/blob/55e29347221f1c3c1fca26ab0144ecc1f54b87b6/cinder/volume/drivers/netapp/eseries/library.py#L1466
[2] https://github.com/openstack/cinder/blob/55e29347221f1c3c1fca26ab0144ecc1f54b87b6/cinder/volume/drivers/netapp/dataontap/nfs_base.py#L888
[3] https://github.com/openstack/cinder/blob/55e29347221f1c3c1fca26ab0144ecc1f54b87b6/cinder/volume/drivers/netapp/dataontap/block_7mode.py#L344
[4] https://github.com/openstack/cinder/blob/55e29347221f1c3c1fca26ab0144ecc1f54b87b6/cinder/volume/drivers/netapp/dataontap/block_cmode.py#L320
[5] https://review.openstack.org/#/c/490116/2/specs/queens/provisioning-improvements.rst@103 |
All NetApp drivers are incorrectly reporting "provisioned_capacity_gb", probably because provisioned capacity means something different on the NetApp storage arrays themselves.
Reported values are always actual physical used size [1][2][3][4], which is not correct as it should contain the maximum size that all volumes present in the backend could reach [5], total virtual size if you will.
Due to this over provisioning doesn't work as expected. A clear example is if you use thin provisioning with a 1.0 max_over_provisioning ratio, as you'll still be doing over provisioning.
[1] https://github.com/openstack/cinder/blob/55e29347221f1c3c1fca26ab0144ecc1f54b87b6/cinder/volume/drivers/netapp/eseries/library.py#L1466
[2] https://github.com/openstack/cinder/blob/55e29347221f1c3c1fca26ab0144ecc1f54b87b6/cinder/volume/drivers/netapp/dataontap/nfs_base.py#L888
[3] https://github.com/openstack/cinder/blob/55e29347221f1c3c1fca26ab0144ecc1f54b87b6/cinder/volume/drivers/netapp/dataontap/block_7mode.py#L344
[4] https://github.com/openstack/cinder/blob/55e29347221f1c3c1fca26ab0144ecc1f54b87b6/cinder/volume/drivers/netapp/dataontap/block_cmode.py#L320
[5] https://review.openstack.org/#/c/490116/2/specs/queens/provisioning-improvements.rst@103 |
|
| 2017-09-02 00:30:40 |
Tom Barron |
bug |
|
|
added subscriber Tom Barron |
| 2017-09-07 20:33:21 |
Paul Grist |
bug |
|
|
added subscriber Paul Grist |
| 2017-09-20 14:56:05 |
OpenStack Infra |
cinder: status |
New |
In Progress |
|
| 2017-09-20 14:56:05 |
OpenStack Infra |
cinder: assignee |
|
Goutham Pacha Ravi (gouthamr) |
|
| 2017-09-21 17:24:23 |
Goutham Pacha Ravi |
description |
All NetApp drivers are incorrectly reporting "provisioned_capacity_gb", probably because provisioned capacity means something different on the NetApp storage arrays themselves.
Reported values are always actual physical used size [1][2][3][4], which is not correct as it should contain the maximum size that all volumes present in the backend could reach [5], total virtual size if you will.
Due to this over provisioning doesn't work as expected. A clear example is if you use thin provisioning with a 1.0 max_over_provisioning ratio, as you'll still be doing over provisioning.
[1] https://github.com/openstack/cinder/blob/55e29347221f1c3c1fca26ab0144ecc1f54b87b6/cinder/volume/drivers/netapp/eseries/library.py#L1466
[2] https://github.com/openstack/cinder/blob/55e29347221f1c3c1fca26ab0144ecc1f54b87b6/cinder/volume/drivers/netapp/dataontap/nfs_base.py#L888
[3] https://github.com/openstack/cinder/blob/55e29347221f1c3c1fca26ab0144ecc1f54b87b6/cinder/volume/drivers/netapp/dataontap/block_7mode.py#L344
[4] https://github.com/openstack/cinder/blob/55e29347221f1c3c1fca26ab0144ecc1f54b87b6/cinder/volume/drivers/netapp/dataontap/block_cmode.py#L320
[5] https://review.openstack.org/#/c/490116/2/specs/queens/provisioning-improvements.rst@103 |
All NetApp ONTAP drivers are incorrectly reporting "provisioned_capacity_gb", probably because provisioned capacity means something different on the NetApp ONTAP storage arrays themselves.
Reported values are always actual physical used size [1][2][3], which is not correct as it should contain the maximum size that all volumes present in the backend could reach [4], total virtual size if you will.
Due to this over provisioning doesn't work as expected. A clear example is if you use thin provisioning with a 1.0 max_over_provisioning ratio, as you'll still be doing over provisioning.
[1] https://github.com/openstack/cinder/blob/55e29347221f1c3c1fca26ab0144ecc1f54b87b6/cinder/volume/drivers/netapp/dataontap/nfs_base.py#L888
[2] https://github.com/openstack/cinder/blob/55e29347221f1c3c1fca26ab0144ecc1f54b87b6/cinder/volume/drivers/netapp/dataontap/block_7mode.py#L344
[3] https://github.com/openstack/cinder/blob/55e29347221f1c3c1fca26ab0144ecc1f54b87b6/cinder/volume/drivers/netapp/dataontap/block_cmode.py#L320
[4] https://review.openstack.org/#/c/490116/2/specs/queens/provisioning-improvements.rst@103
NetApp E-Series drivers may have a similar behavior, reported as a separate bug here: https://bugs.launchpad.net/cinder/+bug/1718739 |
|
| 2017-09-21 17:24:29 |
Goutham Pacha Ravi |
summary |
NetApp reporting incorrect provisioned_capacity_gb |
NetApp ONTAP drivers reporting incorrect provisioned_capacity_gb |
|
| 2017-09-27 16:39:07 |
OpenStack Infra |
cinder: assignee |
Goutham Pacha Ravi (gouthamr) |
Ben Swartzlander (bswartz) |
|
| 2017-10-05 00:59:02 |
OpenStack Infra |
cinder: status |
In Progress |
Fix Released |
|
| 2017-10-09 03:04:59 |
OpenStack Infra |
tags |
drivers netapp |
drivers in-stable-pike netapp |
|
| 2017-10-27 22:12:36 |
OpenStack Infra |
tags |
drivers in-stable-pike netapp |
drivers in-driverfixes-ocata in-stable-pike netapp |
|
| 2018-04-18 17:06:13 |
OpenStack Infra |
tags |
drivers in-driverfixes-ocata in-stable-pike netapp |
drivers in-driverfixes-ocata in-stable-ocata in-stable-pike netapp |
|
