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.
* align testing with antelope
* add new antelope bundles
* add antelope bundles to tests.yaml
* add antelope tests to osci.yaml and .zuul.yaml
* update build-on and run-on bases
* 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
The ovs package in kinetic+ (zed+) uses dh_installsystemd with
--no-start for ovsdb-server, ovs-vswitchd, and ovs-record-hostname.
this results in stop events rather than restart events. This
change updates the restart-services actions for this charm to
handle stop events.
