mirror of
https://github.com/ansible/ansible-documentation.git
synced 2026-04-12 06:08:06 +07:00
feat: update the paramiko description
This commit is contained in:
@@ -354,12 +354,11 @@ when a term comes up on the mailing list.
|
||||
Ansible orchestration is all about modeling that kind of process.
|
||||
|
||||
paramiko
|
||||
By default, Ansible manages machines over SSH. The library that
|
||||
Ansible uses by default to do this is a Python-powered library called
|
||||
paramiko. The paramiko library is generally fast and easy to manage,
|
||||
though users who want to use Kerberos or Jump Hosts may wish to switch
|
||||
to a native SSH binary such as OpenSSH by specifying the connection
|
||||
type in their :term:`playbooks`, or using the ``-c ssh`` flag.
|
||||
By default, Ansible uses native OpenSSH, because it supports ControlPersist.
|
||||
If your control machine uses an older version of OpenSSH that does not support ControlPersist,
|
||||
Ansible will fall back to a Python implementation of OpenSSH called 'paramiko'.
|
||||
The paramiko library is generally fast and easy to manage. To use paramiko
|
||||
you need to specify the connection type in your :term:`playbooks`, or by using the ``-c paramiko`` flag.
|
||||
|
||||
Playbooks
|
||||
Playbooks are the language by which Ansible orchestrates, configures,
|
||||
|
||||
Reference in New Issue
Block a user