OSDC 2017 | Is that an Ansible? Stop holding it like a Puppet by Felix Frank
•
0 likes•22 views
In the configuration management space, Puppet has positioned itself as the de facto industry standard. In recent years, however, competition has been growing, with Ansible taking a prominent place. Both tools share some commonalities, but there are quite severe differences in the respective user experience. Many operations professionals feel drawn to one over the other. But which is the right tool for you? How do you choose? And how do you get most out of your tool of choice? This session systematically gives you the insight needed to answer these questions for your organization.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to OSDC 2017 | Is that an Ansible? Stop holding it like a Puppet by Felix Frank
Similar to OSDC 2017 | Is that an Ansible? Stop holding it like a Puppet by Felix Frank (20)
Recently uploaded
Recently uploaded (20)
OSDC 2017 | Is that an Ansible? Stop holding it like a Puppet by Felix Frank
- 1. IS THAT AN ANSIBLE? STOP HOLDING IT LIKE A PUPPET. OSDC 2017, Berlin Felix Frank, Systems Architect The unbelievable Machine Company GmbH
- 2. WHAT? WHO NOW? Felix (probably not literally a cat) old command line geezer open source vagabond config management nerd came here by bicycle
- 3. A text
- 4. The pig go. The pig put foot. Grunt. The dove fly. The dove drop something. The pig disgusting. Rattle with dove. The pig leave. Produce is chicken wing. No Quack. Go is to the fountain. Foot in what? ketchup. Fly is in sky. The something on the pig. The pig rattle. The dove angry. The dove produce. With wing bark.
- 6. The story goes as follows.
- 21. Don't use blatantly wrong tools.
- 22. When all you have is a hammer, everything looks like a nail
- 23. NO QUACK.
- 24. Now for some items in the config management tool chain
- 27. Benefits of config management No manual tinkering. No wiki install guides.
- 28. Repeatable setup
- 30. Let's model a webserver
- 35. Ansible: Similar but different
- 39. Architecture: Puppet Master Agent Facter Agent Facter Agent Facter Manifest node A { include B } PuppetDB Hiera API Master API
- 40. Architecture: Ansible Ansible Initiator Host Playbook hosts: webtier roles: - apache Inventory Hosts [group A] ... [group B] Variables group A: { ... } ssh Host ssh Host ssh Host ssh
- 41. Naming Things is Hard Puppet Ansible resource type module module role role group (more or less) resource task
- 42. Working with: Puppet Editing code and data Puppet manifests Hiera data stores
- 43. class nodejs::install { $npmrc_auth = $::nodejs::npmrc_auth if $caller_module_name != $module_name { fail("Use of private class ${name} by ${caller_module_name}") } # npm is a Gentoo USE flag if $::operatingsystem == 'Gentoo' { package_use { $nodejs::nodejs_package_name: ensure => present, target => 'nodejs-flags', use => $nodejs::use_flags, before => Package[$nodejs::nodejs_package_name], } }
- 44. --- nodejs::npm_path: /opt/osdc/npm/bin/npm nodejs::manage_package_repo: false nodejs::repo_proxy: "10.17.81.121" nodejs::repo_proxy_username: sys nodejs::repo_proxy_password: o0psThisisS3cre3t apache::default_vhost: stage_site apache::user: fitz
- 45. Modules are available from the Puppet Forge
- 46. web1 db1 web2 Profile: apache_customer1 Profile: apache_customer2 Profile: nginx Profile: mysql nginx mysql io_tuning apache Roles Profiles Modules Custom code organized into Roles and Profiles
- 47. http://projects.theforeman.org/projects/foreman/wiki/Screenshots Optionally use ENCs like the Foreman
- 49. visualization with e.g. PuppetBoard
- 51. Working with: Ansible Write code in Ansible's YAML language: structure things into roles orchestrate roles across your infrastructure in playbooks
- 52. --- # roles/varnish/tasks/main.yml - name: Install the varnish package apt: name=varnish state=installed - name: Write varnish config files template: src={{ item.template }} dest={{ item.dest }} mode=0644 with_items: - dest: /etc/default/varnish src: etc_default_varnish.j2 - dest: /etc/varnish/default.vcl src: etc_varnish_default.vcl.j2 - name: Manage varnish service service: name=varnish state={{ varnish_service_state }}
- 53. --- # playbooks/webtier.yml - name: Provision webservers hosts: web roles: - common - apache - name: Provision reverse proxies hosts: proxies roles: - common - varnish
- 54. Open Source Roles from Ansible Galaxy
- 55. customize machines and groups using --- | --- # inventory/group_vars/all/vars.yml | # inventory/group_vars/web/vars.yml ssh_enabled: true | ssh_root_login: true ssh_root_login: false | | password_hashes: password_hashes: | root: "" root: "$6$deadbeef" | felix: "{{ password_hashes.felix }}" felix: "$6$acceff00" | gitlab_ssh_key: "{{ vault_gitlab_ssh_ke variables
- 56. Ansible Initiator Host Playbook hosts: webtier roles: - apache Inventory Hosts [group A] ... [group B] Variables group A: { ... } ssh Host ssh Host ssh Host ssh run from anywhere using ssh
- 57. http://projects.theforeman.org/projects/foreman/wiki/Screenshots Foreman supports Ansible as well
- 58. https://img.memecdn.com/youre-doing-it-wrong_o_195760.jpg not very comfortable without Ansible Tower
- 59. We've seen the parallels Nowforthedifferences
- 60. Puppet models systems system state will (should) converge equilibrium o en a er single transaction each machine has a definitive catalog of state
- 61. The Puppet Model
- 69. Ansible models distributed activity structured like a script, convergence is up to the user a play in a playbook is like a view or projection assigns tasks to hosts, rather than state
- 83. In Summary
- 84. Ansible v Puppet
- 85. Or let's use a metaphor
- 86. Imagine your infrastructure was a theatre stage
- 89. So don't try to push Ansible into a Puppet-shaped box. https://img.memecdn.com/youre-doing-it-wrong_o_195760.jpg
- 90. Some Ansible tips Having a site.yml is nice, but it should not be the primary use case. Running the code for all machines will become too slow sooner or later.
- 91. Tags aren't very flexible. Better to rely on single-purpose playbooks. Create ad-hoc playbooks whenever you need.
- 92. Don't shoot for DRY on playbook level. But do make DRY roles.
- 93. Take advice on best practices from the upstream Ansible documentation with a grain of salt.
- 94. Let's look at site.yml
- 95. Ansible in Puppet-like mode
- 103. Proper Ansible
- 112. When to choose Ansible over Puppet need to cover code deployments? primarily managing switches and similar gear? many use cases for "ad hoc" management? ubiquitous Python but no Ruby?
- 113. When to choose Puppet over Ansible managing only OS level system properties? very heterogeneous environment? you value power over simplicity? ubiquitous Ruby but no Python? (or Python 3 only?)
- 114. Should I combine both? Only if you know what you are doing. There is value in limiting your tool chain.
- 115. Finally, what's the best way to lead discussions about config management codes? Well...
- 118. We are filling many (not only tech) roles! Check out our careers page
- 119. Questions?
- 120. Testing tools Style Puppet Ansible Preview --noop --check Unit rspec-puppet N/A Static catalog-diff N/A Acceptance beaker testinfra
- 121. @felis_rex / ffrank Puppet vs. Ansible OSDC 2017 Attributions The Git logo, available under . The Jenkins logo: Creative Commons 3.0 https://jenkins.io/