1. SaltStack组件之return
eturn组件可以理解为SaltStack系统对执行Minion返回后的数据进行存储或者返回给其他程序,它支持多种存储方式,比如用MySQL、MongoDB、Redis、Memcache等,通过return我们可以对SaltStack的每次操作进行记录,对以后日志审计提供了数据来源。目前官方已经支持30种return数据存储与接口,我们可以很方便的配置与使用它。当然也支持自己定义的return,自定义的return需由python来编写。在选择和配置好要使用的return后,只需在salt命令后面指定return即可。
//查看所有return列表
[root@vm1 ~]# salt 'vm1' sys.list_returners
vm1:
- carbon
- couchdb
- elasticsearch
- etcd
- highstate
- local
- local_cache
- mattermost
- multi_returner
- pushover
- rawfile_json
- slack
- slack_webhook
- smtp
- splunk
- sqlite3
- syslog
- telegram
1.1 return流程
return是在Master端触发任务,然后Minion接受处理任务后直接与return存储服务器建立连接,然后把数据return存到存储服务器。关于这点一定要注意,因为此过程都是Minion端操作存储服务器,所以要确保Minion端的配置跟依赖包是正确的,这意味着我们将必须在每个Minion上安装指定的return方式依赖包,假如使用Mysql作为return存储方式,那么我们将在每台Minion上安装python-mysql模块。
1.2 使用mysql作为return存储方式
环境说明:
主机名 | ip | 安装的应用 |
---|---|---|
vm1 | 192.168.30.100 | MySQL-python |
vm2 | 192.168.30.130 | mariadb、MySQL-python |
在所有minion上安装Mysql-python模块
[root@vm1 ~]# salt '*' pkg.install MySQL-python
vm2:
----------
MySQL-python:
----------
new:
1.2.5-1.el7
old:
vm1:
----------
[root@vm1 ~]# salt '*' cmd.run 'rpm -qa|grep MySQL-python'
vm2:
MySQL-python-1.2.5-1.el7.x86_64
vm1:
MySQL-python-1.2.5-1.el7.x86_64
部署一台mysql服务器用作存储服务器,此处就直接在192.168.30.130这台主机上部署
\\部署mysql
[root@vm2 ~]# yum -y install mariadb*
[root@vm2 ~]# systemctl start mariadb
[root@vm2 ~]# ss -tanl
State Recv-Q Send-Q Local Address:Port Peer Address:Port
LISTEN 0 50 *:3306 *:*
LISTEN 0 128 *:22 *:*
LISTEN 0 100 127.0.0.1:25 *:*
LISTEN 0 128 :::22 :::*
LISTEN 0 100 ::1:25 :::*
//创建数据库和表结构
[root@vm2 ~]# mysql
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 2
Server version: 5.5.65-MariaDB MariaDB Server
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
MariaDB [(none)]> CREATE DATABASE `salt`
-> DEFAULT CHARACTER SET utf8
-> DEFAULT COLLATE utf8_general_ci;
Query OK, 1 row affected (0.00 sec)
MariaDB [(none)]> USE `salt`;
Database changed
MariaDB [salt]> CREATE TABLE `jids` (
-> `jid` varchar(255) NOT NULL,
-> `load` mediumtext NOT NULL,
-> UNIQUE KEY `jid` (`jid`)
-> ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
Query OK, 0 rows affected (0.00 sec)
MariaDB [salt]> CREATE TABLE `salt_returns` (
-> `fun` varchar(50) NOT NULL,
-> `jid` varchar(255) NOT NULL,
-> `return` mediumtext NOT NULL,
-> `id` varchar(255) NOT NULL,
-> `success` varchar(10) NOT NULL,
-> `full_ret` mediumtext NOT NULL,
-> `alter_time` TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
-> KEY `id` (`id`),
-> KEY `jid` (`jid`),
-> KEY `fun` (`fun`)
-> ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
Query OK, 0 rows affected (0.01 sec)
MariaDB [salt]> CREATE TABLE `salt_events` (
-> `id` BIGINT NOT NULL AUTO_INCREMENT,
-> `tag` varchar(255) NOT NULL,
-> `data` mediumtext NOT NULL,
-> `alter_time` TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
-> `master_id` varchar(255) NOT NULL,
-> PRIMARY KEY (`id`),
-> KEY `tag` (`tag`)
-> ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
Query OK, 0 rows affected (0.01 sec)
MariaDB [salt]> show tables;
+----------------+
| Tables_in_salt |
+----------------+
| jids |
| salt_events |
| salt_returns |
+----------------+
3 rows in set (0.00 sec)
MariaDB [salt]> grant all on salt.* to salt@'%' identified by 'salt';
Query OK, 0 rows affected (0.00 sec)
MariaDB [salt]> flush privileges;
在master上配置minion
#return:
# - mysql
# - hipchat
# - slack
mysql.host: '192.168.30.130'
mysql.user: 'salt'
mysql.pass: 'salt'
mysql.db: 'salt'
mysql.port: 3306
[root@vm1 ~]# systemctl restart salt-minion
在Master上测试存储到mysql中
[root@vm1 ~]# salt '*' test.ping --return mysql
vm2:
True
vm1:
True
在数据库中查询
MariaDB [salt]> select * from salt_returns\G
*************************** 1. row ***************************
fun: test.ping
jid: 20200826024708075912
return: true
id: vm1
success: 1
full_ret: {"fun_args": [], "jid": "20200826024708075912", "return": true, "retcode": 0, "success": true, "fun": "test.ping", "id": "vm1"}
alter_time: 2020-08-25 22:47:08
1 row in set (0.00 sec)
2. job cache
2.1 job cache流程
return时是由Minion直接与存储服务器进行交互,因此需要在每台Minion上安装指定的存储方式的模块,比如python-mysql,那么我们能否直接在Master上就把返回的结果给存储到存储服务器呢?
答案是肯定的,这种方式被称作 job cache 。意思是当Minion将结果返回给Master后,由Master将结果给缓存在本地,然后将缓存的结果给存储到指定的存储服务器,比如存储到mysql中。
开启master端的master_job_cache
[root@vm1 ~]# vim /etc/salt/master
##########################################
# Allow the raw_shell parameter to be used when calling Salt SSH client via API
#netapi_allow_raw_shell: True
master_job_cache: mysql
mysql.host: '192.168.30.130'
mysql.user: 'salt'
mysql.pass: 'salt'
mysql.db: 'salt'
mysql.port: 3306
-- INSERT --
[root@vm1 ~]# systemctl restart salt-master
数据库中清空表内容
MariaDB [salt]> delete from salt.salt_returns;
Query OK, 1 row affected (0.00 sec)
在master上再次测试能否存储至数据库
[root@vm1 ~]# salt 'vm1' test.ping
vm1:
True
在数据库中验证
MariaDB [(none)]> select * from salt.salt_returns\G
*************************** 1. row ***************************
fun: test.ping
jid: 20200826025814281458
return: true
id: vm1
success: 1
full_ret: {"fun_args": [], "jid": "20200826025814281458", "re": true, "retcode": 0, "success": true, "cmd": "_return", "_sta "2020-08-26T02:58:14.465045", "fun": "test.ping", "id": "vm1"}
alter_time: 2020-08-25 22:58:14
1 row in set (0.00 sec)
2.2 job管理
获取任务的jid
[root@vm1 ~]# salt '*' cmd.run 'uptime' -v
Executing job with jid 20200826030205502978
-------------------------------------------
vm2:
23:02:05 up 1:56, 1 user, load average: 0.00, 0.01, 0.05
vm1:
23:02:05 up 2:36, 1 user, load average: 0.01, 0.21, 0.18
通过jid获取此任务的返回结果
[root@vm1 ~]# salt-run jobs.lookup_jid 20200826030205502978
vm1:
23:02:05 up 2:36, 1 user, load average: 0.01, 0.21, 0.18
vm2:
23:02:05 up 1:56, 1 user, load average: 0.00, 0.01, 0.05
3. SaltStack之salt-ssh
3.1. salt-ssh介绍
salt-ssh可以让我们不需要在受控机上安装salt-minion客户端也能够实现管理操作。
3.1.1 salt-ssh的特点
- 远程系统需要Python支持,除非使用-r选项发送原始ssh命令
- salt-ssh是一个软件包,需安装之后才能使用,命令本身也是salt-ssh
- salt-ssh不会取代标准的Salt通信系统,它只是提供了一个基于SSH的替代方案,不需要ZeroMQ和agent
请注意,由于所有与Salt SSH的通信都是通过SSH执行的,因此它比使用ZeroMQ的标准Salt慢得多
3.1.2 salt-ssh远程管理的方式
salt-ssh有两种方式实现远程管理,一种是在配置文件中记录所有客户端的信息,诸如 IP 地址、端口号、用户名、密码以及是否支持sudo等;另一种是使用密钥实现远程管理,不需要输入密码。
3.2 salt-ssh管理
在 master 上安装 salt-ssh
[root@vm1 ~]# yum -y install salt-ssh
3.2.1 通过使用用户名密码的SSH实现远程管理
修改配置文件,添加受控机信息
# host: 192.168.42.2
vm1:
host: 192.168.30.130
user: root
passwd: 147258
测试连通性
[root@vm1 ~]# salt-ssh '*' test.ping
vm2:
----------
retcode:
254
stderr:
stdout:
The host key needs to be accepted, to auto accept run salt-ssh with the -i flag:
The authenticity of host '192.168.30.130 (192.168.30.130)' can't be established.
ECDSA key fingerprint is SHA256:WdoC8gMGaS4xs7TgA0BKRY8VH9MknAX6kRCE02g3cfY.
ECDSA key fingerprint is MD5:b6:03:d2:b3:66:fc:d2:de:b9:4f:d7:78:df:7b:42:eb.
Are you sure you want to continue connecting (yes/no)?
从上面的信息可以看出,第一次访问时需要输入 yes/no ,但是 saltstack 是不支持交互式操作的,所以为了解决这个问题,我们需要对其进行设置,让系统不进行主机验证
[root@vm1 ~]# cat ~/.ssh/config
trictHostKeyChecking no
[root@vm1 ~]# salt-ssh '*' test.ping
vm2:
True
2.2 通过salt-ssh初始化系统安装salt-minion
安装 salt-ssh
修改roster配置文件,添加受控主机
见上文
测试连通性
[root@vm1 ~]# salt-ssh '*' test.ping
vm2:
True
执行状态命令,初始化系统,安装salt-minion
[root@vm1 ~]# mkdir -p /srv/salt/base/{repo,files}
[root@vm1 ~]# cp /etc/salt/minion /srv/salt/base/files
[root@vm1 ~]# wget https://repo.saltstack.com/yum/redhat/salt-repo-3000.el7.noarch.rpm
[root@vm1 ~]# mv salt-repo-3000.el7.noarch.rpm /srv/salt/base/files/
[root@vm1 ~]#vim /srv/salt/base/files/minion
----
master: 192.168.30.100
----
root@vm1 ~]# vim /srv/salt/base/repo.sls
//添加以下内容
/tmp/salt-repo-3000.el7.noarch.rpm:
file.managed:
- source: salt://files/salt-repo-3000.el7.noarch.rpm
cmd.run:
- name: yum -y localinstall /tmp/salt-repo-3000.el7.noarch.rpm
- require:
- file: /tmp/salt-repo-3000.el7.noarch.rpm
clean_cache:
cmd.run:
- name: yum clean all && yum makecache
[root@vm1 ~]# vim /srv/salt/base/minion.sls
//添加以下内容
include:
- repo
salt-minion-install:
pkg.installed:
- name: salt-minion
/etc/salt/minion:
file.managed:
- source: salt://files/minion
- user: root
- group: root
- mode: 644
salt-minion-service:
service.running:
- name: salt-minion
- disable: True
[root@vm1 ~]# salt-ssh '*' state.sls minion
[root@vm1 ~]# salt-key -yA
The following keys are going to be accepted:
Unaccepted Keys:
vm2
Key for minion vm2 ccepted.
Key for minion vm2 accepted.
[root@vm1 ~]# salt-key -L
Accepted Keys:
vm2
Denied Keys:
vm2
Unaccepted Keys:
Rejected Keys:
[root@vm1 ~]# salt '*' test.ping
vm2:
True