运维实战自动化运维 SaltStack入门

Posted 2021-05-16 洛冰音

tags:

篇首语：本文由小常识网(cha138.com)小编为大家整理，主要介绍了运维实战自动化运维 SaltStack入门相关的知识，希望对你有一定的参考价值。

运维实战自动化运维 SaltStack入门

简介
安装部署
简单使用
自行编写模块
编译安装源码的方式
Grains与Pillar详解
使用SaltStack配置Keepalived高可用
Nginx部分补漏
Job管理
扩展部分 Salt-ssh和Salt-syndic
- Salt-syndic
API调用

简介

Saltstack是一个分布式远程执行系统, 用来在远程节点上执行命令和查询数据, 能够维护预定义状态的远程节点.

核心功能

并行发送命令到远端主机, 效率更高
使用安全加密协议
最小最快的网络载荷
提供简单的编程接口

同时, 因为采用SC模式且引入了更细致的领域控制系统, 命令的执行对象不仅可以是主机名, 也可以是符合某一系统属性的主机群体.

4505是其发送端口

4506是其接收端口, 用来接收请求响应报文

Salt命令由三个主要部分构成:

salt '<target>' <function> [arguments]

target					指定哪些minion,默认使用glob匹配minion id
						也可以使用正则表达式
						也可以指定列表

安装部署

rpm --import https://repo.saltstack.com/yum/redhat/7/x86_64/latest/SALTSTACK-GPG-KEY.pub

/etc/yum.repos.d/saltstack.repo

[saltstack-repo]
name=SaltStack repo for RHEL/CentOS $releasever
baseurl=https://repo.saltstack.com/yum/redhat/$releasever/$basearch/latest
enabled=1
gpgcheck=1
gpgkey=https://repo.saltstack.com/yum/redhat/$releasever/$basearch/latest/SALTSTACK-GPG-KEY.pub

Run sudo yum clean expire-cache.

Run sudo yum update.

Install the salt-minion, salt-master, or other Salt components:

    yum install salt-master
    yum install salt-minion
    yum install salt-ssh
    yum install salt-syndic
    yum install salt-cloud
    
##在管理端安装master
yum install -y salt-master
systemctl enable salt-master
systemctl start salt-master

##在客户端安装minion
yum install -y salt-minion

##修改配置文件增加主机设置
vim /etc/salt/minion

master: 172.25.5.1

systemctl enable salt-minion
systemctl start salt-minion

简单使用

##启用管理端服务
[root@Server1 ~]# systemctl enable --now salt-master.service 
Created symlink from /etc/systemd/system/multi-user.target.wants/salt-master.service to /usr/lib/systemd/system/salt-master.service.
##在开启了客户端后,管理端可以看到未被允许的Key
[root@Server1 ~]# salt-key -L
Accepted Keys:
Denied Keys:
Unaccepted Keys:
Server2
Rejected Keys:
[root@Server1 ~]# salt-key -L
Accepted Keys:
Denied Keys:
Unaccepted Keys:
Server2
Server3
Rejected Keys:
##同意所有key
[root@Server1 ~]# salt-key -A
The following keys are going to be accepted:
Unaccepted Keys:
Server2
Server3
Proceed? [n/Y] Y
Key for minion Server2 accepted.
Key for minion Server3 accepted.
[root@Server1 ~]# salt-key -L
Accepted Keys:
Server2
Server3
Denied Keys:
Unaccepted Keys:
Rejected Keys:
##此时,客户端与管理端已经建立连接了,进行测试
[root@Server1 ~]# salt '*' test.ping
Server2:
    True
Server3:
    True

##简单编写一个部署Apache的脚本并测试
[root@Server1 _modules]# vim /srv/salt/Apache.sls
[root@Server1 _modules]# salt '*' state.sls Apache
Server2:
----------
          ID: httpd
    Function: pkg.installed
      Result: True
     Comment: The following packages were installed/updated: httpd
     Started: 14:35:21.096991
    Duration: 6100.891 ms
     Changes:   
              ----------
              apr:
                  ----------
                  new:
                      1.4.8-3.el7_4.1
                  old:
              apr-util:
                  ----------
                  new:
                      1.5.2-6.el7
                  old:
              httpd:
                  ----------
                  new:
                      2.4.6-88.el7
                  old:
              httpd-tools:
                  ----------
                  new:
                      2.4.6-88.el7
                  old:
              mailcap:
                  ----------
                  new:
                      2.1.41-2.el7
                  old:

Summary for Server2
------------
Succeeded: 1 (changed=1)
Failed:    0
------------
Total states run:     1
Total run time:   6.101 s
Server3:
----------
          ID: httpd
    Function: pkg.installed
      Result: True
     Comment: The following packages were installed/updated: httpd
     Started: 14:35:21.290611
    Duration: 6127.828 ms
     Changes:   
              ----------
              apr:
                  ----------
                  new:
                      1.4.8-3.el7_4.1
                  old:
              apr-util:
                  ----------
                  new:
                      1.5.2-6.el7
                  old:
              httpd:
                  ----------
                  new:
                      2.4.6-88.el7
                  old:
              httpd-tools:
                  ----------
                  new:
                      2.4.6-88.el7
                  old:
              mailcap:
                  ----------
                  new:
                      2.1.41-2.el7
                  old:

Summary for Server3
------------
Succeeded: 1 (changed=1)
Failed:    0
------------
Total states run:     1
Total run time:   6.128 s

文件内容

httpd:
  pkg.installed:
    - name: httpd

自行编写模块

##编写一个查看硬盘挂载信息的模块
[root@Server1 _modules]# vim /srv/salt/_modules/mydisk.py

def df():
        return __salt__['cmd.run']('df -h')

##传输给Server2
[root@Server1 _modules]# salt Server2 saltutil.sync_modules
Server2:
    - modules.mydisk
    
##可以通过该模块对Server2进行操作了
[root@Server1 _modules]# salt Server2 mydisk.df
Server2:
    Filesystem             Size  Used Avail Use% Mounted on
    /dev/mapper/rhel-root   17G  1.2G   16G   8% /
    devtmpfs               484M     0  484M   0% /dev
    tmpfs                  496M  100K  496M   1% /dev/shm
    tmpfs                  496M   13M  483M   3% /run
    tmpfs                  496M     0  496M   0% /sys/fs/cgroup
    /dev/vda1             1014M  132M  883M  14% /boot
    tmpfs                  100M     0  100M   0% /run/user/0

编译安装源码的方式

/nginx/install.sls

nginx-install:
  pkg.installed:
    - pkgs:
      - pcre-devel
      - gcc
      - openssl-devel
  file.managed:
    - source: salt://nginx/files/nginx-1.18.0.tar.gz
    - name: /mnt/nginx-1.18.0.tar.gz
  cmd.run:
    - name: cd /mnt && tar zxf nginx-1.18.0.tar.gz && cd nginx-1.18.0 && sed -i 's/CFLAGS="$CFLAGS -g"/#CFLAGS="$CFLAGS -g"/g' auto/cc/gcc &&  ./configure --prefix=/usr/local/nginx --with-http_ssl_module &> /dev/null && make &> /dev/null && make install &> /dev/null
    - creates: /usr/local/nginx

init.sls

include:
  - nginx.install

/usr/local/nginx/conf/nginx.conf:
  file.managed:
    - source: salt://nginx/files/nginx.conf
    
nginx-service:
  file.managed:
    - source: salt://nginx/files/nginx.service
    - name: /etc/systemd/system/nginx.service

  service.running:
    - name: nginx
    - enable: True
    - reload: True
    - watch:
      - file: /usr/local/nginx/conf/nginx.conf

top.sls

base:  'Server2':    - apache  'Server3':    - nginx

执行方式

salt '*' state.highstate

执行情况

[root@Server1 salt]# salt '*' state.highstate
Server2:
----------
          ID: httpd
    Function: pkg.installed
      Result: True
     Comment: All specified packages are already installed
     Started: 15:33:27.464898
    Duration: 706.589 ms
     Changes:   

Summary for Server2
------------
Succeeded: 1
Failed:    0
------------
Total states run:     1
Total run time: 706.589 ms
Server3:
----------
          ID: nginx-install
    Function: pkg.installed
      Result: True
     Comment: All specified packages are already installed
     Started: 15:33:27.667848
    Duration: 739.729 ms
     Changes:   
----------
          ID: nginx-install
    Function: file.managed
        Name: /mnt/nginx-1.18.0.tar.gz
      Result: True
     Comment: File /mnt/nginx-1.18.0.tar.gz is in the correct state
     Started: 15:33:28.410887
    Duration: 39.863 ms
     Changes:   
----------
          ID: nginx-install
    Function: cmd.run
        Name: cd /mnt && tar zxf nginx-1.18.0.tar.gz && cd nginx-1.18.0 && sed -i 's/CFLAGS="$CFLAGS -g"/#CFLAGS="$CFLAGS -g"/g' auto/cc/gcc &&  ./configure --prefix=/usr/local/nginx --with-http_ssl_module &> /dev/null && make &> /dev/null && make install &> /dev/null
      Result: True
     Comment: /usr/local/nginx exists
     Started: 15:33:28.452094
    Duration: 0.847 ms
     Changes:   
----------
          ID: /usr/local/nginx/conf/nginx.conf
    Function: file.managed
      Result: True
     Comment: File /usr/local/nginx/conf/nginx.conf is in the correct state
     Started: 15:33:28.453164
    Duration: 13.671 ms
     Changes:   
----------
          ID: nginx-service
    Function: file.managed
        Name: /etc/systemd/system/nginx.service
      Result: True
     Comment: File /etc/systemd/system/nginx.service is in the correct state
     Started: 15:33:28.467170
    Duration: 13.336 ms
     Changes:   
----------
          ID: nginx-service
    Function: service.running
        Name: nginx
      Result: True
     Comment: The service nginx is already running
     Started: 15:33:28.481955
    Duration: 54.933 ms
     Changes:   

Summary for Server3
------------
Succeeded: 6
Failed:    0
------------
Total states run:     6
Total run time: 862.379 ms

测试

[root@Server3 salt]# curl localhost
<!DOCTYPE html>
<html>
<head>
<title>Welcome to nginx!</title>
<style>
    body {
        width: 35em;
        margin: 0 auto;
        font-family: Tahoma, Verdana, Arial, sans-serif;
    }
</style>
</head>
<body>
<h1>Welcome to nginx!</h1>
<p>If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.</p>

<p>For online documentation and support please refer to
<a href="http://nginx.org/">nginx.org</a>.<br/>
Commercial support is available at
<a href="http://nginx.com/">nginx.com</a>.</p>

<p><em>Thank you for using nginx.</em></p>
</body>
</html>

Grains与Pillar详解

Grains

Grains是SaltStack的一个组件, 存放在SaltStack的minion端.

当salt-minion启动时会把收集到的数据静态存放在Grains当中, 只有当minion重启时才会进行数据的更新.

由于grains是静态数据, 因此不推荐经常去修改它.

应用场景

信息查询
在target中使用, 匹配minion.
在state系统中使用, 配置管理模块.

举例

显示所有可用的grains

salt '*' grains.ls

使用grains.item列出信息

salt '*' grains.items

尝试取值

[root@Server1 salt]# salt Server2  grains.item ipv4
Server2:
    ----------
    ipv4:
        - 127.0.0.1
        - 172.25.5.2

在Server2上编辑

grains:
  roles:
    - webserver
    - memcache
    - Apache
  deployment: datacenter4
  cabinet: 13
  cab_u: 14-15

Server1同步后检测

[root@Server1 salt]# salt Server2  saltutil.sync_grains
Server2:
[root@Server1 salt]# salt Server2  grains.item roles
Server2:
    ----------
    roles:
        - webserver
        - memcache
        - Apache

删除刚才添加的信息后重启被控端

[root@Server1 salt]# salt Server2  grains.item roles
Server2:
    ----------
    roles:
        - webserver
        - memcache
        - Apache
[root@Server1 salt]# salt Server2  grains.item roles
^[[B^[[A^[[A^[[BServer2:
    Minion did not return. [Not connected]
ERROR: Minions returned with non-zero exit code
[root@Server1 salt]# salt Server2  grains.item roles
Server2:
    ----------
    roles:
        - webserver
        - memcache

也可以写入Grains in /etc/salt/grains

roles:
  - webserver
  - memcache
deployment: datacenter4
cabinet: 13
cab_u: 14-15

与上面的作用是一样的.

如果在master端操作就需要创建目录

mkdir /srv/salt/_grains

vim mygrains.py


#!/usr/bin/env python
def yourfunction():
     # initialize a grains dictionary
     grains = {}
     # Some code for logic that sets grains like
     grains['yourcustomgrain'] = True
     grains['anothergrain'] = 'somevalue'
     return grains
     
     
salt '*' saltutil.sync_grains

在两台虚拟机都作了操作后, Grains也可以用来在传输时做配置分流

[root@Server1 salt]# salt -G roles:memcache cmd.run hostname
Server2:
    Server2
Server3:
    Server3

Pillar

pillar和grains一样也是一个数据系统, 但是应用场景不同.

pillar是将信息动态的存放在master端, 主要存放私密/敏感信息如(用户名密码等), 而且可以指定某一个minion才可以看到对应的信息.

pillar更加适合在配置管理中运用.

动态, 存储在MASTER端
独立于base目录
修改后不需要刷新, 更适合集群操作

声明Pillar

##定义pillar基础目录
vim /etc/salt/master

pillar_roots:
  base:
    - /srv/pillar
    
mkdir /srv/pillar

##重启salt-master服务
/etc/init.d/salt-master restart

自定义Pillar项

vim /srv/pillar/top.sls

base:
  '*':
    - packages
    

vim /srv/pillar/packages.sls

{% if grains['fqdn'] == 'server3' %}
package: httpd
{% elif grains['fqdn'] == 'server2' %}
package: mairadb
{% endif %}



##刷新pillar数据
salt '*' saltutil.refresh_pillar
##查询pillar数据
salt '*' pillar.items
salt '*' pillar.item  roles


##在命令行中匹配
salt -I 'roles:apache' test.ping
##在state系统中使用
vim /srv/salt/apache.sls

apache:
  pkg.installed:
    - name: {{ pillar['package'] }}

使用Jinja模板

使用Jinja模板需要记住的用法

两种分隔符: {% ... %}和 {{ ... }}

前者用于执行诸如for 循环或赋值的语句

后者把表达式的结果打印到模板上

基本用法

##用来控制结构包装条件
vim /srv/salt/test.sls

/mnt/testfile:
  file.append:
    {% if grains['fqdn'] == 'server2' %}
    - text: server2
    {% elif grains['fqdn'] == 'server3' %}
    - text: server3
    {% endif %}
    
通过这种用法,可以对不同主机的同一位置文件写入不同内容

##在这个例子中, 用来往普通文件中写入信息
vim /srv/salt/apache.sls

/etc/httpd/conf/httpd.conf:
  file.managed:
  - source: salt://httpd.conf
  - template: jinja
  - context:
    bind: 172.25.0.2

##使用import方式,可在state文件之间共享信息
##使用变量文件定义变量
vim lib.sls

{% set port = 80 %}

##传递变量给配置文件并写入信息
# vim httpd.conf

{% from 'lib.sls' import port %}
...
Listen {{ prot }}

引用变量的几种方式

##直接引用grains变量
Listen {{ grains['ipv4'][1] }}

##直接引用pillar变量
Listen {{ pillar['ip'] }}

##在state文件中引用
- template: jinja
    - context:
      bind: {{ pillar['ip'] }}

使用SaltStack配置Keepalived高可用

明确需要做的事情的步骤

建立Keepalived目录并编写合适的入口文件init.sls
因为机器分为主机和备机, 而需要使用同一个模板因此一定需要定义变量
配置模板中使用的变量在pillar/Keepalived.sls中取值, 在Keepalived/init.sls中赋值,在模板中调用
在salt/top.sls中为所有机器配置Keepalived

kp-install:
  pkg.installed:
    - name: keepalived

  file.managed:
    - source: salt://Keepalived/files/keepalived.conf
    - name: /etc/keepalived/keepalived.conf
    - template: jinja
    - context:
      STATE: {{ pillar['kp-state'] }}
      VRID: {{ pillar['kp-vrid'] }}
      PRI: {{ pillar['kp-pri'] }}

  service.running:
    - name: keepalived
    - enable: True
    - reload: True
    - watch:
      - file: kp-install

pillar/keepalived.sls内容

{% if grains['fqdn'] == 'Server2' %}
kp-state: MASTER
kp-vrid: 5
kp-pri: 100
{% elif grains['fqdn'] == 'Server3' %}
kp-state: BACKUP
kp-vrid: 5
kp-pri: 50
{% endif %}

pillar/top.sls内容

base:
  '*':
    - Keepalived

salt/top.sls内容

base:
  'Server2':
    - Keepalived
  'Server3':
    - Keepalived

配置文件

执行salt '*' state.highstate

执行结果

Server2:
----------
          ID: kp-install
    Function: pkg.installed
        Name: keepalived
      Result: True
     Comment: All specified packages are already installed
     Started: 10:18:26.395059
    Duration: 701.955 ms
     Changes:   
----------
          ID: kp-install
    Function: file.managed
        Name: /etc/keepalived/keepalived.conf
      Result: True
     Comment: File /etc/keepalived/keepalived.conf updated
     Started: 10:18:27.101137
    Duration: 46.93 ms
     Changes:   
              ----------
              diff:
                  --- 
                  +++ 
                  @@ -15,10 +15,10 @@
                   }
                   
                   vrrp_instance VI_1 {
                  -    state { STATE }
                  +    state MASTER
                       interface eth0
                  -    virtual_router_id { VRID }
                  -    priority { PRI }
                  +    virtual_router_id 5
                  +    priority 100
                       advert_int 1
                       authentication {
                           auth_type PASS
----------
          ID: kp-install
    Function: service.running
        Name: keepalived
      Result: True
     Comment: Service keepalived is already enabled, and is running
     Started: 10:18:27.149461
    Duration: 146.67 ms
     Changes:   
              ----------
              keepalived:
                  True

Summary for Server2
------------
Succeeded: 3 (changed=2)
Failed:    0
------------
Total states run:     3
Total run time: 895.555 ms
Server3:
----------
          ID: kp-install
    Function: pkg.installed
        Name: keepalived
      Result: True
     Comment: All specified packages are already installed
     Started: 10:18:26.594020
    Duration: 778.537 ms
     Changes:   
----------
          ID: kp-install
    Function: file.managed
        Name: /etc/keepalived/keepalived.conf
      Result: True
     Comment: File /etc/keepalived/keepalived.conf updated
     Started: 10:18:27.376387
    Duration: 47.47 ms
     Changes:   
              ----------
              diff:
                  --- 
                  +++ 
                  @@ -15,10 +15,10 @@
                   }
                   
                   vrrp_instance VI_1 {
                  -    state { STATE }
                  +    state BACKUP
                       interface eth0
                  -    virtual_router_id { VRID }
                  -    priority { PRI }
                  +    virtual_router_id 5
                  +    priority 50
                       advert_int 1
                       authentication {
                           auth_type PASS
----------
          ID: kp-install
    Function: service.running
        Name: keepalived
      Result: True
     Comment: Service keepalived is already enabled, and is running
     Started: 10:18:27.425795
    Duration: 157.849 ms
     Changes:   
              ----------
              keepalived:
                  True

Summary for Server3
------------
Succeeded: 3 (changed=2)
Failed:    0
------------
Total states run:     3
Total run time: 983.856 ms

观察到Server2上出现VIP

宿主机curl VIP可以得到反馈
down掉Server2上的keepalived, BACKUP转为MASTER, VIP漂移, 因此curl结果变更

[root@foundation5 ~]# curl 172.25.5.100
Server2
[root@foundation5 ~]# curl 172.25.5.100
<!DOCTYPE html>
<html>
<head>
<title>Welcome to nginx!</title>
<style>
    body {
        width: 35em;
        margin: 0 auto;
        font-family: Tahoma, Verdana, Arial, sans-serif;
    }
</style>
</head>
<body>
<h1>Welcome to nginx!</h1>
<p>If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.</p>

<p>For online documentation and support please refer to
<a href="http://nginx.org/">nginx.org</a>.<br/>
Commercial support is available at
<a href="http://nginx.com/">nginx.com</a>.</p>

<p><em>Thank you for using nginx.</em></p>
</body>
</html>

Nginx部分补漏

nginx/init.sls内容

include:
  - Nginx.install

nginx.conf:
  file.managed:
    - source: salt://Nginx/files/nginx.conf
    - name: /usr/local/nginx/conf/nginx.conf

nginx.service:
  file.managed:
    - source: salt://Nginx/files/nginx.service
    - name: /etc/systemd/system/nginx.service

  service.running:
    - name: nginx
    - enable: True
    - reload: True
    - watch:
      - file: nginx.conf

nginx/install.sls内容

nginx-install:
  pkg.installed:
    - pkgs:
      - pcre-devel
      - gcc
      - openssl-devel
  file.managed:
    - source: salt://Nginx/files/nginx-1.18.0.tar.gz
    - name: /mnt/nginx-1.18.0.tar.gz
  cmd.run:
    - name: cd /mnt && tar zxf nginx-1.18.0.tar.gz && cd nginx-1.18.0 && sed -i 's/CFLAGS="$CFLAGS -g"/#CFLAGS="$CFLAGS -g"/g' auto/cc/gcc &&  ./configure --prefix=/usr/local/nginx --with-http_ssl_module &> /dev/null && make &> /dev/null && make install &> /dev/null
    - creates: /usr/local/nginx

nginx.service内容

[Unit]
Description=The NGINX HTTP and reverse proxy server
After=syslog.target network.target remote-fs.target nss-lookup.target

[Service]
Type=forking
PIDFile=/usr/local/nginx/logs/nginx.pid
ExecStartPre=/usr/local/nginx/sbin/nginx -t
ExecStart=/usr/local/nginx/sbin/nginx
ExecReload=/usr/local/nginx/sbin/nginx -s reload
ExecStop=/bin/kill -s QUIT $MAINPID
PrivateTmp=true

[Install]
WantedBy=multi-user.target

salt/top.sls内容

base:
  'Server2':
    - Keepalived
  'Server3':
    - Nginx
    - Keepalived

Job管理

Job缓存默认保存24小时

vim /etc/salt/master

keep_jobs: 24

MASTER端Job缓存目录/var/cache/salt/master/jobs

为了自动化运维一定要配置数据库

master安装

yum install -y mysql-python.x86_64
yum install -y MySQL-python.x86_64

修改配置文件master

vim /etc/salt/master

master_job_cache: mysql
mysql.host: 127.0.0.1
mysql.user: 'salt'
mysql.pass: 'salt'
mysql.db: 'salt'
mysql.port: 3306

启动数据库, 导入官方提供的mysql脚本

CREATE DATABASE  `salt`
  DEFAULT CHARACTER SET utf8
  DEFAULT COLLATE utf8_general_ci;

USE `salt`;

--
-- Table structure for table `jids`
--

DROP TABLE IF EXISTS `jids`;
CREATE TABLE `jids` (
  `jid` varchar(255) NOT NULL,
  `load` mediumtext NOT NULL,
  UNIQUE KEY `jid` (`jid`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
CREATE INDEX jid ON jids(jid) USING BTREE;

--
-- Table structure for table `salt_returns`
--

DROP TABLE IF EXISTS `salt_returns`;
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;

--
-- Table structure for table `salt_events`
--

DROP TABLE IF EXISTS `salt_events`;
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;

登陆数据库做授权操作

grant all on salt.* to salt@'localhost' identified by 'salt';

grant all on salt.* to salt@'%' identified by 'salt';

做登陆测试

mysql -usalt -psalt salt

重启服务并测试

systemctl restart salt-master

salt server3 cmd.run hostname

查看数据库

mysql -usalt -psalt salt

MariaDB [(none)]> use salt;
MariaDB [salt]> select * from salt_returns;
+---------+----------------------+-----------+---------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
| fun     | jid                  | return    | id      | success | full_ret                                                                                                                                                                                                   | alter_time          |
+---------+----------------------+-----------+---------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
| cmd.run | 20210425035148815274 | "Server2" | Server2 | 1       | {"fun_args": ["hostname"], "jid": "20210425035148815274", "return": "Server2", "retcode": 0, "success": true, "cmd": "_return", "_stamp": "2021-04-25T03:51:49.175288", "fun": "cmd.run", "id": "Server2"} | 2021-04-25 11:51:49 |
| cmd.run | 20210425035148815274 | "Server3" | Server3 | 1       | {"fun_args": ["hostname"], "jid": "20210425035148815274", "return": "Server3", "retcode": 0, "success": true, "cmd": "_return", "_stamp": "2021-04-25T03:51:49.245092", "fun": "cmd.run", "id": "Server3"} | 2021-04-25 11:51:49 |
+---------+----------------------+-----------+---------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
2 rows in set (0.00 sec)

扩展部分 Salt-ssh和Salt-syndic

使用salt-ssh不需要minion端, 可以便于某些不能安装minion端的设备进入管理范围.

##首先在管理端安装salt-ssh
##编辑配置文件,填入客户端信息
vim roster

Server3:
  host: 172.25.5.3
  user: root
  passwd: westos
# sudo: True

如果需要sudo可以打开选项

因为使用ssh方式因此客户端不

以上是关于运维实战自动化运维 SaltStack入门的主要内容，如果未能解决你的问题，请参考以下文章

SaltStack 入门

Saltstack自动化运维工具实战与部署

[实战]python开发自动化运维工具--批量操作主机

实战小项目python开发自动化运维工具--批量操作主机

linux运维架构之路-SaltStack快速入门

本周重磅原来SaltStack 可以这么玩

运维实战 自动化运维 SaltStack入门

运维实战 自动化运维 SaltStack入门

简介

安装部署

简单使用

自行编写模块

编译安装源码的方式

Grains与Pillar详解

Grains

Pillar

声明Pillar

自定义Pillar项

使用Jinja模板

引用变量的几种方式

使用SaltStack配置Keepalived高可用

Nginx部分补漏

Job管理

扩展部分 Salt-ssh和Salt-syndic

运维实战自动化运维 SaltStack入门

运维实战自动化运维 SaltStack入门