DevOps: Difference between revisions
Antonizoon (talk | contribs) No edit summary |
Antonizoon (talk | contribs) (→Puppet) |
||
Line 10: | Line 10: | ||
https://puppetlabs.com/puppet/puppet-enterprise | https://puppetlabs.com/puppet/puppet-enterprise | ||
We spend a lot of time building identical configurations on Debian servers. We might as well have a single server as the flagship and use it to automate update tasks. | |||
https://www.scriptrock.com/articles/puppet-vs.-chef-revisited | |||
https://www.digitalocean.com/community/tutorials/how-to-install-puppet-to-manage-your-server-infrastructure | |||
http://docs.puppetlabs.com/puppet/4.3/reference/install_linux.html | |||
=== Chef === | === Chef === |
Latest revision as of 20:28, 30 January 2018
DevOps: that hated buzzword designed to demand sysadmins that can program and do both for half the price.
But the concept of DevOps itself has real benefits, so let's look at them in depth.
Both Chef and Puppet are both programs to automate server operations. They use community-created cookbooks for anyone to use to automate installations of programs, maintenance, or scripts.
Puppet[edit]
Puppet is a DevOps approach to mass server configuration.
https://puppetlabs.com/puppet/puppet-enterprise
We spend a lot of time building identical configurations on Debian servers. We might as well have a single server as the flagship and use it to automate update tasks.
https://www.scriptrock.com/articles/puppet-vs.-chef-revisited
http://docs.puppetlabs.com/puppet/4.3/reference/install_linux.html
Chef[edit]
Chef is another competing approach.