Batch to add building by charmcraft for the ovn charms for the 20.03
batch.
build.lock: Update commit for layer-ovn
Fix UCA source in bundles
At present the bundles will not test what is on the tin.
The ovn-chassis charm is a subordinate charm and requires its
principle charm to configure the correct UCA pocket on the
unit. The magpie charm has grown a ``source`` configuration
option for this purpose.
* use stable/21.10 libraries
* use zaza/zaza-openstack-tests at stable/21.10
* build.lock files for reactive charms
* bundles refer to ~openstack-charms candidate channel
- add non-voting impish
- drop groovy bundle
- rebuild to pick up charm-helpers changes
- update tox/pip.sh to ensure setuptools<50.0.0
Note that this charm doesn't require interim OpenStack releases (e.g.
focal-ussuri, -xena, -victoria) as it isn't based on OpenStack releases.
The ovn-chassis charm doesn't have a source or openstack-origin. The
bionic-train and bionic-ussuri jobs are retained for historical
perspectives as they specify a PPA for the magpie charm in those
bundles.
The ovn-chassis charm consumes the sriov-netplan-shim Python
package as a wheel for its `pci` module which is used to render
the `/etc/sriov-netplan-shim/interfaces.yaml` configuration file
used for boot time configuration of SR-IOV VFs.
The package was recently updated and the chages are required for
the charm to correctly interpret sysfs information when used with
recent versions of the mlx5_core driver.
Setting the external_ids:ovn-match-northd-version value to
'true' will make the ovn-controller refrain from making updates to
the data plane tables in the event of a version mismatch.
This in combination with stopping the ovn-controller with the
ovn-ctl stop_controller --restart command will allow upgrades
to progress with little or no data plane downtime.
(Note that we will accomplish this by a separate proposal to the
OVN package itself in Ubuntu.)
As soon as the central components are upgraded ovn-controller will
notice and resume (re-)programming of the local Open vSwitch data
plane.
Block ovn-chassis units when incorrect bridge config is provided
The reason for this change is to have CI run functional tests
and to trigger a new charm publication. The actual changes are
in charm-helpers, charm-lyer-ovn and zaza-openstack-tests.
* rebuild
change uuid to trigger a new charm publication
