Confirmed users
1,351
edits
ReleaseEngineering/How To/Use Ansible for AdHoc Updates: Difference between revisions
ReleaseEngineering/How To/Use Ansible for AdHoc Updates (view source)
Revision as of 20:26, 21 January 2015
, 21 January 2015note our commitment to moving to ansible
(how to run checkconfig) |
(note our commitment to moving to ansible) |
||
| Line 3: | Line 3: | ||
==Ansible== | ==Ansible== | ||
Ansible is an orchestration/configuration management system written in Python. Since we already have Puppet in place for configuration management, RelEng will only care about Ansible's orchestration oriented features. | Ansible is an orchestration/configuration management system written in Python. Since we already have Puppet in place for configuration management, RelEng will only care about Ansible's orchestration oriented features. Since Ansible has better support for our EC2 use cases, it is the preferred tool for all future non-puppet work (and fabric is deprecated). | ||
====You | ====You will want to use ansible for:==== | ||
* Quickly running a command against all ec2 instances | * Quickly running a command against all ec2 instances | ||
* Testing changes against a subset of all hosts | * Testing changes against a subset of all hosts | ||
* Gathering data on an ad hoc basis (grepping logs for instance) | * Gathering data on an ad hoc basis (grepping logs for instance) | ||
* any new automation development | |||
====Reasons to use Ansible:==== | ====Reasons to use Ansible:==== | ||