It's a push-model and not pull-model (nor is it a continuously running daemon that will enforce system state). While Ansible will also report when something needed changing, it only does this when you run the Ansible Playbook.
You can set configuration management authoritatively on the Puppet Master and then the agent will maintain that state on the systems and will provide reporting when it has to change something which can be wired up to alert monitoring to notify you when something's wrong. One thing that daemon provides you is continuous eventual consistency. On the flip side though Configuration Management tools such as Puppet generally have a daemon running on the nodes, which needs to be provisioned/bootstrapped (maybe with Ansible), which has it's advantages and disadvantages (which I won't debate here, it's largely out of scope). It as a tool gets compared to things like Puppet, Chef, and SaltStack because one of the many "types" of task you would automate more or less add up to configuration management. Effectively, Ansible is your "automation glue" to create and automate a process that you and your team might have otherwise had to do by hand. The main place where I see these tools in completely different light is that Ansible performs automation of tasks, those tasks can be one of many "type" of things that you don't really expect from a configuration management tool, such as IaaS provisioning (AWS, GCE, Azure, RAX, Linode, etc), physical network configuration (Cisco IOS/ASA, JunOS, Arista, VyOS, Netscaler, etc), virtual machine creation/management, physical load balancer configuration (F5 BigIP) and the list goes on. I don't consider them to be direct competitors they way they seem to get compared by tech journalists except for the fact that there's some overlap in their abilities to perform the functions you would want out of a configuration management tool: service/system state, configuration file templating, application lifecycle management, etc. I think this is largely opinionated and you'll get varied results depending on who you talk to but I think about it effectively like this:Īnsible is an automation tool and Puppet is a configuration management tool.
DEPLOYIT VS PUPPET FULL
In the interest of full disclosure, I'm an upstream community contributing developer to Ansible but I will do my best to keep my response neutral.
0 kommentar(er)
