Remove inherited configuration options invalid for charm
The shared OVN code that previously was distributed using the
OVN layer is now in c-h. The ovn-central charm does not have
common code with the chassis charms so it is safe to switch to
consuming the openstack layer directly.
Add version agnostic and fail safe helpers for cluster and
northd status.
Adapt to ``layer-ovn`` replacement of custom_property with
configuration adapter.
Ignore unsupported configuration options from ``layer-ovn``,
remove redundant deletion of configuration options already
deleted for us by ``layer-ovn``.
The UFW default allow calls result in all existing firewall rules
being removed and reinstated. Due to the side effect of active
connections being terminated we only want to do this once.
Actions: Move concrete charm module to works with layer-openstack
This patchset fixes the reference bug by moving the concrete charm class
module to lib/charm/openstack/ from lib/charms. This is so that the
bus.discover() function in layer-openstack [1] can find the concrete
class and instantiate it. The patchset is dependent on the layer-ovn
(linked below).
By default Open vSwitch ovsdb-server sends a inactivity probe
on client connections every 5 seconds. If no response is received
by the next time a probe would be sent the connection is termiated.
Depending on type of CMS and load the default of 5 seconds may not
be sufficient. Consequences of a dropped connection can be increased
load due to recalculation and can also interrupt in-flight requests
from the control plane.
The OpenStack Neutron OVN driver currently assumes a 60s probe
interval, so we align the charm default with that.
