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
The config flags are a comma-seperated list of keys and values.
This enables an operator to pass arbitrary configuration into
the masakari-monitors configuration.
Updates to enable jammy and finalise charmcraft builds
- Add 22.04 to charmcraft.yaml
- Update metadata to include jammy
- Remove impish from metadata
- Update osci.yaml to include py3.10 default job
- Modify tox.ini to remove py35,py36,py37 tox target and add py310
target.
- ensure that the openstack-origin is yoga
Due to a build problem with the reactive plugin, this change falls back
on overriding the steps and doing a manual build, but it also ensures
the CI system builds the charm using charmcraft. Changes:
- add a build-requirements.txt
- modify charmcraft.yaml
- modify osci.yaml
-> indicate build with charmcraft
- modify tox.ini
-> tox -e build does charmcraft build/rename
-> tox -e build-reactive does the reactive build
- modify bundles to use the <charm>.charm artifact in tests.
and fix deprecation warning re: prefix
- tox inception to enable tox -e func-test in the CI
This corresponds to the upstream change titled:
"Use hostname to avoid clash with section".
This avoids a clash with the section of the same name.
An ussuri masakarimonitors.conf template is added that
uses the hostname config option. The base template continues
to use the host config option for older release, inline with
upstream.
This change also updates tox.ini, src/tox.ini, and adds pip.sh
from centrally managed release-tools.