This presentation "Chef vs Puppet vs Ansible vs Saltstack" will compare the DevOps configuration management tools Chef, Puppet, Ansible and Saltstack in terms of their capabilities, architecture, performance, ease of setup, language, scalability and pros and cons. The chef is a configuration management tool written in Ruby and Erlang. Puppet is an open-source software configuration management tool that runs on many Unix-like systems and also Windows. Ansible is yet another tool that automates software provisioning, configuration management, and application deployment. Saltstack is a Python-based open-source configuration management tool. Now, let us get started and get to know which is the best configuration management platform among Chef, Puppet, Ansible and Saltstack. Below are the contents of our "Chef vs Puppet vs Ansible vs Saltstack" configuration management tools comparison slides: 1) Need for Configuration Management Tools 2) Chef - Infrastructure, Architecture, Pros and Cons 3) Puppet- Infrastructure, Architecture, Pros and Cons 4) Ansible - Infrastructure, Architecture, Pros and Cons 5) Saltstack - Infrastructure, Architecture, Pros and Cons 6) Comparison on the basis of architecture, ease of setup, language, scalability, management and interoperability. Why learn DevOps? Simplilearn’s DevOps training course is designed to help you become a DevOps practitioner and apply the latest in DevOps methodology to automate your software development lifecycle right out of the class. You will master configuration management; continuous integration deployment, delivery and monitoring using DevOps tools such as Git, Docker, Jenkins, Puppet and Nagios in a practical, hands-on and interactive approach. The DevOps training course focuses heavily on the use of Docker containers, a technology that is revolutionizing the way apps are deployed in the cloud today and is a critical skillset to master in the cloud age. After completing the DevOps training course you will achieve hands-on expertise in various aspects of the DevOps delivery model. The practical learning outcomes of this Devops training course are: An understanding of DevOps and the modern DevOps toolsets The ability to automate all aspects of a modern code delivery and deployment pipeline using: 1. Source code management tools 2. Build tools 3. Test automation tools 4. Containerization through Docker 5. Configuration management tools 6. Monitoring tools Who should take this course? DevOps career opportunities are thriving worldwide. DevOps was featured as one of the 11 best jobs in America for 2017, according to CBS News, and data from Payscale.com shows that DevOps Managers earn as much as $122,234 per year, with DevOps engineers making as much as $151,461. Learn more at https://www.simplilearn.com/cloud-computing/devops-practitioner-certification-training

1. Chef versus Puppet versus Ansible versus SaltStack
Will be replaced with the actual cover slide

2. Meet Tim, a system administrator

3. When a server fails, Tim is responsible for
putting it back to its working state

4. When a server fails, Tim is responsible for
putting it back to its working state

5. But, what when multiple servers fail?

6. That’s what we have
configuration
management tools for!

7. With these tools, I can fix
all servers in a matter of
seconds

8. All I need to do is code my work and it will
be deployed automatically

9. So, which are these
tools?

10. Chef

11. Let’s get to know our contestants

12. Contestant 1- Chef

13. Introduction
Architecture
Pros and Cons
Chef ensures configurations are applied consistently in every
environment, at any scale, with infrastructure automation
Chef is an open source tool developed by Opscode written in Ruby and
Erlang
Chef is best suited for organizations that have a heterogenous
infrastructure and are looking for mature solutions

14. Introduction
Architecture
Pros and Cons

15. Introduction
Architecture
Pros and Cons
Pros Cons
• A large collection of recipes are
available

16. Introduction
Architecture
Pros and Cons
Pros Cons
• A large collection of recipes are
available
• Integrates well with Git which
provides a strong version control

17. Introduction
Architecture
Pros and Cons
Pros Cons
• A large collection of recipes are
available
• Integrates well with Git which
provides a strong version control
• A considerable amount of learning
time is required if one is not
comfortable with Ruby

18. Introduction
Architecture
Pros and Cons
Pros Cons
• A large collection of recipes are
available
• Integrates well with Git which
provides a strong version control
• A considerable amount of learning
time is required if one is not
comfortable with Ruby
• The main server doesn’t have much
control

19. Contestant 2 - Puppet

20. Introduction
Architecture
Pros and Cons
Puppet is a configuration management tool that supports automatic
deployment
Puppet is built in Ruby and uses DSL for writing manifests
Puppet also works well with a heterogeneous environment where the
focus is on scalability

21. Introduction
Architecture
Pros and Cons

22. Introduction
Architecture
Pros and Cons
Pros Cons
• Strong community support by Puppet
Labs

23. Introduction
Architecture
Pros and Cons
Pros Cons
• Strong community support by Puppet
Labs
• Well developed reporting mechanism

24. Introduction
Architecture
Pros and Cons
Pros Cons
• Strong community support by Puppet
Labs
• Well developed reporting mechanism
• For performing advance tasks, a
good knowledge of Ruby is required

25. Introduction
Architecture
Pros and Cons
Pros Cons
• Strong community support by Puppet
Labs
• Well developed reporting mechanism
• For performing advance tasks, a
good knowledge of Ruby is required
• The main server doesn’t have much
control

26. Contestant 3 - Ansible

27. Introduction
Architecture
Pros and Cons
Ansible is an IT automation tool that automates configuration
management, cloud provisioning, deployment and orchestration
The core of Ansible, playbooks, are written in YAML
Ansible works well with environments where the focus is on getting the
servers up and running quickly

28. Introduction
Architecture
Pros and Cons

29. Introduction
Architecture
Pros and Cons
Pros Cons
• Agent need not be installed on the
systems that require configuration

30. Introduction
Architecture
Pros and Cons
Pros Cons
• Agent need not be installed on the
systems that require configuration
• YAML is extremely easy to
understand and learn

31. Introduction
Architecture
Pros and Cons
Pros Cons
• Agent need not be installed on the
systems that require configuration
• YAML is extremely easy to
understand and learn
• Performance speed is often less than
other tools

32. Introduction
Architecture
Pros and Cons
Pros Cons
• Agent need not be installed on the
systems that require configuration
• YAML is extremely easy to
understand and learn
• Performance speed is often less than
other tools
• YAML is not as powerful as most
other languages

33. Contestant 4 - SaltStack

34. Introduction
Architecture
Pros and Cons
SaltStack is a CLI based tool that automates configuration management
and remote execution
SaltStack is Python based while the instructions are written in YAML or it’s
DSL
SaltStack is perfect for an environment with scalability and resilience as
its priority

35. Introduction
Architecture
Pros and Cons

36. Introduction
Architecture
Pros and Cons
Pros Cons
• Extremely simple usage once it’s set
up

37. Introduction
Architecture
Pros and Cons
Pros Cons
• Extremely simple usage once it’s set
up
• A good reporting mechanism that
allows one to easily view all
operations

38. Introduction
Architecture
Pros and Cons
Pros Cons
• Extremely simple usage once it’s set
up
• A good reporting mechanism that
allows one to easily view all
operations
• Setup phase is slightly tougher

39. Introduction
Architecture
Pros and Cons
Pros Cons
• Extremely simple usage once it’s set
up
• A good reporting mechanism that
allows one to easily view all
operations
• Setup phase is slightly tougher
• Relatively new web UI which is much
less developed as compared to other
tool

40. Let the race begin!

42. SaltStack
Server/ Client Server/ Client Server/ Client

44. SaltStack
Server/ Client Server/ Client Server/ Client

45. Language

46. Language
SaltStack
Server/ Client Server/ ClientServer/ Client

48. SaltStack
Server/ Client Server/ Client Server/ Client

50. SaltStack
Server/ Client Server/ Client Server/ Client

52. SaltStack
Server/ Client Server/ Client Server/ Client

54. SaltStack
Server/ Client Server/ Client Server/ Client

55. Communication

56. Communication
SaltStack
Server/ Client Server/ Client Server/ Client

57. So who wins?

58. Every tool has it’s pros and cons and each
serve specific environment requirements.

59. Note to instructor
Please explain the architecture of all the tools. As we have not covered SaltStack previously, here’s a brief
description on how it works.
Master- the controling system, where the admin sits
Minions- systems to be configured
State- a description of how you want the minion to be configured
Grain- the statis information about the minion. Example- CPU, OS, RAM
Pillars- The variables that could change between deployments. They state the new configurations required.
exampl- file paths, ports
The minions come with the grains, which are sent over to the master. the master checks the grains against the
pillars and state. The master then pushes the configurations onto the minions
At the end you could tell the viewers that the winner of the race depends on their requirements.
Thankyou