Hi,
From a netplan point of view, it's a bit of a tricky one. (Note that
I'm a netplan contributor but *not* a netplan maintainer or architect,
so take this as unofficial.)
I haven't tested pacemaker specifically, but I can replicate the
disappearance of addresses easily[*].
I think it's systemd
On Wed, Oct 17, 2018 at 01:24:03AM +0200, Harald Weidner wrote:
> Hello,
>
> > Currently netplan removes interfaces it does not manage on any
> > change (netplan apply).
> >
> > Please point me to some recommendations for implementing a high
> > availability cluster or pair in Bionic with IP fail
Hello,
> Currently netplan removes interfaces it does not manage on any
> change (netplan apply).
>
> Please point me to some recommendations for implementing a high
> availability cluster or pair in Bionic with IP fail over.
I think the easiest solution is to replace Netplan by ifupdown(2)
or s
Replying to myself :)
Looks like newer versions of keepalived actively put back floating
VIPs if something else rudely removes them:
https://answers.launchpad.net/ubuntu/+question/670475
https://launchpad.net/~hnakamur/+archive/ubuntu/keepalived
Any plans on a newer version of keepalived to appe
Hello,
We have some systems still using keepalived or corosync/pacemaker
for high availability with IP fail over. Easiest case would be a
haproxy or nginx fail over pair.
Currently netplan removes interfaces it does not manage on any
change (netplan apply).
Please point me to some recommendatio
Hello Ubuntu Server,
The purpose of this communication is to provide a status update and
highlights for any interesting subjects from the Ubuntu Server Team. If
you would like to reach the server team, you can find us at
the #ubuntu-server channel on Freenode. Alternatively, you can sign up
and us
