unable to configure goodness_function
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Charm Guide |
In Progress
|
Undecided
|
Unassigned | ||
OpenStack Manila NetApp Charm |
Fix Committed
|
Medium
|
Unassigned |
Bug 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.
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.
description: | updated |
Changed in charm-manila-netapp: | |
importance: | Undecided → Medium |
description: | updated |
Changed in charm-guide: | |
status: | New → In Progress |
Fix proposed to branch: master /review. opendev. org/c/openstack /charm- manila- netapp/ +/924438
Review: https:/