@bortzmeyer not sure there is anything that Salt does that Ansible can't do. They have a slightly different architecture too.
@bortzmeyer good question...
We are about to move to #ansible, should we stop?
@Vor Do you have reasons to move?
(cc @bortzmeyer)
@DaD @bortzmeyer
To #ansible ?
Yes, we're coming from the stone age :)
But for Network Devices, if #salt is a better alternative than #ansible, I'm interested to have some feedback.
@Vor I thought you wanted to move from #SaltStack to #Ansible.
We did some review last year to choose between them and we found some lack of documentation on #Ansible.
Both seems to be used directly by an operator but I configured a #SaltStack shedule to apply the configuration every 15mn à-la cfengine.
To be sure you need to test.
For what I see #Ansible is firstly designed for push, #SalStack for pull but both can use the two modes IIRC.
Regards
https://en.wikipedia.org/wiki/Promise_theory
(cc @bortzmeyer)
Thanks for the feedback Daniel.
@Vor but to be honest my view is a little bit biased 😉
(cc @bortzmeyer)
Not if it's working for you!
OpenStack contains more features but that does not mean you need them.
So unless you have a compelling reason to change, I'd say 'no'.
@bortzmeyer Faut vraiment être motivé pour repasser d'#Ansible à #SaltStack. As-tu géré un projet #SaltStack sur le long terme, avec montée de version majeure ?
@bersace Non, jamais. Juste lu un livre.
@bortzmeyer Be aware that with Salt, you can do salt-ssh, which, as far as I understand, works like Ansible.
So I would say yes ^^