SaltStack之return与job管理
文章目录
SaltStack组件之return
return组件可以理解为SaltStack系统对执行Minion返回后的数据进行存储或者返回给其他程序，它支持多种存储方式，比如用MysqL、MongoDB、Redis、Memcache等，通过return我们可以对SaltStack的每次操作进行记录，对以后日志审计提供了数据来源。目前官方已经支持30种return数据存储与接口，我们可以很方便的配置与使用它。当然也支持自己定义的return，自定义的return需由python来编写。在选择和配置好要使用的return后，只需在salt命令后面指定return即可。
#查看所有return列表
[root@master ~]# salt '*' sys.list_returners
minion1:
- carbon
- couchdb
- etcd
- highstate
- local
- local_cache
- mattermost
- multi_returner
- pushover
- rawfile_json
- slack
- slack_webhook
- smtp
- splunk
- sqlite3
- syslog
- telegram
return流程
return是在Master端触发任务，然后Minion接受处理任务后直接与return存储服务器建立连接，然后把数据return存到存储服务器。关于这点一定要注意，因为此过程都是Minion端操作存储服务器，所以要确保Minion端的配置跟依赖包是正确的，这意味着我们将必须在每个Minion上安装指定的return方式依赖包，假如使用MysqL作为return存储方式，那么我们将在每台Minion上安装python-MysqL模块。
使用MysqL作为return存储方式
[root@master ~]# salt '*' pkg.install python3-PyMysqL
minion1:
----------
python3-PyMysqL:
----------
new:
0.10.1-2.module_el8.5.0+761+faacb0fb
old:
python3-cffi:
----------
new:
1.11.5-5.el8
old:
python3-cryptography:
----------
new:
3.2.1-5.el8
old:
python3-ply:
----------
new:
3.9-9.el8
old:
python3-pycparser:
----------
new:
2.14-14.el8
old:
部署一台MysqL服务器用作存储服务器，此处就直接在MysqL这台主机上部署
[root@MysqL ~]# yum -y install mariadb-server
[root@MysqL ~]# systemctl start mariadb
[root@MysqL ~]# ss -antl
State Recv-Q Send-Q Local Address:Port Peer Address:PortProcess
LISTEN 0 128 0.0.0.0:22 0.0.0.0:*
LISTEN 0 80 *:3306 *:*
LISTEN 0 128 [::]:22 [::]:*
#创建数据库和表结构
[root@MysqL ~]# MysqL
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 8
Server version: 10.3.28-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.001 sec)
MariaDB [(none)]> USE `salt`;
Database changed
MariaDB [salt]> DROP TABLE IF EXISTS `jids`;
Query OK, 0 rows affected, 1 warning (0.001 sec)
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.004 sec)
MariaDB [salt]> DROP TABLE IF EXISTS `salt_returns`;
Query OK, 0 rows affected, 1 warning (0.001 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.006 sec)
MariaDB [salt]> DROP TABLE IF EXISTS `salt_events`;
Query OK, 0 rows affected, 1 warning (0.000 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.004 sec)
#配置访问权限
MariaDB [salt]> grant all on salt.* to salt@'192.168.96.%' identified by 'salt';
Query OK, 0 rows affected (0.001 sec)
MariaDB [salt]> flush privileges;
Query OK, 0 rows affected (0.001 sec)
配置minion
[root@minion1 ~]# vim /etc/salt/minion
MysqL.host: '192.168.96.134'
MysqL.user: 'salt'
MysqL.pass: 'salt'
MysqL.db: 'salt'
MysqL.port: 3306
[root@minion1 ~]# systemctl restart salt-minion
在Master上测试存储到MysqL中
[root@master ~]# salt '*' test.ping --return MysqL
minion1:
True
MariaDB [salt]> select * from salt_returns\G
*************************** 1. row ***************************
fun: test.ping
jid: 20210708130825126962
return: true
id: minion1
success: 1
full_ret: {"success": true, "return": true, "retcode": 0, "jid": "20210708130825126962", "fun": "test.ping", "fun_args": [], "id": "minion1"}
alter_time: 2021-07-08 21:08:25
1 row in set (0.001 sec)
job cache
job cache流程
return时是由Minion直接与存储服务器进行交互，因此需要在每台Minion上安装指定的存储方式的模块，比如python-MysqL，那么我们能否直接在Master上就把返回的结果给存储到存储服务器呢？
答案是肯定的，这种方式被称作 job cache 。意思是当Minion将结果返回给Master后，由Master将结果给缓存在本地，然后将缓存的结果给存储到指定的存储服务器，比如存储到MysqL中。
开启master端的master_job_cache
[root@master ~]# yum -y install python3-PyMysqL
[root@master ~]# vim /etc/salt/master
#return: MysqL
master_job_cache: MysqL
MysqL.host: '192.168.96.134'
MysqL.user: 'salt'
MysqL.pass: 'salt'
MysqL.db: 'salt'
MysqL.port: 3306
[root@master ~]# systemctl restart salt-master
MariaDB [(none)]> delete from salt.salt_returns;
Query OK, 1 row affected (0.002 sec)
MariaDB [(none)]> select * from salt.salt_returns;
Empty set (0.000 sec)
在master上再次测试能否存储至数据库
[root@master ~]# salt '*' test.ping
minion1:
True
MariaDB [(none)]> select * from salt.salt_returns;
Empty set (0.000 sec)
MariaDB [(none)]> select * from salt.salt_returns\G
*************************** 1. row ***************************
fun: test.ping
jid: 20210708131602141349
return: true
id: minion1
success: 1
full_ret: {"cmd": "_return", "id": "minion1", "success": true, "return": true, "retcode": 0, "jid": "20210708131602141349", "fun": "test.ping", "fun_args": [], "_stamp": "2021-07-08T13:16:02.347617"}
alter_time: 2021-07-08 21:16:02
job管理
获取任务的jid
[root@master ~]# salt '*' cmd.run 'uptime' -v
Executing job with jid 20210708131824562090 #此处就是此命令的jid
-------------------------------------------
minion1:
21:18:24 up 1:12, 4 users, load average: 0.00, 0.00, 0.00
通过jid获取此任务的返回结果
[root@master ~]# salt-run jobs.lookup_jid 20210708131824562090
minion1:
21:18:24 up 1:12, 4 users, load average: 0.00, 0.00, 0.00
版权声明：本文内容由互联网用户自发贡献，该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容， 请发送邮件至 [email protected] 举报，一经查实，本站将立刻删除。
