Comment 5 for bug 1822558

I think a part of the issue here is how ``neutron-openvswitch`` handles non-existent interfaces.

I the OPs deployment ``neutron-openvswitch`` is used on both physical machines (for things like ``nova-compute`` and ``neutron-gateway``) and in containers (for Octavia).

The latter does not have a bond interface nor does it need any connection to a ``data-port``.

The charm should gracefully handle this allowing the configuration to be valid for both classes of services.

It does already provide a alternative input mechanism by listing white listed mac-addresses used to automatically resolve the data-port, but I guess this can be tedious for the deployer/operator in the case of all machines being equal except for a few units.