The change this pulls in ensures that when service_resume is called (which
happens on every update-status hook), services are only enabled and started if
they are disabled and stopped respectively.
Also pins charmcraft to 2.2/stable since 2.5.5 throws an error building charmtools.
* Create build.lock file
* ensure tox.ini is from release-tools
* Locked requirements using pip-compile:
* existing (test-)requirements.txt ->
(test-)requirements.in
* pip-compile to *-py3[8|10].txt using python3.8
and python3.10.
* Updated tox.ini to use the appropriate merged
requirements-*.txt files.
* Removal of lunar from metadata, charmcraft.yaml
osci.yaml, tests.yaml and associated bundles.
* Locked libs and tests to stable/bobcat branches for:
* charm-helpers
* charms.openstack
* zaza
* zaza-openstack-tests
The OVN charms prepared for the upgrade from OVN 20.03 to newer
versions by enabling the version pinning by default.
Since then we have reached agreement with upstream that rolling
upgrades should work when upgrading within the previous upstream
LTS version and the next.
Having the pinning enabled by default causes unnecessary grief for
anyone already upgraded to OVN 22.03, so it's time to turn it off
by default.
We add a charm configuration option in case anyone wants to
upgrade across LTS boundaries in the future.
* sync charm-helpers to classic charms
* change openstack-origin/source default to bobcat
* add mantic to metadata series
* align testing with bobcat
* add new bobcat bundles
* add bobcat bundles to tests.yaml
* add bobcat tests to osci.yaml
* update build-on and run-on bases
* drop kinetic
* update charmcraft_channel to 2.x/edge
Add the 'docs' key and point it at a Discourse topic
previously populated with the charm's README contents.
When the new charm revision is released to the Charmhub,
this Discourse-based content will be displayed there. In
the absense of the this new key, the Charmhub's default
behaviour is to display the value of the charm's
'description' key.
