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

Slight accelerate mode page simplification.

Browse source
This commit is contained in:
Michael DeHaan 2013-10-02 21:59:08 -04:00
parent 8dd5a4f0b2
commit e9bd97ea4d
1 changed files with 6 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
docsite/latest/rst/playbooks_acceleration.rst
View file

@ -4,12 +4,15 @@ Accelerated Mode
.. versionadded:: 1.3
While SSH using the ControlPersist feature is quite fast and scalable, there is a certain amount of overhead involved in
creating connections. This can become something of a bottleneck when the number of hosts grows into the hundreds or
thousands. To help overcome this, Ansible offers an accelerated connection option. Accelerated mode can be anywhere from
using SSH connections.
Accelerate mode is there to help connections work faster, but still uses SSH for initial secure key exchange.
Accelerated mode can be anywhere from
2-6x faster than SSH with ControlPersist enabled, and 10x faster than paramiko.
Accelerated mode works by launching a temporary daemon over SSH. Once the daemon is running, Ansible will connect directly
to it via a raw socket connection. Ansible secures this communication by using a temporary AES key that is uploaded during
to it via a socket connection. Ansible secures this communication by using a temporary AES key that is uploaded during
the SSH connection (this key is different for every host, and is also regenerated every time the daemon is started). By default,
Ansible will use port 5099 for the accelerated connection, though this is configurable. Once running, the daemon will accept
connections for 30 minutes, after which time it will terminate itself and need to be restarted over SSH.