Ansible預設安裝好後有一個配置檔案/etc/ansible/ansible.cfg，該配置檔案中定義了ansible的主機的預設配置部分，如預設是否需要輸入密碼、是否開啟sudo認證、action_plugins外掛的位置、hosts主機組的位置、是否開啟log功能、預設埠、key檔案位置等等。

具體如下：

[defaults]
# some basic default values...
hostfile       = /etc/ansible/hosts   \\指定預設hosts配置的位置
# library_path = /usr/share/my_modules/
remote_tmp     = $HOME/.ansible/tmp
pattern
 
        = *
forks          = 5
poll_interval  = 15
sudo_user      = root  \\遠端sudo使用者
#ask_sudo_pass = True  \\每次執行ansible命令是否詢問ssh密碼
#ask_pass      = True  \\每次執行ansible命令時是否詢問sudo密碼
transport      = smart
remote_port    = 22
module_lang    = C
gathering = implicit
host_key_checking = False    \\關閉第一次使用ansible連線客戶端是輸入命令提示
log_path
 
    = /var/log/ansible.log \\需要時可以自行新增。chown -R root:root ansible.log
system_warnings = False    \\關閉執行ansible時系統的提示資訊，一般為提示升級
# set plugin path directories here, separate with colons
action_plugins     = /usr/share/ansible_plugins/action_plugins
callback_plugins   = /usr/share/ansible_plugins/callback_plugins
connection_plugins
 
 = /usr/share/ansible_plugins/connection_plugins
lookup_plugins     = /usr/share/ansible_plugins/lookup_plugins
vars_plugins       = /usr/share/ansible_plugins/vars_plugins
filter_plugins     = /usr/share/ansible_plugins/filter_plugins
fact_caching = memory
[accelerate]
accelerate_port = 5099
accelerate_timeout = 30
accelerate_connect_timeout = 5.0
# The daemon timeout is measured in minutes. This time is measured
# from the last activity to the accelerate daemon.
accelerate_daemon_timeout = 30

本篇就結合一個示例對其進行下了解。我在對之前未連線的主機進行連結時報錯如下：

[[email protected]361way.com ~]# ansible test -a 'uptime'
10.212.52.14 | FAILED => Using a SSH password instead of a key is not possible because Host Key checking is enabled and sshpass does not support this.  Please add this host's fingerprint to your known_hosts file to manage this host.
10.212.52.16 | FAILED => Using a SSH password instead of a key is not possible because Host Key checking is enabled and sshpass does not support this.  Please add this host's fingerprint to your known_hosts file to manage this host.

從上面的輸出提示上基本可以瞭解到由於在本機的~/.ssh/known_hosts檔案中並有fingerprint key串，ssh第一次連線的時候一般會提示輸入yes 進行確認為將key字串加入到 ~/.ssh/known_hosts 檔案中。

方法1：

瞭解到問題原因為，我們瞭解到進行ssh連線時，可以使用-o引數將StrictHostKeyChecking設定為no，使用ssh連線時避免首次連線時讓輸入yes/no部分的提示。通過檢視ansible.cfg配置檔案，發現如下行：

[ssh_connection]
# ssh arguments to use
# Leaving off ControlPersist will result in poor performance, so use
# paramiko on older platforms rather than removing it
#ssh_args = -o ControlMaster=auto -o ControlPersist=60s

所以這裡我們可以啟用ssh_args 部分，使用下面的配置，避免上面出現的錯誤：

ssh_args = -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking＝no 

方法2：

在ansible.cfg配置檔案中，也會找到如下部分：

# uncomment this to disable SSH key host checking
host_key_checking = False  

預設host_key_checking部分是註釋的，通過開啟該行的註釋，同樣也可以實現跳過 ssh 首次連線提示驗證部分。由於配置檔案中直接有該選項，所以推薦用方法2 。

其他部分

由於官方給的說明比較詳細，同時ansible.cfg 檔案本身預設也有註釋提示部分，所以不做過多說明，這裡再舉個例子，預設ansible 執行的時候，並不會輸出日誌到檔案，不過在ansible.cfg 配置檔案中有如下行：

# logging is off by default unless this path is defined
# if so defined, consider logrotate
log_path = /var/log/ansible.log

同樣，預設log_path這行是註釋的，開啟該行的註釋，所有的命令執行後，都會將日誌輸出到/var/log/ansible.log 檔案，便於瞭解在何時執行了何操作及其結果，如下：

[[email protected]361way.com ansible]# cat /var/log/ansible.log
2015-05-04 01:57:19,758 p=4667 u=root |
2015-05-04 01:57:19,759 p=4667 u=root |  /usr/bin/ansible test -a uptime
2015-05-04 01:57:19,759 p=4667 u=root |
2015-05-04 01:57:20,563 p=4667 u=root |  10.212.52.252 | success | rc=0 >>
 01:57am  up 23 days 11:20,  2 users,  load average: 0.38, 0.38, 0.40
2015-05-04 01:57:20,831 p=4667 u=root |  10.212.52.14 | success | rc=0 >>
 02:03am  up 331 days  8:19,  2 users,  load average: 0.08, 0.05, 0.05
2015-05-04 01:57:20,909 p=4667 u=root |  10.212.52.16 | success | rc=0 >>
 02:05am  up 331 days  8:56,  2 users,  load average: 0.00, 0.01, 0.05

更多部分可以參看官方文件。