chef, puppet & ansible - comparing leading configuration systems
TRANSCRIPT
![Page 1: Chef, Puppet & Ansible - Comparing Leading Configuration Systems](https://reader036.vdocument.in/reader036/viewer/2022062522/58cfc2e61a28ab7c6e8b4ad3/html5/thumbnails/1.jpg)
Chef, Puppet, & Ansible - Comparing Leading Configuration Systems
February 15th, 2017Ron Harnik - Product Marketing MgrAlex Green - Technical Content Writer
![Page 2: Chef, Puppet & Ansible - Comparing Leading Configuration Systems](https://reader036.vdocument.in/reader036/viewer/2022062522/58cfc2e61a28ab7c6e8b4ad3/html5/thumbnails/2.jpg)
Introduction
Alex GreenTechnical Content Writer
Ron HarnikProduct Marketing Manager
![Page 3: Chef, Puppet & Ansible - Comparing Leading Configuration Systems](https://reader036.vdocument.in/reader036/viewer/2022062522/58cfc2e61a28ab7c6e8b4ad3/html5/thumbnails/3.jpg)
Agenda• What are Orchestration Systems? • Chef, Puppet & Ansible - an overview• Demonstrate use cases for orchestration systems
![Page 4: Chef, Puppet & Ansible - Comparing Leading Configuration Systems](https://reader036.vdocument.in/reader036/viewer/2022062522/58cfc2e61a28ab7c6e8b4ad3/html5/thumbnails/4.jpg)
Scalr Architecture
![Page 5: Chef, Puppet & Ansible - Comparing Leading Configuration Systems](https://reader036.vdocument.in/reader036/viewer/2022062522/58cfc2e61a28ab7c6e8b4ad3/html5/thumbnails/5.jpg)
Enterprise Scopes
![Page 6: Chef, Puppet & Ansible - Comparing Leading Configuration Systems](https://reader036.vdocument.in/reader036/viewer/2022062522/58cfc2e61a28ab7c6e8b4ad3/html5/thumbnails/6.jpg)
Configuration Systems• This isn’t just writing scripts: Use dev. best practices like
version control, testing, batched deployments, use of design patterns
• Falls under Infrastructure As Code (Iaas): writing code to provision and manage your servers in addition to automating processes.
![Page 7: Chef, Puppet & Ansible - Comparing Leading Configuration Systems](https://reader036.vdocument.in/reader036/viewer/2022062522/58cfc2e61a28ab7c6e8b4ad3/html5/thumbnails/7.jpg)
Why Configuration Systems?• Reproduce a server for scaling or testing• Build systems to be platform independent • Clearly defined software/scripts • Dynamic configurations
![Page 8: Chef, Puppet & Ansible - Comparing Leading Configuration Systems](https://reader036.vdocument.in/reader036/viewer/2022062522/58cfc2e61a28ab7c6e8b4ad3/html5/thumbnails/8.jpg)
Why Configuration Systems?• Automatically configure monitoring when new systems
are built• Recover from a disaster quickly (by defining proper
application state should be)• Get new employees up to speed quickly
![Page 9: Chef, Puppet & Ansible - Comparing Leading Configuration Systems](https://reader036.vdocument.in/reader036/viewer/2022062522/58cfc2e61a28ab7c6e8b4ad3/html5/thumbnails/9.jpg)
Consider• Heavy planning prior to implementation such as choosing
the right tools• Bad configurations could get duplicated on all the servers• Configuration drift - when server configurations are
modified through hot-fixes without modifying the templates)
• Maintaining strict discipline isn’t easy
![Page 10: Chef, Puppet & Ansible - Comparing Leading Configuration Systems](https://reader036.vdocument.in/reader036/viewer/2022062522/58cfc2e61a28ab7c6e8b4ad3/html5/thumbnails/10.jpg)
Chef• Released in 2009• Written in Ruby - great for Developers and DevOps to
finally get along• The most popular of the orchestration/automation tools
on the market• Strong community and collection of resources (Chef
Supermarket)
![Page 11: Chef, Puppet & Ansible - Comparing Leading Configuration Systems](https://reader036.vdocument.in/reader036/viewer/2022062522/58cfc2e61a28ab7c6e8b4ad3/html5/thumbnails/11.jpg)
ChefGood:
• Easier to get productive and stay productive • Ideal for complex infrastructure work Bad:
• Chef takes onboarding time.• Collaboration doesn't scale well. • Runlist ordering can get messy
![Page 12: Chef, Puppet & Ansible - Comparing Leading Configuration Systems](https://reader036.vdocument.in/reader036/viewer/2022062522/58cfc2e61a28ab7c6e8b4ad3/html5/thumbnails/12.jpg)
Ansible• Released in 2012• Agentless structure• Super simple to use - written in python• Designed to be light
![Page 13: Chef, Puppet & Ansible - Comparing Leading Configuration Systems](https://reader036.vdocument.in/reader036/viewer/2022062522/58cfc2e61a28ab7c6e8b4ad3/html5/thumbnails/13.jpg)
Ansible Playbook Structure
![Page 14: Chef, Puppet & Ansible - Comparing Leading Configuration Systems](https://reader036.vdocument.in/reader036/viewer/2022062522/58cfc2e61a28ab7c6e8b4ad3/html5/thumbnails/14.jpg)
AnsibleGood:• Great for single point in time changes• Time to value is great - helps users define infrastructure
faster• Streamline the mundane tasks that sysadmins have to
endureBad:• Because over SSH, slow at scale
![Page 15: Chef, Puppet & Ansible - Comparing Leading Configuration Systems](https://reader036.vdocument.in/reader036/viewer/2022062522/58cfc2e61a28ab7c6e8b4ad3/html5/thumbnails/15.jpg)
Puppet• Released in 2005• Built for the enterprise, incredible support• Uses Client/Server Architecture like Chef• Puppet Master + Puppet Agents
![Page 16: Chef, Puppet & Ansible - Comparing Leading Configuration Systems](https://reader036.vdocument.in/reader036/viewer/2022062522/58cfc2e61a28ab7c6e8b4ad3/html5/thumbnails/16.jpg)
Puppet Enterprise UI
![Page 17: Chef, Puppet & Ansible - Comparing Leading Configuration Systems](https://reader036.vdocument.in/reader036/viewer/2022062522/58cfc2e61a28ab7c6e8b4ad3/html5/thumbnails/17.jpg)
PuppetGood:• Like Chef, Puppet is definitely the DevOps tool to define
and deploy company infrastructure to new servers• Tons of modules• Scales across teams wellBad:• Hard to pick up and experiment with • compared to chef, the terminology was more complicated
![Page 18: Chef, Puppet & Ansible - Comparing Leading Configuration Systems](https://reader036.vdocument.in/reader036/viewer/2022062522/58cfc2e61a28ab7c6e8b4ad3/html5/thumbnails/18.jpg)
Thank You!If you have any questions or feedback on using these configuration management systems feel free to reach out to us at [email protected] and [email protected].