When a VRRP instance is waiting for an IP address on the interface to
start, if the vip is added on the interface, keepalived ignores it and
remains in FAULT state, even if the VRRP instance is the system owner
(priority 255 and vip = system IP). However, when adding an IP address
different than the vip, the instance can change the state.

This makes nonsense for an instance is configured as the system owner
transit to FAULT state since the system has not yet the vip.
When the vip is added to the system, keepalived ignores it
and this instance remains in FAULT state, whereas an IP address
different than the vip can change the state of this instance.

Thus, do not ignore if a vip is added to the system when a VRRP
instance is configured with 255 priority.

Signed-off-by: Loïc Sang <[email protected]>

When a VRRP instance is waiting for an IP address on the interface to
start, if the vip is added on the interface, keepalived ignores it and
remains in FAULT state, even if the VRRP instance is the system owner
(priority 255 and vip = system IP). However, when adding an IP address
different than the vip, the instance can change the state.

This makes nonsense for an instance is configured as the system owner
transit to FAULT state since the system has not yet the vip.
When the vip is added to the system, keepalived ignores it
and this instance remains in FAULT state, whereas an IP address
different than the vip can change the state of this instance.

Thus, do not ignore if a vip is added to the system when a VRRP
instance is configured with 255 priority.

Signed-off-by: Loïc Sang <[email protected]>

Add a global option "vrrp_system_owner" to define the
behavior of a vrrp configured with 255 priority (system owner):

- The VRRP_FLAG_SYSTEM_OWNER_DFT is the current implementation.
A system owner instance can transit with any IP address on the physical
interafce. This is the default option when vrrp_system_owner is not defined.

- With VRRP_FLAG_SYSTEM_OWNER_ANY, a system owner instance can transit
with any VIP configured on the physical interface. To use, that define
"vrrp_system_owner any" in keepalived.conf.

- With VRRP_FLAG_SYSTEM_OWNER_STRICT, a system owner instance can
transit when all VIPs are configured on the physical interface.
To use that, define "vrrp_system_owner strict" in keepalived.conf.

Signed-off-by: Loïc Sang <[email protected]>

Add two more options for a vrrp instance with 255 priority (system owner)
i) Remain in fault state until all the VIPs have been added.
For that, set "vrrp_system_owner strict" in keepalived.conf.

ii) If any of the VIPs exists, add all the remaining VIPs.
For that, set "vrrp_system_owner any" in keepalived.conf.

iii) Go to MASTER state if there is an IP address on the VRRP instance's
interface (this it current implemenation).
This is the default behaviour, if vrrp_system_owner is not configured.

Signed-off-by: Loïc Sang <[email protected]>