Keepalived and netplan

Rene Bakkum <[email protected]> Tue, 26 Jun 2018 12:37:01 +0200
Newsgroups	gmane.linux.keepalived.devel
Organization	True B.V.
Message-ID	<[email protected]>
This is a multi-part message in MIME format.
--===============2000180266718119886==
Content-Type: multipart/alternative;
 boundary="------------83B2C8E61C0E5B88E1B90A71"
Content-Language: en-US

This is a multi-part message in MIME format.
--------------83B2C8E61C0E5B88E1B90A71
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

Not sure if this would be the right list to post it, but I guess this is 
a good start.

When using Ubuntu 18.04 LTS the network configuration has changed from 
an interface file to netplan yaml configuration. The problem I am facing 
is that once I make changes in the netplan configuration and apply 
these, my keepalived IPs are removed from the IP list. Keepalived is 
still running in master mode and still has the idea all is fine, but the 
IPs he should keep running are not there anymore. Once I do a failover 
or restart the keepalived daemon on the server it will bring the 
interface back online. I could just stop using the netplan to apply new 
IPs and use the `ip addr` commands, but would be nice to add the IPs in 
the yaml configuration and have it available with reboots.

Just wondering what solution within keepalived are available?

Regards,
Rene Bakkum

--------------83B2C8E61C0E5B88E1B90A71
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <font face="Helvetica, Arial, sans-serif">Hi,<br>
      <br>
      Not sure if this would be the right list to post it, but I guess
      this is a good start.<br>
      <br>
      When using Ubuntu 18.04 LTS the network configuration has changed
      from an interface file to netplan yaml configuration. The problem
      I am facing is that once I make changes in the netplan
      configuration and apply these, my keepalived IPs are removed from
      the IP list. Keepalived is still running in master mode and still
      has the idea all is fine, but the IPs he should keep running are
      not there anymore. Once I do a failover or restart the keepalived
      daemon on the server it will bring the interface back online. I
      could just stop using the netplan to apply new IPs and use the `ip
      addr` commands, but would be nice to add the IPs in the yaml
      configuration and have it available with reboots. <br>
      <br>
      Just wondering what solution within keepalived are available?<br>
      <br>
      Regards,<br>
      Rene Bakkum<br>
    </font>
  </body>
</html>

--------------83B2C8E61C0E5B88E1B90A71--


--===============2000180266718119886==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
--===============2000180266718119886==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Keepalived-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/keepalived-devel

--===============2000180266718119886==--