This allows specifying functions that further optimize the scheduling
of shares across backend stanzas.
This is needed due to a netapp-driver specific problem 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.
Closes-bug: #2073537
Change-Id: Ia151c50421e75282f633e0b004c2e6c1bda638f3
(cherry picked from commit 94a4d30901bf9edac08cdcb7363dcb42680e8c80)
(cherry picked from commit 5b8c04db1da67cdb22f137968d617bc29b9b9f53)
(cherry picked from commit b550021fe2372bcbb6482d9851e7d8aa9e6017d8)
(cherry picked from commit f500f4e03b189df42974f115018a7701d136d3e1)
(cherry picked from commit 9e0ffda8820e97d55710dd6cfe823f8e5986bf3f)
Tox 4.0.0 was recently released and it has several breaking changes.
We pin to < 4.0.0 here. We are planning to move forward only on the
master charm branches.
Tox is also pinned to < 4.0.0 for stable branches in upstream
openstack-zuul-jobs as well as in zosci-config. However, the
requires= section in the charm's tox.ini file ends up installing
tox>4, wiping out the zuul-pinned tox<4 that was already installed
installed. This patch fixes that.
Update the bundles to use the stable track, edge risk for yoga
The bundles for the yoga channel currently point to "latest/edge"
channel for all the charms. This update points the charms to the
appropriate channel for the charm being used, either from ceph,
openstack, ovn or the misc tracks.
- Set default branch for git review/gerrit.
- Switch tests to stable.
- Switch to using stable charm-helpers branch.
- Switch to using stable charm.openstack branch.
- Switch to using stable zaza, zaza-openstack-tests
branch
- (reactive charms) Add build.lock file
Adds necessary requirements, osci.yaml, charmcraft.yaml etc for
migrationg to charmhub. Additionally, adds xena and yoga tests and
updates the charm overlay for appropriate netapp values.
local_overlay_enabled is set to True as it now defaults to False.
Note that the actual functional tests are still disabled due to [1]
Charmcraft 1.0+ breaks py35 compatibility by introducing f-strings. As
the charms are still being built on a xenial builder, we currently need
to pin this for the builds.
