安科网

ansible批量管理服务入门

onepiecedn

onepiecedn

2020-01-28

关注 关注

2020-01-17

此为ansible批量管理服务的第1个博客，发布博客为ansible批量管理服务入门

综合架构（二）——ansible批量管理服务

一ansible批量管理服务功能


01.可以实现批量系统操作配置
02.可以实现批量软件服务部署
03.可以实现批量文件数据分发
04.可以实现批量系统信息收集，资产管理

二ansible批量管理服务特点


01.管理端不需要启动服务程序（no server）
02.管理端不需要编写配置文件（/etc/ansible/ansible.cfg）
03.受控端不需要安装软件程序（libselinux-python）
04.受控端不需要启动服务程序（no agent）
05.服务程序管理操作模块众多（module）
06.利用剧本编写来实现自动化（playbook）

三批量管理软件安装部暑过程

[ ~]# yum install   -y ansible
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: mirrors.aliyun.com
 * extras: mirrors.aliyun.com
 * updates: mirrors.aliyun.com
base                                                   | 3.6 kB     00:00     
epel                                                   | 5.4 kB     00:00     
extras                                                 | 2.9 kB     00:00     
updates                                                | 2.9 kB     00:00     
(1/2): epel/x86_64/updateinfo                            | 1.0 MB   00:01     
(2/2): epel/x86_64/primary_db                            | 6.9 MB   00:02     
Package ansible-2.9.2-1.el7.noarch already installed and latest version
Nothing to do

涉及到的组件非常多

[ ~]# rpm  -ql  ansible   |  wc
  17280   17280 1446145
[ ~]# rpm  -ql  ansible   |  head
/etc/ansible
/etc/ansible/ansible.cfg
/etc/ansible/hosts
/etc/ansible/roles
/usr/bin/ansible
/usr/bin/ansible-2
/usr/bin/ansible-2.7
/usr/bin/ansible-config
/usr/bin/ansible-connection
/usr/bin/ansible-console
[ ~]# rpm  -ql  ansible   |  tail
/usr/share/doc/ansible-2.9.2/README.rst
/usr/share/man/man1/ansible-config.1.gz
/usr/share/man/man1/ansible-console.1.gz
/usr/share/man/man1/ansible-doc.1.gz
/usr/share/man/man1/ansible-galaxy.1.gz
/usr/share/man/man1/ansible-inventory.1.gz
/usr/share/man/man1/ansible-playbook.1.gz
/usr/share/man/man1/ansible-pull.1.gz
/usr/share/man/man1/ansible-vault.1.gz
/usr/share/man/man1/ansible.1.gz
[ ~]#

查看ansible的版本

版本很重要，因为有些服务的版本可能隔一段时间就会发生变化，相关的功能也会变化

[ ~]# ansible  --version
ansible 2.9.2
  config file = /etc/ansible/ansible.cfg
  configured module search path = [u‘/root/.ansible/plugins/modules‘, u‘/usr/share/ansible/plugins/modules‘]
  ansible python module location = /usr/lib/python2.7/site-packages/ansible
  executable location = /usr/bin/ansible
  python version = 2.7.5 (default, Oct 30 2018, 23:45:53) [GCC 4.8.5 20150623 (Red Hat 4.8.5-36)]

注意只能使用长格式查看

[ ~]# ansible  -V
usage: ansible [-h] [--version] [-v] [-b] [--become-method BECOME_METHOD]
               [--become-user BECOME_USER] [-K] [-i INVENTORY] [--list-hosts]
               [-l SUBSET] [-P POLL_INTERVAL] [-B SECONDS] [-o] [-t TREE] [-k]
               [--private-key PRIVATE_KEY_FILE] [-u REMOTE_USER]
               [-c CONNECTION] [-T TIMEOUT]
               [--ssh-common-args SSH_COMMON_ARGS]
               [--sftp-extra-args SFTP_EXTRA_ARGS]
               [--scp-extra-args SCP_EXTRA_ARGS]
               [--ssh-extra-args SSH_EXTRA_ARGS] [-C] [--syntax-check] [-D]
               [-e EXTRA_VARS] [--vault-id VAULT_IDS]
               [--ask-vault-pass | --vault-password-file VAULT_PASSWORD_FILES]
               [-f FORKS] [-M MODULE_PATH] [--playbook-dir BASEDIR]
               [-a MODULE_ARGS] [-m MODULE_NAME]
               pattern
ansible: error: too few arguments
[ ~]# ansible  -v
usage: ansible [-h] [--version] [-v] [-b] [--become-method BECOME_METHOD]
               [--become-user BECOME_USER] [-K] [-i INVENTORY] [--list-hosts]
               [-l SUBSET] [-P POLL_INTERVAL] [-B SECONDS] [-o] [-t TREE] [-k]
               [--private-key PRIVATE_KEY_FILE] [-u REMOTE_USER]
               [-c CONNECTION] [-T TIMEOUT]
               [--ssh-common-args SSH_COMMON_ARGS]
               [--sftp-extra-args SFTP_EXTRA_ARGS]
               [--scp-extra-args SCP_EXTRA_ARGS]
               [--ssh-extra-args SSH_EXTRA_ARGS] [-C] [--syntax-check] [-D]
               [-e EXTRA_VARS] [--vault-id VAULT_IDS]
               [--ask-vault-pass | --vault-password-file VAULT_PASSWORD_FILES]
               [-f FORKS] [-M MODULE_PATH] [--playbook-dir BASEDIR]
               [-a MODULE_ARGS] [-m MODULE_NAME]
               pattern
ansible: error: too few arguments

 ansible软件学习说明:
1) 掌握ansible主机清单配置:  指定ansible程序可以批量管理哪些主机
       https://docs.ansible.com/ansible/latest/user_guide/intro_inventory.html
2) 掌握ansible常用功能模块:  实现批量管理功能模块
       https://docs.ansible.com/ansible/latest/modules/modules_by_category.html
3) 掌握ansible剧本编写方法:  实现自动化批量管理功能
       https://docs.ansible.com/ansible/latest/user_guide/playbooks.html

四网站主机清单配置

（一）方式一：直接在配置文件/etc/ansible/hosts写入主机地址

[ ~]# tail  /etc/ansible/hosts

# Here‘s another example of host ranges, this time there are no
# leading 0s:

## db-[99:101]-node.example.com

172.16.1.7
172.16.1.8
172.16.1.31
172.16.1.41

m表示module

[ ~]# ansible  --help  |  grep  "\-m "
               [-a MODULE_ARGS] [-m MODULE_NAME]
  -m MODULE_NAME, --module-name MODULE_NAME

在命令行检测

ping 模块：测试主机之间的连通性

参考：https://docs.ansible.com/ansible/latest/modules/ping_module.html#ping-module

[ ~]# ansible  all -m  ping
172.16.1.41 | SUCCESS => {
    "ansible_facts": {
        "discovered_interpreter_python": "/usr/bin/python"
    }, 
    "changed": false, 
    "ping": "pong"
}
172.16.1.7 | SUCCESS => {
    "ansible_facts": {
        "discovered_interpreter_python": "/usr/bin/python"
    }, 
    "changed": false, 
    "ping": "pong"
}
172.16.1.31 | SUCCESS => {
    "ansible_facts": {
        "discovered_interpreter_python": "/usr/bin/python"
    }, 
    "changed": false, 
    "ping": "pong"
}
172.16.1.8 | SUCCESS => {
    "ansible_facts": {
        "discovered_interpreter_python": "/usr/bin/python"
    }, 
    "changed": false, 
    "ping": "pong"
}
[ ~]# ansible   172.16.1.8  -m    ping
172.16.1.8 | SUCCESS => {
    "ansible_facts": {
        "discovered_interpreter_python": "/usr/bin/python"
    }, 
    "changed": false, 
    "ping": "pong"
}
[ ~]# ansible   172.16.1.7  -m    ping
172.16.1.7 | SUCCESS => {
    "ansible_facts": {
        "discovered_interpreter_python": "/usr/bin/python"
    }, 
    "changed": false, 
    "ping": "pong"
}
[ ~]# ansible   172.16.1.31  -m    ping
172.16.1.31 | SUCCESS => {
    "ansible_facts": {
        "discovered_interpreter_python": "/usr/bin/python"
    }, 
    "changed": false, 
    "ping": "pong"
}
[ ~]# ansible   172.16.1.41  -m    ping
172.16.1.41 | SUCCESS => {
    "ansible_facts": {
        "discovered_interpreter_python": "/usr/bin/python"
    }, 
    "changed": false, 
    "ping": "pong"
}
[ ~]#

注意命令的顺序不能写错的

[ ~]# ansible  -m  172.16.1.7 ping
[WARNING]: Could not match supplied host pattern, ignoring: ping

[WARNING]: No hosts matched, nothing to do

[ ~]# ansible  -m  172.16.1.8   ping
[WARNING]: Could not match supplied host pattern, ignoring: ping

[WARNING]: No hosts matched, nothing to do

[ ~]#

（二）方式二：基于密码方式进行配置

参考官网，比较麻烦

把公钥删除，这是在受控端没有管理端的公钥的情况下配置的

以备份服务器为受控端

[ ~]# ip  a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:0c:29:b9:d6:60 brd ff:ff:ff:ff:ff:ff
    inet 10.0.0.31/24 brd 10.0.0.255 scope global noprefixroute eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::d2e4:6879:ac85:c625/64 scope link tentative noprefixroute dadfailed 
       valid_lft forever preferred_lft forever
    inet6 fe80::8c8d:c31b:a121:ca62/64 scope link tentative noprefixroute dadfailed 
       valid_lft forever preferred_lft forever
    inet6 fe80::9d5f:63cb:4c46:8ce7/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:0c:29:b9:d6:6a brd ff:ff:ff:ff:ff:ff
    inet 172.16.1.31/24 brd 172.16.1.255 scope global noprefixroute eth1
       valid_lft forever preferred_lft forever
    inet6 fe80::e654:55e2:8c88:ecfb/64 scope link tentative noprefixroute dadfailed 
       valid_lft forever preferred_lft forever
    inet6 fe80::5e65:529b:4fae:7fc3/64 scope link tentative noprefixroute dadfailed 
       valid_lft forever preferred_lft forever
    inet6 fe80::787b:a3a1:ead:b12e/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
[ ~]# ls  /root/.ssh/
authorized_keys
[ ~]# ll  /root/.ssh/
-bash: ll: command not found
[ ~]# ls  -l  /root/.ssh/  
total 4
-rw------- 1 root root 394 Jan 16 22:47 authorized_keys
[ ~]# cat  /root/.ssh/authorized_keys 
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDhE06kiM6UKlnZqGPBahZuAgq+LHdSssZrInWpkecC5buh2RRzl2NOiXCWNhEIwNgIJjLGsnITrTOyRsOel94oUYHR4iSPPhAe8yVuTZA8fS9ti1goIKt6/UYhi6bbNmFiqWPlSq1EIgpNvlWaDjHIchdIHR/lbgP3Wjg2PPI2QtzR5/SZJOI0g/GTJw1FDGXpYUlz608YTo79tl15zUAGT5rLiu5ugXY28HGQbPru5xA+BQZyzKu4jInllM8WzLimpFb7WX8HagwSU2S/Hx2+HSzEbMHXqz0tm8WbQogEO78gv0cJ6USq8vyc1ueq/Jn27gDu3ygPXtcSCn0XKpZJ
[ ~]# tail -1  /etc/ansible/hosts 
172.16.1.31
[ ~]#  ansible  172.16.1.31 -m  ping
172.16.1.31 | SUCCESS => {
    "ansible_facts": {
        "discovered_interpreter_python": "/usr/bin/python"
    }, 
    "changed": false, 
    "ping": "pong"
}

删除受控端的管理端对应的公钥

[ ~]# rm  -f  /root/.ssh/authorized_keys
[ ~]# ls  /root/.ssh/authorized_keys
ls: cannot access /root/.ssh/authorized_keys: No such file or directory

此时管理端要输入密码才可以登录到受控端

[ ~]# ssh  172.16.1.31
172.16.1.31‘s password: 
Last login: Sun Jan 26 17:30:17 2020 from 172.16.1.61
[ ~]# exit 
logout
Connection to 172.16.1.31 closed.

修改配置文件并且进行

[ ~]# tail -1  /etc/ansible/hosts 
172.16.1.31  ansible_user=root  ansible_password=123456  ansible_port=22
[ ~]#  ansible  172.16.1.31 -m  ping
172.16.1.31 | SUCCESS => {
    "ansible_facts": {
        "discovered_interpreter_python": "/usr/bin/python"
    }, 
    "changed": false, 
    "ping": "pong"
}

 ansible批量管理服务入门

（三）方式三: 采用主机组方式配置

分组进行操作，和班级进行分组管理一样，管理起来更加方便

[ ~]# tail  /etc/ansible/hosts

## db-[99:101]-node.example.com

[web]
172.16.1.7
172.16.1.8
[nfs]
172.16.1.31
[backup]
172.16.1.41

执行命令

[ ~]# ansible   web  -m    ping
172.16.1.7 | SUCCESS => {
    "ansible_facts": {
        "discovered_interpreter_python": "/usr/bin/python"
    }, 
    "changed": false, 
    "ping": "pong"
}
172.16.1.8 | SUCCESS => {
    "ansible_facts": {
        "discovered_interpreter_python": "/usr/bin/python"
    }, 
    "changed": false, 
    "ping": "pong"
}
[ ~]# ansible   nfs  -m    ping
172.16.1.31 | SUCCESS => {
    "ansible_facts": {
        "discovered_interpreter_python": "/usr/bin/python"
    }, 
    "changed": false, 
    "ping": "pong"
}
[ ~]# ansible   backup  -m    ping
172.16.1.41 | SUCCESS => {
    "ansible_facts": {
        "discovered_interpreter_python": "/usr/bin/python"
    }, 
    "changed": false, 
    "ping": "pong"
}

主机子组配置，对组进行管理

[ ~]# tail   -15   /etc/ansible/hosts
# leading 0s:

## db-[99:101]-node.example.com

[client:children]
web
nfs
backup
[web]
172.16.1.7
172.16.1.8
[nfs]
172.16.1.31
[backup]
172.16.1.41

 执行命令

[ ~]# ansible   client   -m    ping
172.16.1.31 | SUCCESS => {
    "ansible_facts": {
        "discovered_interpreter_python": "/usr/bin/python"
    }, 
    "changed": false, 
    "ping": "pong"
}
172.16.1.7 | SUCCESS => {
    "ansible_facts": {
        "discovered_interpreter_python": "/usr/bin/python"
    }, 
    "changed": false, 
    "ping": "pong"
}
172.16.1.8 | SUCCESS => {
    "ansible_facts": {
        "discovered_interpreter_python": "/usr/bin/python"
    }, 
    "changed": false, 
    "ping": "pong"
}
172.16.1.41 | SUCCESS => {
    "ansible_facts": {
        "discovered_interpreter_python": "/usr/bin/python"
    }, 
    "changed": false, 
    "ping": "pong"
}

（四）方式四：采用匹配方式配置主机信息

 [7:20]表示IP地址最后一位为7到20的主机

[ ~]# tail  -1    /etc/ansible/hosts
172.16.1.[7:20]

执行命令

31，41没有匹配

[ ~]# ansible   172.16.1.7  -m    ping
172.16.1.7 | SUCCESS => {
    "ansible_facts": {
        "discovered_interpreter_python": "/usr/bin/python"
    }, 
    "changed": false, 
    "ping": "pong"
}
[ ~]# ansible   172.16.1.8  -m    ping
172.16.1.8 | SUCCESS => {
    "ansible_facts": {
        "discovered_interpreter_python": "/usr/bin/python"
    }, 
    "changed": false, 
    "ping": "pong"
}
[ ~]# ansible   172.16.1.31  -m    ping
[WARNING]: Could not match supplied host pattern, ignoring: 172.16.1.31

[WARNING]: No hosts matched, nothing to do

[ ~]# ansible   172.16.1.41  -m    ping
[WARNING]: Could not match supplied host pattern, ignoring: 172.16.1.41

[WARNING]: No hosts matched, nothing to do
[ ~]# tail  -1    /etc/ansible/hosts
172.16.1.[1:20]
[ ~]# ansible   172.16.1.7  -m    ping
172.16.1.7 | SUCCESS => {
    "ansible_facts": {
        "discovered_interpreter_python": "/usr/bin/python"
    }, 
    "changed": false, 
    "ping": "pong"
}
[ ~]# ansible   172.16.1.8  -m    ping
172.16.1.8 | SUCCESS => {
    "ansible_facts": {
        "discovered_interpreter_python": "/usr/bin/python"
    }, 
    "changed": false, 
    "ping": "pong"
}
[ ~]# ansible   172.16.1.31  -m    ping
[WARNING]: Could not match supplied host pattern, ignoring: 172.16.1.31

[WARNING]: No hosts matched, nothing to do

[ ~]# ansible   172.16.1.41  -m    ping
[WARNING]: Could not match supplied host pattern, ignoring: 172.16.1.41

[WARNING]: No hosts matched, nothing to do

五批量管理服务应用方法


批量管理命令语法结构:

ansible      管理主机信息/主机组信息    -m    模块名称    -a     "模块参数"

[ ~]# tail     /etc/ansible/hosts

# Here‘s another example of host ranges, this time there are no
# leading 0s:

## db-[99:101]-node.example.com
[client]
172.16.1.7
172.16.1.8
172.16.1.31
172.16.1.41

（一）command模块 (默认)

[ ~]# ansible client  -a  "free -h"
172.16.1.7 | CHANGED | rc=0 >>
              total        used        free      shared  buff/cache   available
Mem:           972M        138M        591M        7.7M        242M        651M
Swap:          1.5G          0B        1.5G

172.16.1.31 | CHANGED | rc=0 >>
              total        used        free      shared  buff/cache   available
Mem:           972M        140M        642M        7.7M        189M        647M
Swap:          1.5G          0B        1.5G

172.16.1.41 | CHANGED | rc=0 >>
              total        used        free      shared  buff/cache   available
Mem:           972M        136M        673M        7.7M        162M        665M
Swap:          1.5G          0B        1.5G

172.16.1.8 | CHANGED | rc=0 >>
              total        used        free      shared  buff/cache   available
Mem:           972M        140M        662M        7.7M        169M        657M
Swap:          1.5G          0B        1.5G
[ ~]# ansible client -m  shell   -a  "rm  -rf  /tmp/*"
[WARNING]: Consider using the file module with state=absent rather than running
‘rm‘.  If you need to use command because file is insufficient you can add ‘warn:
false‘ to this command task or set ‘command_warnings=False‘ in ansible.cfg to get
rid of this message.

172.16.1.7 | CHANGED | rc=0 >>


172.16.1.8 | CHANGED | rc=0 >>


172.16.1.31 | CHANGED | rc=0 >>


172.16.1.41 | CHANGED | rc=0 >>


[ ~]# ansible client -m  shell   -a  "ls  /tmp/*"
172.16.1.8 | CHANGED | rc=0 >>
ansible_command_payload.zip

172.16.1.7 | CHANGED | rc=0 >>
ansible_command_payload.zip

172.16.1.41 | CHANGED | rc=0 >>
ansible_command_payload.zip

172.16.1.31 | CHANGED | rc=0 >>
ansible_command_payload.zip
[ ~]# ansible client -m  command   -a  "pwd"
172.16.1.41 | CHANGED | rc=0 >>
/root

172.16.1.7 | CHANGED | rc=0 >>
/root

172.16.1.8 | CHANGED | rc=0 >>
/root

172.16.1.31 | CHANGED | rc=0 >>
/root

模块参数:chdir:  在执行批量管理命令时, 先进行目录切换        

[ ~]# ansible   client  -m   command   -a  "chdir=/tmp pwd"
172.16.1.41 | CHANGED | rc=0 >>
/tmp

172.16.1.7 | CHANGED | rc=0 >>
/tmp

172.16.1.31 | CHANGED | rc=0 >>
/tmp

172.16.1.8 | CHANGED | rc=0 >>
/tmp

creates: 判断指定文件是否存在, 如果不存在,就执行后面命令；存在就不执行后面命令

和判断语句类似

[ ~]# ansible client -m  command   -a  "creates=/tmp/happy.txt  touch /tmp/happy.txt"
[WARNING]: Consider using the file module with state=touch rather than running
‘touch‘.  If you need to use command because file is insufficient you can add ‘warn:
false‘ to this command task or set ‘command_warnings=False‘ in ansible.cfg to get
rid of this message.

172.16.1.31 | CHANGED | rc=0 >>


172.16.1.7 | CHANGED | rc=0 >>


172.16.1.41 | CHANGED | rc=0 >>


172.16.1.8 | CHANGED | rc=0 >>
[ ~]# ansible client -m  command   -a  "chdir=/tmp ls"
172.16.1.41 | CHANGED | rc=0 >>
ansible_command_payload_dKZhze
happy.txt

172.16.1.8 | CHANGED | rc=0 >>
ansible_command_payload_0Y2P6b
happy.txt

172.16.1.7 | CHANGED | rc=0 >>
ansible_command_payload_sagI1X
happy.txt

172.16.1.31 | CHANGED | rc=0 >>
ansible_command_payload_1XAqCp
happy.txt

再次执行会跳过了

[ ~]# ansible client -m  command   -a  "creates=/tmp/happy.txt  touch /tmp/happy.txt"
172.16.1.31 | SUCCESS | rc=0 >>
skipped, since /tmp/happy.txt exists

172.16.1.8 | SUCCESS | rc=0 >>
skipped, since /tmp/happy.txt exists

172.16.1.7 | SUCCESS | rc=0 >>
skipped, since /tmp/happy.txt exists

172.16.1.41 | SUCCESS | rc=0 >>
skipped, since /tmp/happy.txt exists

批量执行脚本


第一个步骤：编写脚本
第二个步骤：将脚本推送到被管理主机上
第三个步骤：将脚本文件权限进行设置
第四个步骤：批量执行脚本

 https://docs.ansible.com/ansible/latest/modules/shell_module.html#shell-module

（二）shell模块（万能模块）

作用说明：批量执行命令，可以识别特殊符号

[ ~]#  ansible-doc   --help |  grep  "\-s"
                   [-j] [-F | -l | -s | --metadata-dump]
                        prepend colon-separated path(s) to module library (def
  -s, --snippet         Show playbook snippet for specified plugin(s)
[ ~]# ansible-doc -s  shell
- name: Execute shell commands on targets
  shell:
      chdir:                 # Change into this directory before running the
                               command.
      cmd:                   # The command to run followed by optional
                               arguments.
      creates:               # A filename, when it already exists, this step
                               will *not* be
                               run.
      executable:            # Change the shell used to execute the command.
                               This expects an
                               absolute path to
                               the executable.
      free_form:             # The shell module takes a free form command to
                               run, as a string.
                               There is no
                               actual parameter
                               named ‘free
                               form‘. See the
                               examples on how
                               to use this
                               module.
      removes:               # A filename, when it does not exist, this step
                               will *not* be
                               run.
      stdin:                 # Set the stdin of the command directly to the
                               specified value.
      stdin_add_newline:     # Whether to append a newline to stdin data.
      warn:                  # Whether to enable task warnings.
(END)

把管理端的脚本传输到受控端的目录里面

先查看目录是否存在

[ ~]# ansible  client  -m  shell  -a  "ls  -d  /shell_scripts"
172.16.1.8 | CHANGED | rc=0 >>
/shell_scripts

172.16.1.7 | CHANGED | rc=0 >>
/shell_scripts

172.16.1.31 | CHANGED | rc=0 >>
/shell_scripts

172.16.1.41 | CHANGED | rc=0 >>
/shell_scripts

正式进行文件传输

[ ~]# time   ansible  client  -m  copy    -a  ‘src=/shell_scripts/install.sh  dest=/shell_scripts‘
172.16.1.41 | SUCCESS => {
    "ansible_facts": {
        "discovered_interpreter_python": "/usr/bin/python"
    }, 
    "changed": false, 
    "checksum": "d8930d18657635c362456d4e25091679006031e8", 
    "dest": "/shell_scripts/install.sh", 
    "gid": 0, 
    "group": "root", 
    "mode": "0755", 
    "owner": "root", 
    "path": "/shell_scripts/install.sh", 
    "size": 36, 
    "state": "file", 
    "uid": 0
}
172.16.1.7 | SUCCESS => {
    "ansible_facts": {
        "discovered_interpreter_python": "/usr/bin/python"
    }, 
    "changed": false, 
    "checksum": "d8930d18657635c362456d4e25091679006031e8", 
    "dest": "/shell_scripts/install.sh", 
    "gid": 0, 
    "group": "root", 
    "mode": "0644", 
    "owner": "root", 
    "path": "/shell_scripts/install.sh", 
    "size": 36, 
    "state": "file", 
    "uid": 0
}
172.16.1.31 | SUCCESS => {
    "ansible_facts": {
        "discovered_interpreter_python": "/usr/bin/python"
    }, 
    "changed": false, 
    "checksum": "d8930d18657635c362456d4e25091679006031e8", 
    "dest": "/shell_scripts/install.sh", 
    "gid": 0, 
    "group": "root", 
    "mode": "0755", 
    "owner": "root", 
    "path": "/shell_scripts/install.sh", 
    "size": 36, 
    "state": "file",

ansible gz

onepiecedn

onepiecedn

0 关注 0 粉丝 0 动态

关注 关注

相关推荐

shell脚本实现公司项目部署交付环境预检查的思路

echo -e "\033[1;32;31m检测到节点umask值非022,将为您执行修改操作！ansible dragon -m shell -a "sed -i 's/^.*umask.*/umask 022/g' /etc/pro

laisean 2020-09-27

使用Ansible的Kubernetes模块实现容器编排自动化

将 Kubernetes 与 Ansible 结合实现云端自动化。此外，还可以参照我们的 Ansible 的 k8s 模块速查表。Ansible是实现自动化工作的优秀工具，而Kubernetes则是容器编排方面的利器，要是把两者结合起来，会有怎样的效果呢？

onepiecedn 2020-10-29

避免云锁定有哪几招？

我们Render正在构建一个跨多个公共云启动的新云平台，计划增加本地工作负载，这对于我们避免将自己被某一家提供商锁定至关重要。本文讨论了我们做出的一些关键技术决策，以避免自己被某一家云提供商锁定，并为混合云未来做好准备。大受欢迎的选择包括AWS Clou

guchengxinfen 2020-10-12

一篇让你快速熟悉ansible和使用

默认使用SSH协议进行管理主从集中化管理配置简单，扩展性强支持API及自定义模块，可通过python扩展通过playbooks剧本来定制强大的配置。ansible命令语法：ansible[-i:主机文件][-f：批次][组名][-m模块名称][-a：模块参

houdaiye 2020-09-23

ansible生产环境使用场景(四)：encrypt_string加密和ansible-lint调试

有时需要对yaml文件中的某些敏感字段进行加密，这时就需要‘ansible-vault encrypt_string ’加密字符串，在使用过程中发现报错：Vault format unhexlify error: Odd-length string fat

逆时针 2020-08-19

Playbook语法快速入门

playbook是ansible用于配置，部署，和管理被控节点的剧本。通过playbook的详细描述，执行其中的一系列tasks，可以让远端主机达到预期的状态。playbook就像Ansible控制器给被控节点列出的的一系列to-do-list，而被控节点

pzczyy 2020-08-19

ansible生产环境使用场景(二)

生产上新入网的服务器都需要安装prometheus的监控客户端软件，主要步骤有：新建监控用户、拷贝客户端软件、拉起客户端进程、开机自启动。本文记录了使用ansible的role方式批量快速的安装该客户端软件。本文使用到的主要模块：user、stat、cop

annan 2020-08-02

记录：部署Ansible，Ansible ad-hoc应用(1

准备如表-1所示的实验环境，操作系统为RHEL8，配置主机名称、IP地址、YUM源。ansible通过ssh远程被管理主机，将控制端的模块（脚本）或命令传输到被管理主机；最后ansible退出ssh远程。绝大多数模块（脚本）都需要参数才能执行成功！！！类似

hpujsj 2020-07-26

Ansible自动化

目录第一章 前提条件1.1创建ssh密钥对 1.2分发公钥文件 1.3编写脚本 1.4端口被更改 第二章 安装测试2.1 安装配置 2.2 常用模块说明 2.3 command模块 2.4 shell模块 2.5 scr

annan 2020-07-18

jenkins流水线共享库搭建实例

创建共享库代码项目。整个流程搭建结束

逆时针 2020-06-25

运维简介&amp;Ansible详解

运维工作的核心任务：。发布、变更、故障处理。程序安装、配置、服务启动。新版本的代码先发布到服务器。不能影响用户体验。不能导致系统故障或造成系统完全不可用。通过调度器将线上的一批服务器标记为down模式。部署新版本的应用程序至目标位置。自动化灰度发布：脚本、

逆时针 2020-06-21

自动化运维工具-Ansible Jinja2模板

自动化运维工具-Ansible Jinja2模板。Ansible通常会使用jinja2模板来修改被管理主机的配置文件等...在saltstack中同样会使用到jinja2. 为了方便，使用jinja2语法，渲染配置文件。{{ EXPR }}输出变量值，会输

annan 2020-06-20

ansible playbook中when的多种用法和playbook handler

剧本中可以使用判断的方式，减少hosts的个数。shutdown -f　强行关闭应用程序。shutdown -m \\计算机名　控制远程计算机。shutdown -i　显示“远程关机”图形用户界面，但必须是Shutdown的第一个参数 　。shutdown

逆时针 2020-06-14

ansible常用的定义变量方式和变量注册facts缓存和template的使用

可以使用自定义主机组的方式定义hosts，这样可以减少重复任务的代码。"{{ ansible_fqdn }}" 无论是自定义变量还是系统变量的调用，写到剧本中的路径里的话不要加引号，单独的调用需要加引号。playbook变量可以通过多种

逆时针 2020-06-14

使用playbook实现一键部署rsync

5.把客户端密码加入环境全局变量文件

awoyaoc 2020-06-14

[Ansible实战]-ansible部署rsync全网备份项目

[Ansible实战]-ansible部署rsync全网备份项目.b.开机自启动的配置文件。3)Web服务器站点目录假定为。6)备份服务器上,保留每周一的所有数据副本，其它要保留6个月的数据副本。7)备份服务器上要按照备份数据服务器的内网IP为目录保存备份

awoyaoc 2020-06-12

Ansible-doc里面的一些简单模块使用

ansible webs -m shell -a ‘echo ${HOSTNAME}‘ //取消本地的结果输出，直接在ansible远程主机上执行echo ${HOSTNAME}. ansible 主机或主机集合 -m service -a

逆时针 2020-06-09

ansible自动部署ftp中遇到的坑

记录一下本周写ansible自动部署时遇到的坑。因为要部署ftp服务器，所以整理了ftp部署相关的资料，按照整理的资料可以顺利的进行ftp部署和卸载，但是利用ansible自动部署的时候总会出现各种异常。通过一步步的排查发现是配置文件有问题。所以在ansi

piaotiejun 2020-06-07

YAML语法入门

Ansible是一个系列文章，我会尽量以通俗易懂、诙谐幽默的总结方式给大家呈现这些枯燥的知识点，让学习变的有趣一些。在学习playbook的时候，你可能会被惊讶到，YAML是什么鬼？然后就对这个YAML产生了一个中莫名的恐惧和厌烦感！YAML就和XML、J

awoyaoc 2020-06-07

ansible批量禁止root用户登录

- name: "Replace / etc / SSH / sshd_ Permitrootlogin parameter in config file"

BraveWangDev 2020-06-05
onepiecedn

onepiecedn

W3CSchool教程
HTML 教程
CSS 教程
Bootstrap 教程
Javascript 教程
jQuery 教程
后端教程
C 教程
Java 教程
PHP 教程
Python 教程
Go 教程
移动开发
Android 教程
Swift 教程
Kotlin 教程
jQuery Mobile 教程
ionic 教程
关于我们
新闻动态
联系方式
招聘英才
安科实验室
帮助与反馈

安科网(Ancii)，中国第一极客网

Copyright © 2013 - 2019 Ancii.com

京ICP备18063983号 京公网安备11010802014868号