ansible/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00
Code Releases Activity

Allude to ansible-pull, more docs coming later.

Browse source
This commit is contained in:
Michael DeHaan 2012-05-02 00:23:47 -04:00
parent 5954a7d8cc
commit 139a1324e9
1 changed files with 4 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
rst/index.rst
View file

@ -24,6 +24,10 @@ version of software if required.
Multi-machine software deployment is poorly solved by most systems management tools -- often due to architectural nature of being pull oriented and having complex ordering systems, they cover configuration but fail at deployment when updating tiers of machines in well defined steps. This results in using two (or more) logically distinct tools and having complex overlap between them.
If you actually do need pull oriented mode, though, Ansible 0.4 and later can run playbooks in pull mode as well.
This is useful in extreme scaling scenarios or when automatic system remediation is desired. Since Ansible remains
server and daemonless, scaling potential is unlimited, and no resources are wasted on running management daemons.
Deployment and Configuration, Unified
`````````````````````````````````````