search

platform9 / cctl

Apache License 2.0
47 stars 8 forks source link

Remove default for VIP interface name #59

Open dlipovetsky opened 6 years ago

dlipovetsky commented 6 years ago

The best way to avoid split-brain, or at least to minimise the impact, is NOT to use a dedicated link for the VRRP communication, but for the VRRP communication to use the same network interfaces that keepalived will add the virtual IP addresses to. In terms of how to configure this, ensure that you don't have any dev keywords in the virtual_ipaddress and virtual_ipaddress_excluded blocks. -- https://github.com/acassen/keepalived/issues/408#issuecomment-242923723

Keepalived and the API server should listen on the same interface. This interface can be discovered on the host, and does not need to be known by cctl.

sarun87 commented 6 years ago

Requiring keepalived and the API servier to listen on the same interface does not imply that this interface can be discovered on the machine. If a machine contains more than one interface, the administrator/user should have the ability to choose this interface for both keepalived & API server to use. There should be a way for the user to configure this interface and thus needs to be known by cctl.