Ansible and chef are configuration administration (CM) instruments that assist sysadmins and DevOps professionals handle numerous servers. They excel at repetitive activity automation, simultaneous deployment of apps and packages to a gaggle of servers or configuration and provisioning of recent servers from scratch.
Ansible vs Chef Infographic
What’s Ansible?
Ansible was launched in 2012 by its father or mother firm AnsibleWorks and has since gained a devoted following.
Ansible is written in Python and solely requires the Python libraries to be current on the servers to be configured, the default on nearly all Linux distros.
Ansible’s distinctive promoting factors are its light-weight, relative ease of use and pace of deployment in comparison with different CM instruments.
In distinction to Chef, you need not study Ruby to make use of Ansible. It is because Ansible packages all instructions into YAML modules known as playbooks.
This implies so long as your most popular language can output JSON modules, you need to use Ansible.
Ansible additionally does away with brokers, all master-agent communication is deal with by normal SSH instructions or the Paramiko module that gives a Python interface for SSH2.
It is a nice added bonus because of SSH’s in-built safety.
What’s Chef?
Chef was launched in 2009. It’s supported by father or mother sponsor OpsCode. It’s steadily in contrast and contrasted to different old-timer CM instruments like Puppet. Like Puppet, Chef is written within the Ruby programming language and its CLI makes use of a Ruby-based DSL. The software program could be run on a client-server or in a standalone known as Chef-solo.
Chef makes use of a master-agent mannequin and a grasp server. This implies a Chef set up requires a workstation to management the grasp. Brokers are put in from the workstation utilizing the knife software that makes use of SSH for deployment. From there, managed nodes authenticate with the grasp by means of certificates.
Chef brokers have to be configured to examine in with the grasp periodically and instantaneous master-to-agent rollout adjustments aren’t but attainable.
Chef configs are packaged into JSON recordsdata known as recipes.
Ansible vs Chef: The place Ansible Wins
Ansible is an easier method to the configuration administration work. It avoids the grasp and minions method utilized by different open supply configuration administration instruments like Chef.
Relatively than organising a client-server set up, Ansible makes use of an agentless structure. It is a totally different method Chef, which has one Chef server and quite a few Chef-client situations.
Ansible manages distant connections through SSH networking utilizing implementations corresponding to OpenSSH. SSH is broadly supported throughout cloud platforms together with AWS, Google Cloud and Microsoft Azure.
This leads to quicker deployments and reduces the complexity of configuration recordsdata.
For enterprises, Ansible Tower a premium product that has a web-based API and graphical stock administration software. Ansible Tower provides a user-friendly central dashboard the place you may see the standing of your servers, handle entry management and monitor job runs.
In addition to the decrease studying curve, Ansible is nearer to the naked metallic working system on the distant server. In contrast to CHef the place it’s essential to perceive Ruby area particular language (DSL), Ansible runs positive from the command line with instructions you’re conversant in. Alongside its easy YAML format for its playbooks.
This implies your instructions are simpler to purpose with and the efficiency on the machine is quick.
Deploying through VM pictures like VMWare or containerization through Docker is widespread for making constant environments simpler for DevOps engineers.
Ansible requires no consumer set up, eliminating one other efficiency penalty out of your utility deployment setup. In case your workforce is new to DevOps instruments, Ansible can cowl most use instances with out drowning the workforce in a sea of advanced orchestration.
Ansible additionally safeguards your DevOps workforce from configuration drift by means of idempotent configuration administration.
Ansible permits you to maintain the state of your servers constant sooner or later by working Ansible playbooks based mostly on Ansible’s stock replace coverage.
On future executions of a playbook, Ansible begins by “Gathering Facts” to determine when a specified change was carried out in an earlier run of the playbook.
This ensures, for instance, if a specified OS consumer or say, Github distant was already added, it will not be added once more sooner or later while you rerun the playbook.
State adjustments are solely executed if the specified state laid out in your playbook shouldn’t be met.
With its minimalist design, idempotency, and sticking as shut as attainable to pure SSH, Ansible wins out if you’d like the least intrusive deployment, orchestration, and configuration administration workflow.
Ansible vs Chef: The place Chef Wins
The unique use case for Chef at OpsCode once they launched their automation software in 2009. Regardless of the efficiency advantages and decrease studying curve of Ansible, there are use instances the place Chef is not only justifiable however preferable.
Chef’s Ruby DSL is an actual pleasure to work with for groups composed of a mixture of DevOps engineers and software program builders who use Ruby for the majority of their work.
DevOps engineers conversant in the Ruby and different crucial languages corresponding to Python, C++ and Java will likely be at house with Chef.
Whereas Ansible and YAML are simple to select up, the declarative paradigm is step faraway from on a regular basis crucial coding with Ruby, which is what Chef replicates properly.
As Ansible is “just SHH”, Chef is “just another Ruby DSL” so it presents little in the best way of obstacles to entry for a well-versed Rubyist.
The opposite massive benefit for Chef is its flexibility. That is as a result of distinctive energy of the DSL that composes Chef recipes and cookbooks, together with embedded Ruby (ERB) templates that present superior customization for numerous configuration recordsdata.
When you have a posh cloud deployment throughout platforms corresponding to Amazon EC2, Google Cloud, Azure and OpenStack with common schedules for server updates, Chef is a superb choice.
The most recent Chef open supply model 15.3.14 was launched on September 12 2019 and is on the market without cost.
There’s enterprise supported Chef Infra, Chef Examine, Chef Habitat and Chef Automate. Plans for these look as follows for 100-500 nodes:
Easy Infrastructure: $16,500/yr for the “Essentials” plan, which fits as much as 100 nodes, and $75,000/yr for the “Enterprise” choice, which fits to 500 nodes and offers Premium Assist.Enterprise Automation Stack: the “Essentials” plan prices $35,000/yr, with Commonplace Assist, aspect by aspect with the “Enterprise” plan, which is priced at $150,000/yr. Does Ansible or Chef Have Higher Assist?
Chef is an older product, so its documentation is healthier than Ansible’s.
That mentioned, the higher documentation could also be because of the truth that there’s extra to study than with Ansible.
Chef presents help for Linux, *nix and Home windows. The browser-based GUI is sweet however not as full as Puppet and is missing options like reporting and superior config choices.
Chef’s relative maturity means it might enchantment to firms who place a premium on stability greater than people. IT is legendary for avoiding documenting something, so it is no shock that Ansible’s documentation continues to be a weak level.
That is mitigated considerably by how simple it’s to study.
Ansible is simply obtainable for Linux and Unix and its GUI is worse than Chef’s, it would not sync to the CLI, so the GUI and CLI may give totally different outcomes.
Ansible’s agentless push-mode utilizing the ZeroMq implementation on the transport layer means fast deployment and low efficiency overhead, the caveat is it’s simply not as versatile and highly effective as utilizing brokers.
Ansible vs Chef vs Different Configuration Administration Instruments
Ansible and Chef vie for management with different notable configuration administration instruments like SaltStack, Terraform and Puppet among the many most notable.
These instruments serve the aim of provisioning and sustaining server farms in a predictable, time-saving trend whether or not hosted on-premise or on cloud platforms like Azure and AWS.
Giant scale deployment include distinctive challenges like sustaining functions, compliance necessities, patching, configuration drift and software program upgrades all pose a novel problem to DevOps groups.
DevOps instruments are inclined to fall into two classes:
Orchestration: Offers with provisioning servers and different infrastructure together with databases throughout clusters whereas handing over accountability for managing the software program working on the situations to configuration administration instruments.Configuration administration: Give attention to managing the software program on infrastructure nodes, together with set up and upgrades on servers already in existence
Different DevOps instruments:
SaltStack: Written in Python, SaltStack(Salt) holds your stock’s state on a grasp server, with YAML being the default format for storing configurations. SaltStack templates use the Jinja templating language, which will likely be acquainted to Python customers.Puppet: One other software on the configuration administration aspect, Puppet requires a grasp server, known as the Puppet grasp, which shops the configuration of your infrastructure and pushes adjustments out to shoppers. Like Ansible Tower, Puppet Enterprise comes with an online dashboard, Puppet Enterprise Console, for managing your stock.Terraform: A special method to each Ansible and Chef. Terraform focuses on organising your total infrastructure and provisioning servers. As such, it falls on the orchestration aspect of the spectrum, however it may be used alongside configuration targeted instruments like Chef and Ansible.
Many DevOps groups have discovered methods to combine and match CM instruments to go well with the complexity of their configuration and orchestration wants. Typically working on virtualization options corresponding to Docker containers, Vagrant, Kubernetes and others.
Containerization with Docker is an interesting path to go as a result of Docker containers assist ease the configuration course of whereas providing portability throughout numerous server working methods and cloud suppliers.
In some situations, options like Kubernetes or Docker can handle most of your configuration administration wants. As an example, Docker pictures can have all of your software program necessities put in.
It’s also attainable to make use of Ansible or Chef to deploy Docker containers and handle them, with prepared plugins obtainable within the type of a built-in Docker module on Ansible, and a Docker cookbook from the Chef Grocery store.
By way of recognition for particular person configuration administration instruments, Ansible is now forward of the pack, with a survey from TechRepublic displaying that Ansible had essentially the most widespread utilization throughout survey respondents, at 41%, adopted by Chef and Puppet in a tie at 31%, with Terraform at 31%, and Saltstack at 18%.
Conclusion
First off, any admin or DevOps will likely be mighty glad to have such instruments of their nook; just some years in the past there was a lot much less alternative on this area. Selecting both of them is a win, and your life will likely be richer and simpler for it.
That mentioned, if you happen to should select between them, contemplate your personal wants rigorously first and weigh them towards what every answer presents. You should utilize the infographic beneath to match Chef and Ansible.
