Ansible目錄結構

安裝完成ansible後要知道ansible主要安裝的了什麼，安裝的目錄結構是什麼，每個目錄做什麼的

可以使用：rpm -ql ansible | less 來檢視ansible安裝的所有路徑
輸出的目錄比較多，主要分為下面幾類：
配置檔案目錄：   /etc/ansible
執行檔案目錄：  /usr/bin
lib庫依賴目錄：/usr/lib/python2.7/site-packages/ansible
help文件目錄：/usr/share/doc/ansible-2.7.5
man文件目錄：/usr/share/man/man1/

Ansible配置檔案

對於ansible的配置檔案，其實沒有過多的要了解的，因為ansible預設的配置檔案就是挺適合日常使用的了，一般情況下不需要進行過多的修改

ansible的配置檔案在安裝完成ansible後的 /etc/ansible/ansible.cfg 檔案

預設配置檔案如下:

# config file for ansible -- https://ansible.com/
# ===============================================

# nearly all parameters can be overridden in ansible-playbook
# or with command line flags. ansible will read ANSIBLE_CONFIG,
# ansible.cfg 
 
in the current working directory, .ansible.cfg in
# the home directory or /etc/ansible/ansible.cfg, whichever it
# finds first

[defaults]

# some basic default values...

#inventory      = /etc/ansible/hosts
#library        = /usr/share/my_modules/
#module_utils   = /usr/share/my_module_utils/
#remote_tmp     
 
= ~/.ansible/tmp
#local_tmp      = ~/.ansible/tmp
#plugin_filters_cfg = /etc/ansible/plugin_filters.yml
#forks          = 5
#poll_interval  = 15
#sudo_user      = root
#ask_sudo_pass = True
#ask_pass      = True
#transport      = smart
#remote_port    = 22
#module_lang    = C
#module_set_locale = False

# plays will gather facts by default, which contain information about
# the remote system.
#
# smart - gather by default, but don't regather if already gathered
# implicit - gather by default, turn off with gather_facts: False
# explicit - do not gather by default, must say gather_facts: True
#gathering = implicit

# This only affects the gathering done by a play's gather_facts directive,
# by default gathering retrieves all facts subsets
# all - gather all subsets
# network - gather min and network facts
# hardware - gather hardware facts (longest facts to retrieve)
# virtual - gather min and virtual facts
# facter - import facts from facter
# ohai - import facts from ohai
# You can combine them using comma (ex: network,virtual)
# You can negate them using ! (ex: !hardware,!facter,!ohai)
# A minimal set of facts is always gathered.
#gather_subset = all

# some hardware related facts are collected
# with a maximum timeout of 10 seconds. This
# option lets you increase or decrease that
# timeout to something more suitable for the
# environment.
# gather_timeout = 10

# Ansible facts are available inside the ansible_facts.* dictionary
# namespace. This setting maintains the behaviour which was the default prior
# to 2.5, duplicating these variables into the main namespace, each with a
# prefix of 'ansible_'.
# This variable is set to True by default for backwards compatibility. It
# will be changed to a default of 'False' in a future release.
# ansible_facts.
# inject_facts_as_vars = True

# additional paths to search for roles in, colon separated
#roles_path    = /etc/ansible/roles

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

# change the default callback, you can only have one 'stdout' type  enabled at a time.
#stdout_callback = skippy


## Ansible ships with some plugins that require whitelisting,
## this is done to avoid running all of a type by default.
## These setting lists those that you want enabled for your system.
## Custom plugins should not need this unless plugin author specifies it.

# enable callback plugins, they can output to stdout but cannot be 'stdout' type.
#callback_whitelist = timer, mail

# Determine whether includes in tasks and handlers are "static" by
# default. As of 2.0, includes are dynamic by default. Setting these
# values to True will make includes behave more like they did in the
# 1.x versions.
#task_includes_static = False
#handler_includes_static = False

# Controls if a missing handler for a notification event is an error or a warning
#error_on_missing_handler = True

# change this for alternative sudo implementations
#sudo_exe = sudo

# What flags to pass to sudo
# WARNING: leaving out the defaults might create unexpected behaviours
#sudo_flags = -H -S -n

# SSH timeout
#timeout = 10

# default user to use for playbooks if user is not specified
# (/usr/bin/ansible will use current user as default)
#remote_user = root

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

# default module name for /usr/bin/ansible
#module_name = command

# use this shell for commands executed under sudo
# you may need to change this to bin/bash in rare instances
# if sudo is constrained
#executable = /bin/sh

# if inventory variables overlap, does the higher precedence one win
# or are hash values merged together?  The default is 'replace' but
# this can also be set to 'merge'.
#hash_behaviour = replace

# by default, variables from roles will be visible in the global variable
# scope. To prevent this, the following option can be enabled, and only
# tasks and handlers within the role will see the variables there
#private_role_vars = yes

# list any Jinja2 extensions to enable here:
#jinja2_extensions = jinja2.ext.do,jinja2.ext.i18n

# if set, always use this private key file for authentication, same as
# if passing --private-key to ansible or ansible-playbook
#private_key_file = /path/to/file

# If set, configures the path to the Vault password file as an alternative to
# specifying --vault-password-file on the command line.
#vault_password_file = /path/to/vault_password_file

# format of string {{ ansible_managed }} available within Jinja2
# templates indicates to users editing templates files will be replaced.
# replacing {file}, {host} and {uid} and strftime codes with proper values.
#ansible_managed = Ansible managed: {file} modified on %Y-%m-%d %H:%M:%S by {uid} on {host}
# {file}, {host}, {uid}, and the timestamp can all interfere with idempotence
# in some situations so the default is a static string:
#ansible_managed = Ansible managed

# by default, ansible-playbook will display "Skipping [host]" if it determines a task
# should not be run on a host.  Set this to "False" if you don't want to see these "Skipping"
# messages. NOTE: the task header will still be shown regardless of whether or not the
# task is skipped.
#display_skipped_hosts = True

# by default, if a task in a playbook does not include a name: field then
# ansible-playbook will construct a header that includes the task's action but
# not the task's args.  This is a security feature because ansible cannot know
# if the *module* considers an argument to be no_log at the time that the
# header is printed.  If your environment doesn't have a problem securing
# stdout from ansible-playbook (or you have manually specified no_log in your
# playbook on all of the tasks where you have secret information) then you can
# safely set this to True to get more informative messages.
#display_args_to_stdout = False

# by default (as of 1.3), Ansible will raise errors when attempting to dereference
# Jinja2 variables that are not set in templates or action lines. Uncomment this line
# to revert the behavior to pre-1.3.
#error_on_undefined_vars = False

# by default (as of 1.6), Ansible may display warnings based on the configuration of the
# system running ansible itself. This may include warnings about 3rd party packages or
# other conditions that should be resolved if possible.
# to disable these warnings, set the following value to False:
#system_warnings = True

# by default (as of 1.4), Ansible may display deprecation warnings for language
# features that should no longer be used and will be removed in future versions.
# to disable these warnings, set the following value to False:
#deprecation_warnings = True

# (as of 1.8), Ansible can optionally warn when usage of the shell and
# command module appear to be simplified by using a default Ansible module
# instead.  These warnings can be silenced by adjusting the following
# setting or adding warn=yes or warn=no to the end of the command line
# parameter string.  This will for example suggest using the git module
# instead of shelling out to the git command.
# command_warnings = False


# set plugin path directories here, separate with colons
#action_plugins     = /usr/share/ansible/plugins/action
#cache_plugins      = /usr/share/ansible/plugins/cache
#callback_plugins   = /usr/share/ansible/plugins/callback
#connection_plugins = /usr/share/ansible/plugins/connection
#lookup_plugins     = /usr/share/ansible/plugins/lookup
#inventory_plugins  = /usr/share/ansible/plugins/inventory
#vars_plugins       = /usr/share/ansible/plugins/vars
#filter_plugins     = /usr/share/ansible/plugins/filter
#test_plugins       = /usr/share/ansible/plugins/test
#terminal_plugins   = /usr/share/ansible/plugins/terminal
#strategy_plugins   = /usr/share/ansible/plugins/strategy


# by default, ansible will use the 'linear' strategy but you may want to try
# another one
#strategy = free

# by default callbacks are not loaded for /bin/ansible, enable this if you
# want, for example, a notification or logging callback to also apply to
# /bin/ansible runs
#bin_ansible_callbacks = False


# don't like cows?  that's unfortunate.
# set to 1 if you don't want cowsay support or export ANSIBLE_NOCOWS=1
#nocows = 1

# set which cowsay stencil you'd like to use by default. When set to 'random',
# a random stencil will be selected for each task. The selection will be filtered
# against the `cow_whitelist` option below.
#cow_selection = default
#cow_selection = random

# when using the 'random' option for cowsay, stencils will be restricted to this list.
# it should be formatted as a comma-separated list with no spaces between names.
# NOTE: line continuations here are for formatting purposes only, as the INI parser
#       in python does not support them.
#cow_whitelist=bud-frogs,bunny,cheese,daemon,default,dragon,elephant-in-snake,elephant,eyes,\
#              hellokitty,kitty,luke-koala,meow,milk,moofasa,moose,ren,sheep,small,stegosaurus,\
#              stimpy,supermilker,three-eyes,turkey,turtle,tux,udder,vader-koala,vader,www

# don't like colors either?
# set to 1 if you don't want colors, or export ANSIBLE_NOCOLOR=1
#nocolor = 1

# if set to a persistent type (not 'memory', for example 'redis') fact values
# from previous runs in Ansible will be stored.  This may be useful when
# wanting to use, for example, IP information from one group of servers
# without having to talk to them in the same playbook run to get their
# current IP information.
#fact_caching = memory

#This option tells Ansible where to cache facts. The value is plugin dependent.
#For the jsonfile plugin, it should be a path to a local directory.
#For the redis plugin, the value is a host:port:database triplet: fact_caching_connection = localhost:6379:0

#fact_caching_connection=/tmp



# retry files
# When a playbook fails by default a .retry file will be created in ~/
# You can disable this feature by setting retry_files_enabled to False
# and you can change the location of the files by setting retry_files_save_path

#retry_files_enabled = False
#retry_files_save_path = ~/.ansible-retry

# squash actions
# Ansible can optimise actions that call modules with list parameters
# when looping. Instead of calling the module once per with_ item, the
# module is called once with all items at once. Currently this only works
# under limited circumstances, and only with parameters named 'name'.
#squash_actions = apk,apt,dnf,homebrew,pacman,pkgng,yum,zypper

# prevents logging of task data, off by default
#no_log = False

# prevents logging of tasks, but only on the targets, data is still logged on the master/controller
#no_target_syslog = False

# controls whether Ansible will raise an error or warning if a task has no
# choice but to create world readable temporary files to execute a module on
# the remote machine.  This option is False by default for security.  Users may
# turn this on to have behaviour more like Ansible prior to 2.1.x.  See
# https://docs.ansible.com/ansible/become.html#becoming-an-unprivileged-user
# for more secure ways to fix this than enabling this option.
#allow_world_readable_tmpfiles = False

# controls the compression level of variables sent to
# worker processes. At the default of 0, no compression
# is used. This value must be an integer from 0 to 9.
#var_compression_level = 9

# controls what compression method is used for new-style ansible modules when
# they are sent to the remote system.  The compression types depend on having
# support compiled into both the controller's python and the client's python.
# The names should match with the python Zipfile compression types:
# * ZIP_STORED (no compression. available everywhere)
# * ZIP_DEFLATED (uses zlib, the default)
# These values may be set per host via the ansible_module_compression inventory
# variable
#module_compression = 'ZIP_DEFLATED'

# This controls the cutoff point (in bytes) on --diff for files
# set to 0 for unlimited (RAM may suffer!).
#max_diff_size = 1048576

# This controls how ansible handles multiple --tags and --skip-tags arguments
# on the CLI.  If this is True then multiple arguments are merged together.  If
# it is False, then the last specified argument is used and the others are ignored.
# This option will be removed in 2.8.
#merge_multiple_cli_flags = True

# Controls showing custom stats at the end, off by default
#show_custom_stats = True

# Controls which files to ignore when using a directory as inventory with
# possibly multiple sources (both static and dynamic)
#inventory_ignore_extensions = ~, .orig, .bak, .ini, .cfg, .retry, .pyc, .pyo

# This family of modules use an alternative execution path optimized for network appliances
# only update this setting if you know how this works, otherwise it can break module execution
#network_group_modules=eos, nxos, ios, iosxr, junos, vyos

# When enabled, this option allows lookups (via variables like {{lookup('foo')}} or when used as
# a loop with `with_foo`) to return data that is not marked "unsafe". This means the data may contain
# jinja2 templating language which will be run through the templating engine.
# ENABLING THIS COULD BE A SECURITY RISK
#allow_unsafe_lookups = False

# set default errors for all plays
#any_errors_fatal = False

[inventory]
# enable inventory plugins, default: 'host_list', 'script', 'yaml', 'ini', 'auto'
#enable_plugins = host_list, virtualbox, yaml, constructed

# ignore these extensions when parsing a directory as inventory source
#ignore_extensions = .pyc, .pyo, .swp, .bak, ~, .rpm, .md, .txt, ~, .orig, .ini, .cfg, .retry

# ignore files matching these patterns when parsing a directory as inventory source
#ignore_patterns=

# If 'true' unparsed inventory sources become fatal errors, they are warnings otherwise.
#unparsed_is_failed=False

[privilege_escalation]
#become=True
#become_method=sudo
#become_user=root
#become_ask_pass=False

[paramiko_connection]

# uncomment this line to cause the paramiko connection plugin to not record new host
# keys encountered.  Increases performance on new host additions.  Setting works independently of the
# host key checking setting above.
#record_host_keys=False

# by default, Ansible requests a pseudo-terminal for commands executed under sudo. Uncomment this
# line to disable this behaviour.
#pty=False

# paramiko will default to looking for SSH keys initially when trying to
# authenticate to remote devices.  This is a problem for some network devices
# that close the connection after a key failure.  Uncomment this line to
# disable the Paramiko look for keys function
#look_for_keys = False

# When using persistent connections with Paramiko, the connection runs in a
# background process.  If the host doesn't already have a valid SSH key, by
# default Ansible will prompt to add the host key.  This will cause connections
# running in background processes to fail.  Uncomment this line to have
# Paramiko automatically add host keys.
#host_key_auto_add = True

[ssh_connection]

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

# The base directory for the ControlPath sockets.
# This is the "%(directory)s" in the control_path option
#
# Example:
# control_path_dir = /tmp/.ansible/cp
#control_path_dir = ~/.ansible/cp

# The path to use for the ControlPath sockets. This defaults to a hashed string of the hostname,
# port and username (empty string in the config). The hash mitigates a common problem users
# found with long hostames and the conventional %(directory)s/ansible-ssh-%%h-%%p-%%r format.
# In those cases, a "too long for Unix domain socket" ssh error would occur.
#
# Example:
# control_path = %(directory)s/%%h-%%r
#control_path =

# Enabling pipelining reduces the number of SSH operations required to
# execute a module on the remote server. This can result in a significant
# performance improvement when enabled, however when using "sudo:" you must
# first disable 'requiretty' in /etc/sudoers
#
# By default, this option is disabled to preserve compatibility with
# sudoers configurations that have requiretty (the default on many distros).
#
#pipelining = False

# Control the mechanism for transferring files (old)
#   * smart = try sftp and then try scp [default]
#   * True = use scp only
#   * False = use sftp only
#scp_if_ssh = smart

# Control the mechanism for transferring files (new)
# If set, this will override the scp_if_ssh option
#   * sftp  = use sftp to transfer files
#   * scp   = use scp to transfer files
#   * piped = use 'dd' over SSH to transfer files
#   * smart = try sftp, scp, and piped, in that order [default]
#transfer_method = smart

# if False, sftp will not use batch mode to transfer files. This may cause some
# types of file transfer failures impossible to catch however, and should
# only be disabled if your sftp version has problems with batch mode
#sftp_batch_mode = False

# The -tt argument is passed to ssh when pipelining is not enabled because sudo 
# requires a tty by default. 
#use_tty = True

# Number of times to retry an SSH connection to a host, in case of UNREACHABLE.
# For each retry attempt, there is an exponential backoff,
# so after the first attempt there is 1s wait, then 2s, 4s etc. up to 30s (max).
#retries = 3

[persistent_connection]

# Configures the persistent connection timeout value in seconds.  This value is
# how long the persistent connection will remain idle before it is destroyed.
# If the connection doesn't receive a request before the timeout value
# expires, the connection is shutdown. The default value is 30 seconds.
#connect_timeout = 30

# Configures the persistent connection retry timeout.  This value configures the
# the retry timeout that ansible-connection will wait to connect
# to the local domain socket. This value must be larger than the
# ssh timeout (timeout) and less than persistent connection idle timeout (connect_timeout).
# The default value is 15 seconds.
#connect_retry_timeout = 15

# The command timeout value defines the amount of time to wait for a command
# or RPC call before timing out. The value for the command timeout must
# be less than the value of the persistent connection idle timeout (connect_timeout)
# The default value is 10 second.
#command_timeout = 10

[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

# If set to yes, accelerate_multi_key will allow multiple
# private keys to be uploaded to it, though each user must
# have access to the system via SSH to add a new key. The default
# is "no".
#accelerate_multi_key = yes

[selinux]
# file systems that require special treatment when dealing with security context
# the default behaviour that copies the existing context or uses the user default
# needs to be changed to use the file system dependent context.
#special_context_filesystems=nfs,vboxsf,fuse,ramfs,9p

# Set this to yes to allow libvirt_lxc connections to work without SELinux.
#libvirt_lxc_noseclabel = yes

[colors]
#highlight = white
#verbose = blue
#warn = bright purple
#error = red
#debug = dark gray
#deprecate = purple
#skip = cyan
#unreachable = red
#ok = green
#changed = yellow
#diff_add = green
#diff_remove = red
#diff_lines = cyan


[diff]
# Always print diff when running ( same as always running with -D/--diff )
# always = no

# Set how many context lines to show in diff
# context = 3

上面的配置檔案是ansible 2.7.5的版本的(版本不同可能具體的內容也會有小小的變化)

一般情況下的配置檔案並不需要進行修改

下面對幾個我自己常用的設定進行解釋一下

預設配置
這裡的配置項有很多，這裡主要介紹一些常用的
[defaults]
#inventory      = /etc/ansible/hosts                        #被控端的主機列表檔案
#library        = /usr/share/my_modules/                    #庫檔案存放目錄
#remote_tmp     = ~/.ansible/tmp                            #臨時檔案遠端主機存放目錄
#local_tmp      = ~/.ansible/tmp                            #臨時檔案本地存放目錄
#forks          = 5                                         #預設開啟的併發數
#poll_interval  = 15                                        #預設輪詢時間間隔(單位秒)
#sudo_user      = root                                      #預設sudo使用者
#ask_sudo_pass = True                                       #是否需要sudo密碼
#ask_pass      = True                                       #是否需要密碼
#transport      = smart                                     #傳輸方式
#remote_port    = 22                                        #預設遠端主機的埠號
建議開啟修改以下兩個配置引數(取消掉註釋即可)
#host_key_checking = False                                  #檢查對應伺服器的host_key
#log_path=/var/log/ansible.log                              #開啟ansible日誌

Ansible系列命令

如何獲取Ansible的系列命令呢？

使用如下命令獲取:

[[email protected] ~]# ls /usr/bin/ | grep ansible | grep -v [0-9]
ansible
ansible-config
ansible-connection
ansible-console
ansible-doc
ansible-galaxy
ansible-inventory
ansible-playbook
ansible-pull
ansible-vault

下面我們對系列命令做一下簡單的瞭解:

ansible

ansible命令其實在運維工作中用的最多的命令，它的主要目的或者說是主要的應用場景是：在做臨時性的操作的時候(比如只想看看被控端的一臺主機或者多臺主機是否存活),在man中的定義是:run a command somewhere else
ansible通過ssh實現配置管理、應用部署、任務執行等功能，建議配置ansible端能基於金鑰認證的方式聯絡各個被管理節點

語法:ansible <host-pattern> [options]
選項引數：
使用ansible --help可以檢視到命令引數
這裡只寫一些常用的引數：
--version               #顯示版本
-m module               #指定使用的模組，預設為command
-v                      #檢視執行的詳細過程(-vv、-vvvv更詳細)
--list-hosts            #顯示主機列表(可以簡寫為--list)
-k,--ask-pass           #提示輸入ssh連線密碼，預設使用key驗證
-K,--ask-become-pass    #提示執行輸入sudo的密碼
-C,--check              #檢查，並不執行
-T,--timeout=TIMEOUT    #執行命令的超時時間，預設10s
-u,--user=REMOTE_USER   #指定遠端執行的執行使用者
-b,--become             #代替舊版本的sudo切換
-h,--help               #顯示使用幫助

ansible命令在運維工作中是尤為重要的在操作的時候結合ansible的模組(ansible-doc --list命令檢視模組)可以實現很多功能
ansible命令選項和常用模組詳細解釋:https://www.cnblogs.com/brianzhu/p/10174130.html

ansible-doc

ansible-doc是檢視ansible模組(外掛)文件說明，針對每個模組都有詳細的用法說明，功能和Linux的man命令類似

語法:ansible-doc [-l|-F|-s] [options] [-t <plugin type> ] [plugin]
引數:
-a, --all                                   #顯示文件所有的模組(這個選項有個bug)
-h, --help                                  #顯示使用幫助
-j, --json                                  #將所有的模組轉儲為JSON格式
-l, --list                                  #檢視模組列表
-F, --list_files                            #顯示模組的名稱和模組原路徑
-M MODULE_PATH, --module-path=MODULE_PATH   #
-s, --snippet                               #簡介的顯示模組的幫助資訊
-t TYPE, --type=TYPE                        #指定模組型別(預設為module)
-v, --verbose                               #檢視執行的詳細過程(-vv、-vvvv更詳細)
--version                                   #檢視版本

執行 ansible-doc 模組名  檢視模組的詳細資訊
示例:
檢視模組詳細資訊
[[email protected] ~]# ansible-doc ping
> PING    (/usr/lib/python2.7/site-packages/ansible/modules/system/ping.py)

        A trivial test module, this module always returns `pong' on successful contact. It does not make sense in playbooks, but it is useful from `/usr/bin/ansible' to verify the
        ability to login and that a usable Python is configured. This is NOT ICMP ping, this is just a trivial test module that requires Python on the remote-node. For Windows targets,
        use the [win_ping] module instead. For Network targets, use the [net_ping] module instead.

OPTIONS (= is mandatory):

- data
        Data to return for the `ping' return value.
        If this parameter is set to `crash', the module will cause an exception.
        [Default: pong]


NOTES:
      * For Windows targets, use the [win_ping] module instead.
      * For Network targets, use the [net_ping] module instead.

AUTHOR: Ansible Core Team, Michael DeHaan
        METADATA:
          status:
          - stableinterface
          supported_by: core
        

EXAMPLES:
# Test we can logon to 'webservers' and execute python with json lib.
# ansible webservers -m ping

# Example from an Ansible Playbook
- ping:

# Induce an exception to see what happens
- ping:
    data: crash

RETURN VALUES:


ping:
    description: value provided with the data parameter
    returned: success
    type: string
    sample: pong

檢視模組的簡單資訊
[[email protected] ~]# ansible-doc -s ping
- name: Try to connect to host, verify a usable python and return `pong' on success
  ping:
      data:                  # Data to return for the `ping' return value. If this parameter is set to `crash', the module will cause an exception.

ansible-doc命令在運維工作中也是尤為重要的我們在對模組進行了解學習的時候經常會用到
ansible-doc命令選項和常用模組詳細解釋:https://www.cnblogs.com/brianzhu/p/10174130.html

ansible-playbook

ansible-playbook是日常用的最多的命令，其工作機制是:通過讀取預先編寫好的playbook檔案實現批量管理，要實現的功能與命令ansbile一樣，可以理解為按一定的條件組成ansible的任務集
ansible-playbook命令後跟YML格式的playbook檔案，執行事先編排好的任務集

語法: ansible-playbook [options] playbook.yml [playbook2 ...]
引數：大部分的引數和ansible的引數一致
可以使用:ansible-playbook --help可以檢視到命令引數

ansible-playbook命令在運維工作中是使用的最多的
ansible-playbook詳細使用:https://www.cnblogs.com/brianzhu/p/10174123.html

ansible-galaxy

這個命令是一個下載網際網路上roles集合的工具(這裡提到的roles集合其實就是多個playbook檔案的集合)
roles集合所在地址:https://galaxy.ansible.com

使用方法：
語法:ansible-galaxy [delete|import|info|init|install|list|login|remove|search|setup] [--help] [options] ...
引數:
-h, --help                          #檢視命令幫助
-c, --ignore-certs                  #忽略SSL證書驗證錯誤
-s API_SERVER, --server=API_SERVER  #API伺服器地址          
-v, --verbose                       #檢視執行的詳細過程(-vv、-vvvv更詳細)                   
--version                           #檢視版本

示例:
搜尋roles
[[email protected] ~]# ansible-galaxy search nginx
檢視search的使用幫助
[[email protected] ~]# ansible-galaxy search --help

安裝roles
[[email protected] ~]# ansible-galaxy install geerlingguy.nginx
- downloading role 'nginx', owned by geerlingguy
- downloading role from https://github.com/geerlingguy/ansible-role-nginx/archive/2.6.2.tar.gz
- extracting geerlingguy.nginx to /root/.ansible/roles/geerlingguy.nginx
- geerlingguy.nginx (2.6.2) was installed successfully
上面可以看到實際上就是網際網路上的geerlingguy.nginx下載到本地的/root/.ansible/roles/中
檢視install的使用幫助
[[email protected] ~]# ansible-galaxy install --help

刪除roles
[[email protected] ~]# ansible-galaxy remove geerlingguy.nginx
這個步驟就是把/root/.ansible/roles/中的geerlingguy.nginx資料夾刪除
檢視remove的使用幫助
[[email protected] ~]# ansible-galaxy remove --help

列出安裝的roles
[[email protected] ~]# ansible-galaxy list
- geerlingguy.nginx, 2.6.2
檢視list的使用幫助
[[email protected] ~]# ansible-galaxy list --help
--------------------------------------------------------------------------------------------------------
溫馨提示:
ansible-galaxy的使用方法還有很多，在語法中可以看到能執行的操作，可以使用示例中的相同方法檢視各個功能的幫助資訊！！！
--------------------------------------------------------------------------------------------------------

ansible-pull

該指令設計到了ansible的另一種的工作模式:pull模式(ansible預設使用的是push模式)，這個和通常使用的push模式的工作機制正好相反(push拉取，pull推送)
ansible的pull模式適用於：
1) 你有數量巨大的機器需要配置，即使使用高併發執行緒依然需要花費大量的時間
2）你要在剛啟動的，沒有聯網的主機上執行ansible

語法:ansible-pull -U <repository> [options] [<playbook.yml>]
引數：大部分的引數和ansible的引數一直，因為不常用所有就不列舉了
可以使用 ansible-pull --help檢視具體的幫助
--------------------------------------------------------------------------------------------------------------------------------
溫馨提示:
ansible-pull通常在配置大批量的機器的場景下使用，靈活性有小小的欠缺，但效率幾乎可以無限的提升，對於運維人員的技術水平和前瞻性的規劃有很高要求！！！
--------------------------------------------------------------------------------------------------------------------------------

ansible-console

ansible自己的終端

語法：ansible-console [<host-pattern>] [options]
引數：大部分的引數和ansible的引數一直，因為不常用所有就不列舉了
可以使用:ansible-console --help 檢視幫助
使用示例:
對所有的被控端進行終端命令操作
[[email protected] ~]# ansible-console
Welcome to the ansible console.
Type help or ? to list commands.

[email protected] (3)[f:5]$ 

對/etc/ansible/hosts裡面定義的某個清單列表進行終端命令操作
[[email protected] ~]# ansible-console web
Welcome to the ansible console.
Type help or ? to list commands.

[email protected] (2)[f:5]$ 

exit命令退出終端

ansible-config

檢視，編輯管理ansible的配置檔案

語法：ansible-config [view|dump|list] [--help] [options] [ansible.cfg]
引數:
-c CONFIG_FILE, --config=CONFIG_FILE    #指定配置檔案所在的路徑
-h, --help                              #檢視幫助資訊
-v, --verbose                           #檢視執行的詳細過程(-vv、-vvvv更詳細)  
--version                               #檢視版本
-----------------------------------------------
溫馨提示:不常用(個人感覺)
-----------------------------------------------

ansible-connection

應該是個模組具體不知道幹什麼的

ansible-inventory

檢視被控制端主機清單的詳細資訊預設情況下它使用庫存指令碼,返回JSON格式

語法:ansible-inventory [options] [host|group]
引數:ansible-inventory --help 檢視
示例:
[[email protected] ~]# ansible-inventory --list
{
    "_meta": {
        "hostvars": {
            "192.168.192.129": {}, 
            "192.168.192.130": {}, 
            "192.168.192.131": {}
        }
    }, 
    "all": {
        "children": [
            "db", 
            "ungrouped", 
            "web"
        ]
    }, 
    "db": {
        "hosts": [
            "192.168.192.131"
        ]
    }, 
    "ungrouped": {}, 
    "web": {
        "hosts": [
            "192.168.192.129", 
            "192.168.192.130"
        ]
    }
}

ansible-vault

ansible-vault主要用於配置檔案的加密，如編寫的playbook配置檔案中包含敏感的資訊，不希望其他人隨便的看，ansible-vault可加密/解密這個配置檔案

語法:ansible-vault [create|decrypt|edit|encrypt|encrypt_string|rekey|view] [options] [vaultfile.yml]
引數:
--ask-vault-pass      ask for vault password
-h, --help                                          #檢視幫助資訊
--new-vault-id=NEW_VAULT_ID                         #設定用於rekey的新vault標識
--new-vault-password-file=NEW_VAULT_PASSWORD_FILE   #新的保險庫密碼檔案為rekey
--vault-id=VAULT_IDS                                #要使用的保險庫標識
--vault-password-file=VAULT_PASSWORD_FILES          #庫密碼檔案
-v, --verbose                                       #檢視執行的詳細過程(-vv、-vvvv更詳細)
--version                                           #檢視版本

示例:
新建一個yml的檔案，寫入一些資料
[[email protected] ~]# echo "1243" > test.yml
給test.yml設定密碼
[[email protected] ~]# ansible-vault encrypt test.yml 
New Vault password: 
Confirm New Vault password: 
Encryption successful
在次檢視test.yml檔案
[[email protected] ~]# cat test.yml 
$ANSIBLE_VAULT;1.1;AES256
62316362376261393235633834333861383330356365666362333165343164386464306134643537
3730616331656630383264373734666635386430343435640a613366623365353963623031613738
31376363336532323730383561663539313730646431646133336333303230313239643366383264
6137633461363937350a326166383662643239623931653231643039373364383664393035356336
3538
上面檢視到明顯被加密了
正確的檢視方式(解密檢視):
[[email protected] ~]# ansible-vault decrypt test.yml 
Vault password: 
Decryption successful
[[email protected] ~]# cat test.yml 
1243