| Excerpt |
|---|
Configuration management tool to facilitate managing our (Linux) cluster head nodes, other Linux servers, and our Linux desktops. Works with other OSes (MacOS, Windows), but we'll first focus on Linux. |
...
Puppet
http://docs.puppetlabs.com/#puppetpuppet
...
NOTE: Read Read many ebooks for free using CU Library's access. Get CUL Passkey to facilitate access to cited books from off-campus. See details on this page's parent page.
...
Paraphrasing ansibleworks.com's web site: An "idempotent" “idempotent” resource model describes the desired state of computer systems and services, not the paths to get them to this state. Thus, no matter what state a system is in, this type of system understands how to transform it to the desired state (some also support a "dry run" “dry run” mode to preview needed changes). This allows reliable and repeatable IT infrastructure configuration, avoiding the potential failures from scripting and script-based solutions that describe explicit and often irreversible actions rather than the end goal.
...
- http://en.wikipedia.org/wiki/DevOps
- From "Puppet 3 Beginner's Guide", cited above:
- Devops write code, herd servers, build apps, scale systems, analyze outages, and fix bugs. With the advent of CM (configuration management) systems, devs and ops are now all just people who work with code.
Systems management
One of the functions of systems management is configuration management.
Artisan server crafting
From "Puppet 3 Beginner's Guide", cited above:
So the first problem with building servers by hand (artisan server crafting, as it's been called) is that it's complicated and tedious and it takes a long time. There's another problem. The next time you need to build an identical server, how do you do it, especially since your painstaking notes will no longer be up to date with reality.
Other configuration management tools (vs. Puppet)
...
From one person's comment to the "versus" article<http://bitfieldconsulting.com/puppet-vs-chef> above:
Chef will draw in Ruby developers because it's it’s not declarative, and because it's it’s easy.
My experience is that most developers don't don’t do declarative systems. Everyday languages are imperative, and when you're you’re a developer looking to get something deployed quickly, you're you’re most likely to pick the tool that suits your world view.
Systems Administrators tend to use more declarative tools (make, etc.)
Developers and Systems Administrators also have a divergent set of incentives. Developers are generally rewarded for delivering systems quickly, and SA's SA’s are rewarded for stability. IMHO, Chef is a tool to roll out something quickly, and Puppet is the one to manage the full lifecycle. That's That’s why I think Chef makes a good fit for cloud deployment because Vm instances have a short lifespan.
- Chef will draw in Ruby developers because it's it’s not declarative, and because it's it’s easy.
My experience is that most developers don't don’t do declarative systems. Everyday languages are imperative, and when you're you’re a developer looking to get something deployed quickly, you're you’re most likely to pick the tool that suits your world view.
Systems Administrators tend to use more declarative tools (make, etc.)
Developers and Systems Administrators also have a divergent set of incentives. Developers are generally rewarded for delivering systems quickly, and SA's SA’s are rewarded for stability. IMHO, Chef is a tool to roll out something quickly, and Puppet is the one to manage the full lifecycle. That's That’s why I think Chef makes a good fit for cloud deployment because Vm instances have a short lifespan.