> I think it's fine. It sounds like there will just be no way to
override package-installed blacklists any more. That's unfortunate, but
it's a very rare situation.
The i6300esb watchdog driver is required for every KVM/qemu virtual
machine with an emulated watchdog
(https://wiki.openstack.org/wik
> Note that the *proper* way to place eth0 into a bridge while also
being under systemd-networkd management is to create a .netdev for the
bridge and assign eth0 to it.
What is the recommended way for Ubuntu's OpenStack offering that
dynamically creates bridges (neutron-linuxbridge-agent)? Not usi
Public bug reported:
We are running an OpenStack installation from Ubuntu's Cloud Archive,
and our computer hosts have their network configured with systemd-
networkd. For example, a bond and several VLANs on top, including two
VLANs used for OpenStack flat networks. We are using neutron-
linuxbri
This backport to 18.04 LTS broke all our OpenStack compute nodes. We use
systemd-network to configure interfaces etc. and neutron-linuxbridge-
agent with some flat networks. In this scenario, the neutron agent
creates bridges for the flat networks and assigns them to physical
interfaces based on a
Thanks a lot for your work, Dan! Unfortunately, I wasn't able to pick up
the new bug from here, sorry for that. (It appears I did not get any
notification on your comments, need to check that)
The bridges are managed by OpenStack Neutron from Ubuntu cloud archives
and with names derived from the n
> > The fix was revered in bug #1929560, but the behavior will not be reverted
> > in newer releases. Therefore, every reload of systemd-networkd will remove
> > the physical network interface from neutrons bridge.
>
> It looks like the patch was backported to stable releases in that bug; not
>
6 matches
Mail list logo
