Releases: evrardjp/ansible-keepalived
3.1.2
3.1 (The IT Crowd reference doesn't work anymore)
This release has the following included:
- New option keepalived_global_defs, which can be used for defining "enable_script_security" [1]
- Make the most recent PPAs work again
- Simplified, Improved and more extensive testing.
As usual, this is a minor release, not a patch release, so you can have downtime.
Pay attention to the new code! 2
[1]: When enable_script_security is not present in keepalived.conf,
the daemon will print a warning in the journal:
SECURITY VIOLATION - scripts are being executed but
script_security not enabled.
...3 !
Yup, 3.0.0 finally arrived.
This is the third "re-definition" of the role. The role was revamped for multiple OSes, with real life testing you could do by running vagrant up.
Keepalived is now functionally tested across our three mostly used OSes: centos, ubuntu trusty and ubuntu xenial.
This release also marks the move to a different branching/versioning model.
I used to loosely follow semver: http://semver.org/
From now the versioning is done like this:
-
The first number before the first dot ("MAJOR"), is marking a significant amount of ansible code changes that are not backwards compatible, like the current one.
-
The second number (between the first and second dot, alias "MINOR"), is, from now on, marking a bump of keepalived (example, bump the UCA version, change the PPA branch...).
-
The last number is for bug fixes intra series.
In a summary:
- if the last number changes, you're fine.
- if the second number changes, you can (and probably will) have keepalived downtime, and you should pay attention to the new code, it may introduce/fix keepalived bugs
- if the first number changes, you have to update your configuration.
Patch release 2.6.2
This patch release fixes the warmup that requires an int.
Thanks Robert Hecht!