Netplan and high availability

Wed Nov 28 18:11:28 UTC 2018

Reading all this, it looks like reverting to ifupdown is the alternative until something changes.  However, when I tried to do that using a post on the web things appeared to work (no error messages) but networking got really weird - ping loss in the 20-50% range (and this was to my gateway on the same physical cable as my NIC).  Can someone point me to information on how to do this reliably?

Leroy Tennison
Network Information/Cyber Security Specialist
E: leroy at datavoiceint.com
2220 Bush Dr
McKinney, Texas
75070
www.datavoiceint.com
TThis message has been sent on behalf
of a company that is part of the Harris Operating Group of
Constellation Software Inc. These companies are listed
here
.
If you prefer not to be contacted by Harris
Operating Group
please notify us
.
This message is intended exclusively for the
individual or entity to which it is addressed. This communication
may contain information that is proprietary, privileged or
confidential or otherwise legally exempt from disclosure. If you are
not the named addressee, you are not authorized to read, print,
retain, copy or disseminate this message or any part of it. If you
have received this message in error, please notify the sender
immediately by e-mail and delete all copies of the
message.

________________________________________
From: ubuntu-server <ubuntu-server-bounces at lists.ubuntu.com> on behalf of cdmiller <cdmiller at adams.edu>
Sent: Wednesday, November 28, 2018 11:46 AM
To: ubuntu-server at lists.ubuntu.com
Subject: [EXTERNAL] Re: Netplan and high availability

Hello,

Thanks for all the responses, sorry for replying so late.

We utilize puppet so our current work around is to subscribe an exec
of keepalived to the exec for netplan.  A change in the netplan
config triggers cascading reloads, putting back the virtual IP.

We considered going back to ifupdown but we like the netplan yaml
syntax and try to minimize our deviations from baseline installs.

Not surprised systemd-networkd is the culprit.  IMO systemd treats
many server expectations as corner cases.  While sometimes annoying
it might delay the eventual AI take over of all sysadmin functions :)

Thanks,

- cameron

On 10/30/18 3:38 PM, James Hebden wrote:
> On Tue, Oct 30, 2018 at 09:17:58PM +0100, Harald Weidner wrote:
>> Hello,
>>
>> On Wed, Oct 17, 2018 at 11:09:07AM +1100, James Hebden wrote:
>>
>>> Do you get the same behaviour if you use an alias interface in your
>>> keepalived configuration? This configured keepalived to behave in a
>>> similar way to pacemaker/crm, in that it will create an secondary
>>> interface attached to the configured interface, which will be configured
>>> with the VIP.
>>>
>>> For example, if your interface is eth0, and you provide an alias of
>>> eth0:1, eth0:1 will be configured with the virtual IP, and eth0 will
>>> retain whichever IP is configured in your netplan if ifupdown
>>> configuration.
>>
>> I have tried this now, and it didn't help. After "netplan apply", all
>> of keepalived's virtual IP addresses are dropped, regardless of having a
>> label or not.
>
> Unfortunate - this means that netplan is also likely to clobber VIPs
> configured by other software too, for example, keepalived.
>
>>
>> Best regards,
>> Harald
>>
>> --
>> ubuntu-server mailing list
>> ubuntu-server at lists.ubuntu.com
>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
>> More info: https://wiki.ubuntu.com/ServerTeam
>

--
ubuntu-server mailing list
ubuntu-server at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam