| 2024-07-18 20:09:09 |
Rodrigo Barbieri |
bug |
|
|
added bug |
| 2024-07-18 20:11:47 |
OpenStack Infra |
charm-manila-netapp: status |
New |
In Progress |
|
| 2024-07-19 12:20:06 |
Rodrigo Barbieri |
description |
Manila allows configuring the backend option goodness_function per backend stanza for optimizing backend balance. This option is not available in the charm. |
Manila allows configuring the backend option goodness_function per backend stanza for optimizing backend balance. This option is not available in the charm.
In case of NetApp, this is needed due to a problem in the driver when using SVM scoped accounts. It does not have enough permissions to obtain the total_capacity_gb information, so it cannot calculate utilization, and therefore the goodness_function always returns 50 and end up scheduling shares always to the same pool. |
|
| 2024-07-19 15:06:32 |
Alex Kavanagh |
charm-manila-netapp: importance |
Undecided |
Medium |
|
| 2024-08-02 14:12:26 |
Felipe Reyes |
bug task added |
|
charm-guide |
|
| 2024-08-02 14:40:09 |
Rodrigo Barbieri |
description |
Manila allows configuring the backend option goodness_function per backend stanza for optimizing backend balance. This option is not available in the charm.
In case of NetApp, this is needed due to a problem in the driver when using SVM scoped accounts. It does not have enough permissions to obtain the total_capacity_gb information, so it cannot calculate utilization, and therefore the goodness_function always returns 50 and end up scheduling shares always to the same pool. |
Manila allows configuring the backend option goodness_function per backend stanza for optimizing backend balance. This option is not available in the charm.
In case of NetApp, this is needed due to a problem in the driver when using SVM scoped accounts. It does not have enough permissions to obtain the total_capacity_gb information, so it cannot calculate utilization, and therefore the goodness_function always returns 50 and end up scheduling shares always to the same pool.
The goodness_function is necessary to overcome bug [1] where the driver is not reporting the utilization correctly due to the usage of SVM-scoped account, and therefore scheduling of shares is inefficient, requiring the use of a goodness_function to create a rule such as below based on free_capacity_gb to restore good enough scheduling while [1] is not fixed.
goodness_function = "(capabilities.free_capacity_gb / 1000)"
[1] https://bugs.launchpad.net/manila/+bug/2073599 |
|
| 2024-08-05 15:40:27 |
OpenStack Infra |
charm-manila-netapp: status |
In Progress |
Fix Committed |
|
| 2024-08-14 11:00:40 |
OpenStack Infra |
charm-guide: status |
New |
In Progress |
|
| 2024-08-14 14:59:34 |
OpenStack Infra |
tags |
|
in-stable-zed |
|
| 2024-08-14 17:46:46 |
OpenStack Infra |
tags |
in-stable-zed |
in-stable-yoga in-stable-zed |
|
