Ansible’s main goals are simplicity and ease-of-use.
usage of OpenSSH for transport with other transports and pull modes as alternatives
Ansible manages machines in an agent-less manner.
If needed, Ansible can easily connect with Kerberos, LDAP, and other centralized authentication management systems.
Ansible is an agentless automation tool that by default manages machines over the SSH protocol. Once installed, Ansible does not add a database, and there will be no daemons to start or keep running. You only need to install it on one machine and it can manage an entire fleet of remote machines from that central point. When Ansible manages remote machines, it does not leave software installed or running on them, so there’s no real question about how to upgrade Ansible when moving to a new version.
Control node requirements (控制节点)
Managed node requirements (被控节点)
"module_stdout": "/bin/sh: /usr/bin/python: No such file or directory\r\n"
This topic describes how to control Ansible settings.
Certain settings in Ansible are adjustable via a configuration file (ansible.cfg).
If installing Ansible from a package manager, the latest
ansible.cfg file should be present in /etc/ansible, possibly as a .rpmnew file (or other) as appropriate in the case of updates.
Starting with Ansible version 2.4, you can use the ansible-config command line utility to list your available options and inspect the current values.
Ansible also allows configuration of settings using environment variables. If these environment variables are set, they will override any setting loaded from the configuration file.
Not all configuration options are present in the command line, just the ones deemed most useful or common. Settings in the command line will override those passed through the configuration file and the environment.
配置文件设置优先级 Command line options << Environmental configuration << Configuration file
porting 在计算机英语中是 移植 的含义