簡介：
當下有許多的運維自動化工具( 配置管理 )，例如：Ansible、SaltStack、Puppet、Fabric 等。
Ansible 一種集成 IT 系統的配置管理、應用部署、執行特定任務的開源平台，是 AnsibleWorks 公司名下的項目，該公司由 Cobbler 及 Func 的作者於 2012 年創建成立。
Ansible 基於 Python 語言實現，由 Paramiko 和 PyYAML 兩個關鍵模塊構建。
Ansible 特點：
>> 部署簡單，只需在主控端部署 Ansible 環境，被控端無需做任何操作。
>> 默認使用 SSH（Secure Shell）協議對設備進行管理。
>> 主從集中化管理。
>> 配置簡單、功能強大、擴展性強。
>> 支持 API 及自定義模塊，可通過 Python 輕松擴展。
>> 通過 Playbooks 來定制強大的配置、狀態管理。
>> 對雲計算平台、大數據都有很好的支持。
>> 提供一個功能強大、操作性強的 Web 管理界面和 REST API 接口 ---- AWX 平台。
Ansible 與 SaltStack
>> 最大的區別是 Ansible 無需在被監控主機部署任何客戶端代理，默認通過 SSH 通道進行遠程命令執行或下發配置。
>> 相同點是都具備功能強大、靈活的系統管理、狀態配置，都使用 YAML 格式來描述配置，兩者都提供豐富的模板及 API，對雲計算平台、大數據都有很好的支持。
一、安裝 Ansible
shell > yum -y install ansible
二、配置 Ansible
shell > ls /etc/ansible # ansible.cfg 是 Ansible 工具的配置文件；hosts 用來配置被管理的機器；roles 是一個目錄，playbook 將使用它 ansible.cfg hosts roles
1、Ansible 管理機與被管理機做秘鑰認證
shell > ssh-keygen # 生成秘鑰 Generating public/private rsa key pair. Enter file in which to save the key (/root/.ssh/id_rsa): Created directory '/root/.ssh'. Enter passphrase (empty for no passphrase): Enter same passphrase again: Your identification has been saved in /root/.ssh/id_rsa. Your public key has been saved in /root/.ssh/id_rsa.pub. The key fingerprint is: ea:11:72:ea:d2:d1:fa:1c:e0:df:4f:b0:98:31:be:fe [email protected] The key's randomart image is: +--[ RSA 2048]----+ | | | | | | | | | o.= S | | ..*.B o | | .ooB . . | | ..o+ = . | | ..oB.E.. | +-----------------+ shell > ssh-copy-id -i ~/.ssh/id_rsa.pub "-p 22 [email protected]" # 將公鑰寫入被管理機 The authenticity of host '192.168.12.129 (192.168.12.129)' can't be established. RSA key fingerprint is f0:9e:01:73:a4:bf:14:10:ac:46:a9:48:cd:c5:d8:1c. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '192.168.12.129' (RSA) to the list of known hosts. [email protected]'s password: Now try logging into the machine, with "ssh '-p 22 [email protected]'", and check in: .ssh/authorized_keys to make sure we haven't added extra keys that you weren't expecting.
2、hosts 文件添加被管理機
shell > > /etc/ansible/hosts shell > vim /etc/ansible/hosts [Client] 192.168.12.129
三、測試 Ansible
shell > ansible Client -m ping # 操作 Client 組 ( all 為操作 hosts 文件中所有主機 )，-m 指定執行 ping 模塊，下面是返回結果
192.168.12.129 | SUCCESS => {
"changed": false,
"ping": "pong"
}
# -i 指定 hosts 文件位置
# -u username 指定 SSH 連接的用戶名
# -k 指定遠程用戶密碼
# -f 指定並發數
# -s 如需要 root 權限執行時使用 ( 連接用戶不是 root 時 )
# -K -s 時，-K 輸入 root 密碼
四、附加
1、/etc/ansible/hosts 文件
## Ansible 定義主機、組規則的配置文件
shell > vim /etc/ansible/hosts www.abc.com # 定義域名 192.168.1.100 # 定義 IP 192.168.1.150:37268 # 指定端口號 [WebServer] # 定義分組 192.168.1.10 192.168.1.20 192.168.1.30 [DBServer] # 定義多個分組 192.168.1.50 192.168.1.60 Monitor ansible_ssh_port=12378 ansible_ssh_host=192.168.1.200 # 定義別名 # ansible_ssh_host 連接目標主機的地址 # ansible_ssh_port 連接目標主機的端口，默認 22 時無需指定 # ansible_ssh_user 連接目標主機默認用戶 # ansible_ssh_pass 連接目標主機默認用戶密碼 # ansible_ssh_connection 目標主機連接類型，可以是 local 、ssh 或 paramiko # ansible_ssh_private_key_file 連接目標主機的 ssh 私鑰 # ansible_*_interpreter 指定采用非 Python 的其他腳本語言，如 Ruby 、Perl 或其他類似 ansible_python_interpreter 解釋器 [webservers] # 主機名支持正則描述 www[01:50].example.com [dbservers] db-[a:f].example.com
2、Ansible 常用模塊學習
shell > ansible-doc -l # 列出 Ansible 支持的模塊 shell > ansible-doc ping # 查看該模塊幫助信息
>> 遠程命令模塊（ command / script / shell ）
command 作為 Ansible 的默認模塊，可以運行遠程權限范圍所有的 shell 命令，不支持管道符。
例：
shell > ansible Client -m command -a "free -m" # 查看 Client 分組主機內存使用情況
script 的功能是在遠程主機執行主控端存儲的 shell 腳本文件，相當於 scp + shell 組合。
例：
shell > ansible Client -m script -a "/home/test.sh 12 34" # 遠程執行本地腳本
shell 的功能是執行遠程主機上的 shell 腳本文件，支持管道符。
例：
shell > ansible Client -m shell -a "/home/test.sh" # 執行遠程腳本
>> copy 模塊（實現主控端向目標主機拷貝文件，類似於 scp 功能）
例：
shell > ansible Client -m copy -a "src=/home/test.sh desc=/tmp/ owner=root group=root mode=0755" # 向 Client 組中主機拷貝 test.sh 到 /tmp 下，屬主、組為 root ，權限為 0755
>> stat 模塊（獲取遠程文件狀態信息，atime/ctime/mtime/md5/uid/gid 等信息）
例：
shell > ansible Client -m stat -a "path=/etc/syctl.conf"
>> get_url 模塊（實現在遠程主機下載指定 URL 到本地，支持 sha256sum 文件校驗）
例：
shell > ansible Client -m get_utl -a "url=http://www.baidu.com dest=/tmp/index.html mode=0440 force=yes"
>> yum 模塊（軟件包管理）
例：
shell > ansible Client -m yum -a "name=curl state=latest"
>> cron 模塊（遠程主機 crontab 配置）
例：
shell > ansible Client -m cron -a "name='check dirs' hour='5,2' job='ls -alh > /dev/null'"
效果：
#Ansible: check dirs * 5,2 * * * ls -alh > /dev/null
>> mount 模塊（遠程主機分區掛載）
例：
shell > ansible Client -m mount -a "name=/mnt/data src=/dev/sd0 fstype=ext4 opts=ro state=present"
>> service 模塊（遠程主機系統服務管理）
例：
shell > ansible Client -m service -a "name=nginx state=stoped" shell > ansible Client -m service -a "name=nginx state=restarted" shell > ansible Client -m service -a "name=nginx state=reloaded"
>> user 服務模塊（遠程主機用戶管理）
例：
shell > ansible Client -m user -a "name=wang comment='user wang'" shell > ansible Client -m user -a "name=wang state=absent remove=yes" # 添加刪除用戶
五、Ansible-playbook
# 使用 Ansible-playbook 可以完成一組復雜的動作，例如部署環境、搭建服務、修改配置等。
簡單示例：
shell > vim /etc/ansible/playbook.yml # 將遠程主機IP地址寫入文件中保存
---
- hosts: Client
remote_user: root
tasks:
- name: Save IP To info.txt
shell: "ifconfig eth0 | awk -F '[ :]'+ '/inet addr/{print $4}' > ~/info.txt"
# hosts 指定執行操作主機
# remote_user 指定執行用戶
# tasks 指明有哪些動作
# name 動作描述
# shell 模塊，後面為具體指令
Playbook 實戰：
一、目錄結構
shell > cd /etc/ansible/ ; tree .
.
├── ansible.cfg
├── delete_zabbix_agent.yml
├── hosts
├── install_zabbix_agent.yml
└── roles
├── delete_zabbix_agent
│ ├── tasks
│ │ └── main.yml
│ └── vars
│ └── main.yml
└── install_zabbix_agent
├── files
│ └── zabbix-2.4.5.tar.gz
├── tasks
│ └── main.yml
├── templates
│ ├── zabbix_agentd
│ └── zabbix_agentd.conf
└── vars
└── main.yml
## ansible.cfg 此文件為 ansible 的主配置文件
## hosts 用於定義主機組
## roles 定義不同的角色
## install_zabbix_agent.yml 用於安裝 zabbix_agent 的引導文件
## delete_zabbix_agent.yml 刪除已安裝的 zabbix_agent 的引導文件
└── install_zabbix_agent
├── files
│ └── zabbix-2.4.5.tar.gz
├── tasks
│ └── main.yml
├── templates
│ ├── zabbix_agentd
│ └── zabbix_agentd.conf
└── vars
└── main.yml
## 其中，install_zabbix_agent 為一個角色，用於安裝 zabbix_agent
## file 目錄：用於存放將要拷貝到遠程主機的安裝包等
## tasks 目錄：將要執行的所有任務，如果比較復雜，可以單獨定義不同的任務，最後在 main.yml 文件中引用即可
## templates 目錄：模板目錄，這裡存放著一些可變的文件，即：每台主機上的這些文件中的內容都不完全相同
## vars 目錄：用於存放變量
## 這是一個比較簡單的結構，其實一個角色中還可以有 meta 、handlers 等
二、Playbook 安裝軟件需要的步驟
1、定義 hosts（ 給哪些主機安裝軟件 ）
shell > vim /etc/ansible/hosts [mini] 129.139.153.78:16283 155.139.190.94:12573
2、定義入口文件 install_zabbix_agent.yml
shell > vim /etc/ansible/install_zabbix_agent.yml --- - hosts: mini roles: - install_zabbix_agent ## 可以看到將要安裝的主機組為 mini 組，角色為 install_zabbix_agent
3、定義角色 install_zabbix_agent
shell > tree /etc/ansible/roles/install_zabbix_agent/
├── files
│ └── zabbix-2.4.5.tar.gz
├── tasks
│ └── main.yml
├── templates
│ ├── zabbix_agentd
│ └── zabbix_agentd.conf
└── vars
└── main.yml
## 建立 files 目錄，存放編譯安裝過的 zabbix_agent 目錄的壓縮文件，用於拷貝到遠程主機
## 建立 tasks 目錄，用於編寫將要執行的任務
## 建立 templates 目錄，用於存放可變的模板文件
## 建立 vars 目錄，用於存放變量信息
shell > cat /etc/ansible/roles/install_zabbix_agent/tasks/main.yml
---
- name: Install Software
yum: name={{ item }} state=latest
with_items:
- libcurl-devel
- name: Create Zabbix User
user: name={{ zabbix_user }} state=present createhome=no shell=/sbin/nologin
- name: Copy Zabbix.tar.gz
copy: src=zabbix-{{ zabbix_version }}.tar.gz dest={{ zabbix_dir }}/src/zabbix-{{ zabbix_version }}.tar.gz owner=root group=root
- name: Uncompression Zabbix.tar.gz
shell: tar zxf {{ zabbix_dir }}/src/zabbix-{{ zabbix_version }}.tar.gz -C {{ zabbix_dir }}/
- name: Copy Zabbix Start Script
template: src=zabbix_agentd dest=/etc/init.d/zabbix_agentd owner=root group=root mode=0755
- name: Copy Zabbix Config File
template: src=zabbix_agentd.conf dest={{ zabbix_dir }}/zabbix/etc/zabbix_agentd.conf owner={{ zabbix_user }} group={{ zabbix_user }} mode=0644
- name: Modify Zabbix Dir Permisson
file: path={{ zabbix_dir }}/zabbix owner={{ zabbix_user }} group={{ zabbix_user }} mode=0755 recurse=yes
- name: Start Zabbix Service
shell: /etc/init.d/zabbix_agentd start
- name: Add Boot Start Zabbix Service
shell: chkconfig --level 35 zabbix_agentd on
shell > cat /etc/ansible/roles/install_zabbix_agent/vars/main.yml zabbix_dir: /usr/local zabbix_version: 2.4.5 zabbix_user: zabbix zabbix_port: 10050 zabbix_server_ip: 131.142.101.120
shell > cat /etc/ansible/roles/install_zabbix_agent/templates/zabbix_agentd #!/bin/bash # # chkconfig: - 90 10 # description: Starts and stops Zabbix Agent using chkconfig # Tested on Fedora Core 2 - 5 # Should work on all Fedora Core versions # # @name: zabbix_agentd # @author: Alexander Hagenah <[email protected]> # @created: 18.04.2006 # # Modified for Zabbix 2.0.0 # May 2012, Zabbix SIA # # Source function library. . /etc/init.d/functions # Variables # Edit these to match your system settings # Zabbix-Directory BASEDIR={{ zabbix_dir }}/zabbix # Binary File BINARY_NAME=zabbix_agentd # Full Binary File Call FULLPATH=$BASEDIR/sbin/$BINARY_NAME # PID file PIDFILE=/tmp/$BINARY_NAME.pid # Establish args ERROR=0 STOPPING=0 # # No need to edit the things below # # application checking status if [ -f $PIDFILE ] && [ -s $PIDFILE ] then PID=`cat $PIDFILE` if [ "x$PID" != "x" ] && kill -0 $PID 2>/dev/null && [ $BINARY_NAME == `ps -e | grep $PID | awk '{print $4}'` ] then STATUS="$BINARY_NAME (pid `pidof $APP`) running.." RUNNING=1 else rm -f $PIDFILE STATUS="$BINARY_NAME (pid file existed ($PID) and now removed) not running.." RUNNING=0 fi else if [ `ps -e | grep $BINARY_NAME | head -1 | awk '{ print $1 }'` ] then STATUS="$BINARY_NAME (pid `pidof $APP`, but no pid file) running.." else STATUS="$BINARY_NAME (no pid file) not running" fi RUNNING=0 fi # functions start() { if [ $RUNNING -eq 1 ] then echo "$0 $ARG: $BINARY_NAME (pid $PID) already running" else action $"Starting $BINARY_NAME: " $FULLPATH touch /var/lock/subsys/$BINARY_NAME fi } stop() { echo -n $"Shutting down $BINARY_NAME: " killproc $BINARY_NAME RETVAL=$? echo [ $RETVAL -eq 0 ] && rm -f /var/lock/subsys/$BINARY_NAME RUNNING=0 } # logic case "$1" in start) start ;; stop) stop ;; status) status $BINARY_NAME ;; restart) stop sleep 10 start ;; help|*) echo $"Usage: $0 {start|stop|status|restart|help}" cat <<EOF start - start $BINARY_NAME stop - stop $BINARY_NAME status - show current status of $BINARY_NAME restart - restart $BINARY_NAME if running by sending a SIGHUP or start if not running help - this screen EOF exit 1 ;; esac exit 0
shell > cat /etc/ansible/roles/install_zabbix_agent/templates/zabbix_agentd.conf
# This is a config file for the Zabbix agent daemon (Unix)
# To get more information about Zabbix, visit http://www.zabbix.com
############ GENERAL PARAMETERS #################
### Option: PidFile
# Name of PID file.
#
# Mandatory: no
# Default:
# PidFile=/tmp/zabbix_agentd.pid
### Option: LogFile
# Name of log file.
# If not set, syslog is used.
#
# Mandatory: no
# Default:
# LogFile=
LogFile=/tmp/zabbix_agentd.log
### Option: LogFileSize
# Maximum size of log file in MB.
# 0 - disable automatic log rotation.
#
# Mandatory: no
# Range: 0-1024
# Default:
# LogFileSize=1
### Option: DebugLevel
# Specifies debug level
# 0 - basic information about starting and stopping of Zabbix processes
# 1 - critical information
# 2 - error information
# 3 - warnings
# 4 - for debugging (produces lots of information)
#
# Mandatory: no
# Range: 0-4
# Default:
# DebugLevel=3
### Option: SourceIP
# Source IP address for outgoing connections.
#
# Mandatory: no
# Default:
# SourceIP=
### Option: EnableRemoteCommands
# Whether remote commands from Zabbix server are allowed.
# 0 - not allowed
# 1 - allowed
#
# Mandatory: no
# Default:
# EnableRemoteCommands=0
### Option: LogRemoteCommands
# Enable logging of executed shell commands as warnings.
# 0 - disabled
# 1 - enabled
#
# Mandatory: no
# Default:
# LogRemoteCommands=0
##### Passive checks related
### Option: Server
# List of comma delimited IP addresses (or hostnames) of Zabbix servers.
# Incoming connections will be accepted only from the hosts listed here.
# If IPv6 support is enabled then '127.0.0.1', '::127.0.0.1', '::ffff:127.0.0.1' are treated equally.
#
# Mandatory: no
# Default:
# Server=
Server={{ zabbix_server_ip }}
### Option: ListenPort
# Agent will listen on this port for connections from the server.
#
# Mandatory: no
# Range: 1024-32767
# Default:
# ListenPort=10050
ListenPort={{ zabbix_port }}
### Option: ListenIP
# List of comma delimited IP addresses that the agent should listen on.
# First IP address is sent to Zabbix server if connecting to it to retrieve list of active checks.
#
# Mandatory: no
# Default:
# ListenIP=0.0.0.0
### Option: StartAgents
# Number of pre-forked instances of zabbix_agentd that process passive checks.
# If set to 0, disables passive checks and the agent will not listen on any TCP port.
#
# Mandatory: no
# Range: 0-100
# Default:
# StartAgents=3
##### Active checks related
### Option: ServerActive
# List of comma delimited IP:port (or hostname:port) pairs of Zabbix servers for active checks.
# If port is not specified, default port is used.
# IPv6 addresses must be enclosed in square brackets if port for that host is specified.
# If port is not specified, square brackets for IPv6 addresses are optional.
# If this parameter is not specified, active checks are disabled.
# Example: ServerActive=127.0.0.1:20051,zabbix.domain,[::1]:30051,::1,[12fc::1]
#
# Mandatory: no
# Default:
# ServerActive=
#ServerActive=127.0.0.1:10051
### Option: Hostname
# Unique, case sensitive hostname.
# Required for active checks and must match hostname as configured on the server.
# Value is acquired from HostnameItem if undefined.
#
# Mandatory: no
# Default:
# Hostname=
Hostname={{ ansible_all_ipv4_addresses[1] }}
### Option: HostnameItem
# Item used for generating Hostname if it is undefined. Ignored if Hostname is defined.
# Does not support UserParameters or aliases.
#
# Mandatory: no
# Default:
# HostnameItem=system.hostname
### Option: HostMetadata
# Optional parameter that defines host metadata.
# Host metadata is used at host auto-registration process.
# An agent will issue an error and not start if the value is over limit of 255 characters.
# If not defined, value will be acquired from HostMetadataItem.
#
# Mandatory: no
# Range: 0-255 characters
# Default:
# HostMetadata=
### Option: HostMetadataItem
# Optional parameter that defines an item used for getting host metadata.
# Host metadata is used at host auto-registration process.
# During an auto-registration request an agent will log a warning message if
# the value returned by specified item is over limit of 255 characters.
# This option is only used when HostMetadata is not defined.
#
# Mandatory: no
# Default:
# HostMetadataItem=
### Option: RefreshActiveChecks
# How often list of active checks is refreshed, in seconds.
#
# Mandatory: no
# Range: 60-3600
# Default:
# RefreshActiveChecks=120
### Option: BufferSend
# Do not keep data longer than N seconds in buffer.
#
# Mandatory: no
# Range: 1-3600
# Default:
# BufferSend=5
### Option: BufferSize
# Maximum number of values in a memory buffer. The agent will send
# all collected data to Zabbix Server or Proxy if the buffer is full.
#
# Mandatory: no
# Range: 2-65535
# Default:
# BufferSize=100
### Option: MaxLinesPerSecond
# Maximum number of new lines the agent will send per second to Zabbix Server
# or Proxy processing 'log' and 'logrt' active checks.
# The provided value will be overridden by the parameter 'maxlines',
# provided in 'log' or 'logrt' item keys.
#
# Mandatory: no
# Range: 1-1000
# Default:
# MaxLinesPerSecond=100
############ ADVANCED PARAMETERS #################
### Option: Alias
# Sets an alias for an item key. It can be used to substitute long and complex item key with a smaller and simpler one.
# Multiple Alias parameters may be present. Multiple parameters with the same Alias key are not allowed.
# Different Alias keys may reference the same item key.
# For example, to retrieve the ID of user 'zabbix':
# Alias=zabbix.userid:vfs.file.regexp[/etc/passwd,^zabbix:.:([0-9]+),,,,\1]
# Now shorthand key zabbix.userid may be used to retrieve data.
# Aliases can be used in HostMetadataItem but not in HostnameItem parameters.
#
# Mandatory: no
# Range:
# Default:
### Option: Timeout
# Spend no more than Timeout seconds on processing
#
# Mandatory: no
# Range: 1-30
# Default:
Timeout=20
### Option: AllowRoot
# Allow the agent to run as 'root'. If disabled and the agent is started by 'root', the agent
# will try to switch to the user specified by the User configuration option instead.
# Has no effect if started under a regular user.
# 0 - do not allow
# 1 - allow
#
# Mandatory: no
# Default:
# AllowRoot=0
### Option: User
# Drop privileges to a specific, existing user on the system.
# Only has effect if run as 'root' and AllowRoot is disabled.
#
# Mandatory: no
# Default:
# User=zabbix
### Option: Include
# You may include individual files or all files in a directory in the configuration file.
# Installing Zabbix will create include directory in /usr/local/etc, unless modified during the compile time.
#
# Mandatory: no
# Default:
# Include=
# Include=/usr/local/etc/zabbix_agentd.userparams.conf
# Include=/usr/local/etc/zabbix_agentd.conf.d/
# Include=/usr/local/etc/zabbix_agentd.conf.d/*.conf
####### USER-DEFINED MONITORED PARAMETERS #######
### Option: UnsafeUserParameters
# Allow all characters to be passed in arguments to user-defined parameters.
# 0 - do not allow
# 1 - allow
#
# Mandatory: no
# Range: 0-1
# Default:
UnsafeUserParameters=1
### Option: UserParameter
# User-defined parameter to monitor. There can be several user-defined parameters.
# Format: UserParameter=<key>,<shell command>
# See 'zabbix_agentd' directory for examples.
#
# Mandatory: no
# Default:
# UserParameter=
####### LOADABLE MODULES #######
### Option: LoadModulePath
# Full path to location of agent modules.
# Default depends on compilation options.
#
# Mandatory: no
# Default:
# LoadModulePath=${libdir}/modules
### Option: LoadModule
# Module to load at agent startup. Modules are used to extend functionality of the agent.
# Format: LoadModule=<module.so>
# The modules must be located in directory specified by LoadModulePath.
# It is allowed to include multiple LoadModule parameters.
#
# Mandatory: no
# Default:
# LoadModule=
4、執行安裝
shell > ansible-playbook /etc/ansible/install_zabbix_agent.yml PLAY [mini] ******************************************************************* GATHERING FACTS *************************************************************** ok: [129.139.153.78] ok: [155.139.190.94] TASK: [install_zabbix_agent | Install Software] ******************************* changed: [155.139.190.94] => (item=libcurl-devel) changed: [129.139.153.78] => (item=libcurl-devel) TASK: [install_zabbix_agent | Create Zabbix User] ***************************** changed: [129.139.153.78] changed: [155.139.190.94] TASK: [install_zabbix_agent | Copy Zabbix.tar.gz] ***************************** changed: [129.139.153.78] changed: [155.139.190.94] TASK: [install_zabbix_agent | Uncompression Zabbix.tar.gz] ******************** changed: [129.139.153.78] changed: [155.139.190.94] TASK: [install_zabbix_agent | Copy Zabbix Start Script] *********************** changed: [155.139.190.94] changed: [129.139.153.78] TASK: [install_zabbix_agent | Copy Zabbix Config File] ************************ changed: [129.139.153.78] changed: [155.139.190.94] TASK: [install_zabbix_agent | Modify Zabbix Dir Permisson] ******************** changed: [155.139.190.94] changed: [129.139.153.78] TASK: [install_zabbix_agent | Start Zabbix Service] *************************** changed: [129.139.153.78] changed: [155.139.190.94] TASK: [install_zabbix_agent | Add Boot Start Zabbix Service] ****************** changed: [129.139.153.78] changed: [155.139.190.94] PLAY RECAP ******************************************************************** 155.139.190.94 : ok=10 changed=9 unreachable=0 failed=0 129.139.153.78 : ok=10 changed=9 unreachable=0 failed=0 ## 關注一下，啟動腳本跟配置文件中變量的引用。 ## 完成安裝，可以去客戶機檢查效果了 ！
附上：delete_zabbix_agent.yml 相關內容
shell > vim /etc/ansible/delete_zabbix_agent.yml
---
- hosts: mini
roles:
- delete_zabbix_agent
shell > vim /etc/ansible/roles/delete_zabbix_agent/tasks/main.yml
---
- name: Stop Zabbix_agent
shell: pgrep zabbix_agentd | xargs kill
ignore_errors: yes
- name: Delete Boot Start
shell: chkconfig --del zabbix_agentd
- name: Delete Start Script
shell: rm -rf /etc/init.d/zabbix_agentd
- name: Delete Install Dir
shell: rm -rf {{ zabbix_dir }}/zabbix
- name: Delete Software
shell: rm -rf {{ zabbix_dir }}/src/zabbix-{{ zabbix_version }}.tar.gz
- name: Delete Log File
shell: rm -rf /tmp/zabbix_agentd.log
- name: Delete Zabbix User
user: name={{ zabbix_user }} state=absent remove=yes
shell > vim /etc/ansible/roles/delete_zabbix_agent/vars/main.yml
zabbix_dir: /usr/local
zabbix_version: 2.4.5
zabbix_user: zabbix
# End
http://xxxxxx/Linuxjc/1143053.html TechArticle