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)
This patch is to lock the stable/2023.1 (antelope release) charms
down so that as much as possible.
In particular, this patch does:
- set the .gitreview to stable/2023.1
- lock zaza and zaza-openstack-tests to stable/antelope branches
- for reactive charms Add build.lock files to lock the layers
and python modules used to build the charm.
- for ops framework charms, extract a pip freeze from the
charmcraft container after building the charm to lock the
modules used to build the charm.
- drop the kinetic bundles if the exist. (Note the updates to
tests.yaml is in another batch (topic: antelope-voting)
- update the bundles so that they point to the antelope specific
channels. e.g. 2023.1/edge for OpenStack charms, 23.03/edge for
OVN charms, quincy/edge for Ceph charms and generally, the
appropriate LTS Jammy branch for the various support charms.
Enable jammy-antelope voting and drop kinetic-zed tests
* Voting was turned on for jammy-antelope in the
project-template for charm-functional-jobs in zosci-config
* Voting for jammy-antelope bundles with non-standard names
is turned on in individual charms
* Kinetic-zed bundles/tests are removed
Change-Id: If1e623c5c495940c537ebf8b8e666945216f4138
(cherry picked from commit dfb225b51ed5ce6de29090b8828ad91e74742e4f)
* sync charm-helpers to classic charms
* change openstack-origin/source default to zed
* align testing with zed
* add new zed bundles
* add zed bundles to tests.yaml
* add zed tests to osci.yaml and .zuul.yaml
* update build-on and run-on bases
* add bindep.txt for py310
* sync tox.ini and requirements.txt for ruamel
* use charmcraft_channel 2.0/stable
* drop reactive plugin overrides
* move interface/layer env vars to charmcraft.yaml
