mirror of
https://github.com/ansible-collections/community.general.git
synced 2026-05-04 20:32:45 +00:00
Docs rebuild
This commit is contained in:
4
faq.html
4
faq.html
@@ -234,7 +234,7 @@ even bash ... just return some output in JSON format. You don’t need to k
|
||||
as it can. A system shouldn’t be half correct, especially if we’re planning on configuring
|
||||
other systems that depend on that system.</p>
|
||||
<p>Ansible also has a VERY short learning curve – but it also has less language constructs and
|
||||
does not create it’s own programming language. What constructs Ansible does have should be enough to cover 80% or so of the cases of most Puppet users, and it should scale equally well (not having a server is
|
||||
does not create its own programming language. What constructs Ansible does have should be enough to cover 80% or so of the cases of most Puppet users, and it should scale equally well (not having a server is
|
||||
almost like cheating).</p>
|
||||
<p>I also suspect some Ansible users will actually use Ansible to trigger Puppet – using the git
|
||||
module to checkout a Puppet module hierachy from source, and the command module to run
|
||||
@@ -284,7 +284,7 @@ run multiple commands in seperate forks, thanks to the magic behind
|
||||
Python’s multiprocessing module.</p>
|
||||
<p>If you need to address 500 machines you can decide if you want to try
|
||||
to contact 5 at a time, or 50 at a time.
|
||||
It’s up to you and how much power you can throw at it, but it’s heritage
|
||||
It’s up to you and how much power you can throw at it, but its heritage
|
||||
is about handling those kinds of use cases.</p>
|
||||
<p>There are no daemons so it’s entirely up to you. When you are aren’t using
|
||||
Ansible, it is not consuming any resources.</p>
|
||||
|
||||
Reference in New Issue
Block a user