t-t-t-t-t/deployment-tool-ansible-puppet-chef-salt.md

Forked from jaceklaskowski/deployment-tool-ansible-puppet-chef-salt.md

Created January 13, 2020 07:49

Star (0) You must be signed in to star a gist
Fork (0) You must be signed in to fork a gist

Select an option

Learn more about clone URLs
Clone this repository at <script src="https://gist.github.com/t-t-t-t-t/68089ac75c684695ced94e60ad8fc03a.js"></script>
Save t-t-t-t-t/68089ac75c684695ced94e60ad8fc03a to your computer and use it in GitHub Desktop.

Download ZIP

Choosing a deployment tool - ansible vs puppet vs chef vs salt

Raw

deployment-tool-ansible-puppet-chef-salt.md

Requirements

no upfront installation on remote/slave machines - ssh should be enough
configuration templating
environment requires/asserts, i.e. we need a JVM in a given version before doing deployment

Candidates

Ansible, Chef, Puppet, Salt

Excerpts from the net

What is difference between docker, puppet, chef and vagrant?:

turns the configuration of an environment in to source code.
That code can then be managed from within a VCS such as git or SVN so that changes are attempted, shared, rolled forward and rolled back in a much more frictionless way than the traditional written specification documents or word-of-mouth configuration sharing (e.g. do this .... now try that ... no, OK then try this) described beautifully in Gene Kim's book The Phoenix Project.

Ansible

Seems the choice of many that gets me curious what others offer in the space.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment