Hello!
I have a question that derives from the comparison Ansible vs. Salt.
As Ansible relies on SSH connection some people say that this has a
downside for a scenario like
- mass deployment of 1000 servers
Can you confirm that there's a severe performance impact when Ansible
master must
I suggest you start with reading about
http://docs.ansible.com/ansible/latest/intro_configuration.html#forks
On Wed, Feb 14, 2018 at 10:23 AM, cmonty14 <74cmo...@gmail.com> wrote:
> Hello!
>
> I have a question that derives from the comparison Ansible vs. Salt.
>
> As Ansible relies on SSH connec
This means there's no drawback with regards to performance when using
Ansible in a landscape with +1000 servers?
Am Mittwoch, 14. Februar 2018 19:36:22 UTC+1 schrieb Andrew Latham:
>
> I suggest you start with reading about
> http://docs.ansible.com/ansible/latest/intro_configuration.html#forks
Hey,
combined with the aforementioned forks configuration it all depends on your
Controll-Hosts capability to handle that many connections at the same time.
I dont think that ansible would be the bottleneck here but the saturation
of your network.
Regards
Am Donnerstag, 15. Februar 2018 11:2
Correct, Ansible is not the limit. Saltstack has guidelines around the same
bottle necks for its ssh only solution.
On Thu, Feb 15, 2018 at 5:15 AM, Manuel Schmidt
wrote:
> Hey,
>
> combined with the aforementioned forks configuration it all depends on
> your Controll-Hosts capability to handle
Could you please share some info how to mitigate the risk of a bottleneck
caused by SSH and/or the underlying network?
Am Donnerstag, 15. Februar 2018 16:37:53 UTC+1 schrieb Andrew Latham:
>
> Correct, Ansible is not the limit. Saltstack has guidelines around the
> same bottle necks for its ssh