Do not start keepalived after installation about ansible-keepalived HOT 5 CLOSED

Hello,

Why would you want to NOT run it? Is there a good reason for that? As mentioned in the README, you should probably pass variables to the role to make it run fine, and define the VIPs for it.

It would be perfectly possible to add a new variable for this, but I'd rather avoid variable proliferation.

Should the README be updated to explain that more in detail? If yes, could you help us figure out what's not clear?

Thank you in advance.

from ansible-keepalived.

The problem is the start of the keepalived service directly after the installation of the keepalived package (at least on Ubuntu). This way the default configuration provided by the keepalived package is active directly after the installation of the package. I think it makes sense to not start the keepalived service after the installation of the keepalived package. The keepalived service should be started after the customized configuration / rollout of the template configuration file.

from ansible-keepalived.

Ok. I'll create a pull request this week end, and inform you here.

from ansible-keepalived.

Hello, here is a side note for transparency.
Basically everything will work if we do this, but we"ll break idempotency.
Before the install, we'll have to create a new file (task status: changed each time) and then remove it afterwards (task status: changed each time).

I don't like to add changed_when: False, but I think that's gonna be the best way of doing it. Except if you have another idea?

from ansible-keepalived.

Hello,

Could you try with the latest version, please?

Thank you in advance.

from ansible-keepalived.