It’s been quite a journey, y’all.But we’re excited to announce the first release of OpenVox, the community-maintained open source implementation of Puppet.OpenVox 8.11 is functionally equivalent to...
I don’t frequent that world much these days, but I personally preferred the agent/pull model when I did. I can’t really articulate why, I think I feel comfortable knowing that the agent will run with the last known config on the machine, potentially correcting any misconfiguration even if the central host is down.
The big debate back in the day was Puppet vs. Chef (before Ansible/SaltStack). Puppet was more declarative, Chef more imperative.
I also admit, I don’t like YAML, other than for simple, mostly flat config and serializing.
I further admit that Ansible just has a bigger community these days, and that’s worth something. When I need to do a bit of CM these days, I use Ansible.
As someone that has never used Puppet, I also wonder this. Ansible is agentless and works on basically anything. What do you gain by requiring an agent, like with this?
Why not just use Ansible?
I don’t frequent that world much these days, but I personally preferred the agent/pull model when I did. I can’t really articulate why, I think I feel comfortable knowing that the agent will run with the last known config on the machine, potentially correcting any misconfiguration even if the central host is down.
The big debate back in the day was Puppet vs. Chef (before Ansible/SaltStack). Puppet was more declarative, Chef more imperative.
I also admit, I don’t like YAML, other than for simple, mostly flat config and serializing.
I further admit that Ansible just has a bigger community these days, and that’s worth something. When I need to do a bit of CM these days, I use Ansible.
As someone that has never used Puppet, I also wonder this. Ansible is agentless and works on basically anything. What do you gain by requiring an agent, like with this?