The disk-allocation-ratio charm configuration option has no effect

[Frode Nordahl]

At Victoria the disk-allocation-ratio charm configuration option appears to have no effect:

It may be this is the case for earlier OpenStack versions as well, as I do not when the upstream behavior changed.

Having Nova re-create the resource provider by manually deleting them also has no effect.

ubuntu@cloud-benchmarking:~/deploy$ juju config nova-cloud-controller disk-allocation-ratio
16
ubuntu@cloud-benchmarking:~/deploy$ openstack resource provider list
+--------------------------------------+-------------------+------------+
| uuid | name | generation |
+--------------------------------------+-------------------+------------+
| faa0a1cd-44d6-4ff4-93a2-93e9b3a60b4d | node-fontana.maas | 2 |
| bf42f4c7-629d-4c96-b4f4-c4b5bbb08589 | node-laveran.maas | 2 |
| 0f74e156-24f8-4eaf-9682-1a30cbc04693 | node-husband.maas | 2 |
+--------------------------------------+-------------------+------------+
ubuntu@cloud-benchmarking:~/deploy$ openstack resource provider inventory list bf42f4c7-629d-4c96-b4f4-c4b5bbb08589
+----------------+------------------+----------+----------+----------+-----------+--------+
| resource_class | allocation_ratio | min_unit | max_unit | reserved | step_size | total |
+----------------+------------------+----------+----------+----------+-----------+--------+
| VCPU | 16.0 | 1 | 48 | 0 | 1 | 48 |
| MEMORY_MB | 1.5 | 1 | 257720 | 65536 | 1 | 257720 |
| DISK_GB | 1.0 | 1 | 365 | 0 | 1 | 365 |
+----------------+------------------+----------+----------+----------+-----------+--------+

A workaround could be to use the API to set the allocation_ratio, for example:
openstack resource provider inventory class set --allocation_ratio 16.0 --total 365 bf42f4c7-629d-4c96-b4f4-c4b5bbb08589 DISK_GB

[Nobuto Murata (nobuto)]

This might be the same topic with this one?
https://bugs.launchpad.net/charm-nova-compute/+bug/1677223
https://review.opendev.org/c/openstack/charm-nova-compute/+/717888