SaltStack配置管理

最新推荐文章于 2024-09-19 21:14:20 发布

阿木690

最新推荐文章于 2024-09-19 21:14:20 发布

阅读量106

点赞数 1

分类专栏：运维 linux 文章标签： saltstack 自动化工具

本文链接：https://blog.csdn.net/Gf19991225/article/details/121098849

版权

linux 同时被 2 个专栏收录

49 篇文章 1 订阅

订阅专栏

运维

34 篇文章 1 订阅

订阅专栏

文章目录

一、YAML语言
二、用SaltStack配置一个apache实例
- 2.1 在Master上部署sls配置文件并执行
- 2.2 在node1主机上检查
三、top file
- 3.1 top file介绍
- 3.2 高级状态highstate的使用

一、YAML语言

YAML是一种直观的能够被电脑识别的数据序列化格式，是一个可读性高并且容易被人类阅读，容易和脚本语言交互，用来表达资料序列的编程语言。

它类似于标准通用标记语言的子集XML的数据描述语言，语法比XML简单很多。

YAML语言的格式如下：

house:
  family:
    name: Doe
    parents:
      - John
      - Jane
    children:
      - Paul
      - Mark
      - Simone
  address:
    number: 34
    street: Main Street
    city: Nowheretown
    zipcode: 12345

YAML的基本规则：

使用缩进来表示层级关系，每层2个空格，禁止使用TAB键
当冒号不是处于最后时，冒号后面必须有一个空格
用 - 表示列表，- 的后面必须有一个空格
用 # 表示注释

YAML配置文件要放到SaltStack让我们放的位置，可以在SaltStack的 Master 配置文件中查找file_roots即可看到。

// 查看帮助文档
[root@master ~]# cd /etc/salt/
[root@master salt]# ls
cloud           cloud.profiles.d   minion     proxy
cloud.conf.d    cloud.providers.d  minion.d   proxy.d
cloud.deploy.d  master             minion_id  roster
cloud.maps.d    master.d           pki
[root@master salt]# vim master
# file_roots:
#   base:
#     - /srv/salt/
#   dev:
#     - /srv/salt/dev/services
#     - /srv/salt/dev/states
#   prod:
#     - /srv/salt/prod/services
#     - /srv/salt/prod/states
#
#file_roots:
#  base:
#    - /srv/salt


// base：基础环境（这里面的配置所有主机通用）
// test：测试环境（仅仅只给测试环境使用的）
// dev：开发环境（仅仅只给开发环境使用的）
// prod：生成环境（仅仅只给生成环境使用的）
所有我们不要像上面的帮助文档那样设置

// 修改配置文件
[root@master salt]# vim master
#file_roots:
#  base:
#    - /srv/salt
#

file_roots:		// 自己编写一个
  base:
    - /srv/salt/base
  dev:
    - /srv/salt/dev
  prod:
    - /srv/salt/prod
  test:
    - /srv/salt/test

// 创建环境目录
[root@master salt]# tree /srv/
/srv/

0 directories, 0 files
[root@master salt]# mkdir -p /srv/salt/{base,test,dev,prod}
[root@master salt]# tree /srv/
/srv/
`-- salt
    |-- base
    |-- dev
    |-- prod
    `-- test

// 重启服务
[root@master salt]# systemctl restart salt-master

需要注意：

base是默认的位置，如果file_roots只有一个，则base是必备的且必须叫base，不能改名

二、用SaltStack配置一个apache实例

环境说明：

主机名字	主机类型	IP	系统	需要安装的应用
master	控制机	192.168.91.135	CentOS8	salt-master salt-minion
node1	被控机	192.168.91.137	CentOS8	salt-minion
node2	被控机	192.168.91.134	CentOS8	salt-minion
node3	被控机	192.168.91.138	CentOS8	salt-minion

注意：node1 这台主机设置过id，访问的时候以 IP 名访问，不再是主机名字访问

2.1 在Master上部署sls配置文件并执行

// 创建一个apache目录
[root@master salt]# cd /srv/salt/base/
[root@master base]# ls
[root@master base]# mkdir -p web/apache
[root@master base]# tree
.
`-- web
    `-- apache

2 directories, 0 files

// 生成一个状态描述文件
[root@master base]# vim web/apache/install.sls
apache-install:
  pkg.installed:
    - name: httpd  // 安装httpd

apache-service:
  service.running:
    - name: httpd
    - enable: True  // 运行httpd,设置自启动

// YAML 配置文件中顶格写的被称作ID，必须全局唯一，不能重复
// SaltStack 读 YAML 配置文件时是从上往下读，所以要把先执行的写在前面

// 查看node1主机是否有apache服务
[root@node1 ~]# rpm -qa | grep httpd
[root@node1 ~]# 	// 没有apache服务

// 测试node1主机能否ping通
[root@master base]# salt "192.168.91.137" test.ping
192.168.91.137:
    True

// 在192.168.91.137主机执行state状态函数，在web.apache.apache文件下执行
[root@master base]# salt '192.168.91.137' state.sls web.apache.install saltenv=base

// saltnev：指定环境，默认是base环境
192.168.91.137:
----------
          ID: apache-install
    Function: pkg.installed
        Name: httpd
      Result: True
     Comment: The following packages were installed/updated: httpd
     Started: 14:48:59.409563
    Duration: 21188.407 ms
     Changes:   
              ----------
              apr:
                  ----------
                  new:
                      1.6.3-12.el8
                  old:
              apr-util:
                  ----------
                  new:
                      1.6.1-6.el8
                  old:
              apr-util-bdb:
                  ----------
                  new:
                      1.6.1-6.el8
                  old:
              apr-util-openssl:
                  ----------
                  new:
                      1.6.1-6.el8
                  old:
              centos-logos-httpd:
                  ----------
                  new:
                      85.8-1.el8
                  old:
              httpd:
                  ----------
                  new:
                      2.4.37-40.module_el8.5.0+852+0aafc63b
                  old:
              httpd-filesystem:
                  ----------
                  new:
                      2.4.37-40.module_el8.5.0+852+0aafc63b
                  old:
              httpd-tools:
                  ----------
                  new:
                      2.4.37-40.module_el8.5.0+852+0aafc63b
                  old:
              mailcap:
                  ----------
                  new:
                      2.1.48-3.el8
                  old:
              mod_http2:
                  ----------
                  new:
                      1.15.7-3.module_el8.4.0+778+c970deab
                  old:
----------
          ID: apache-service
    Function: service.running
        Name: httpd
      Result: True
     Comment: Service httpd has been enabled, and is running
     Started: 14:49:20.627691
    Duration: 2168.635 ms
     Changes:   
              ----------
              httpd:
                  True

Summary for 192.168.91.137
------------
Succeeded: 2 (changed=2)
Failed:    0
------------
Total states run:     2
Total run time:  23.357 s

2.2 在node1主机上检查

// 查看安装情况
[root@node1 ~]# rpm -qa | grep httpd
httpd-filesystem-2.4.37-40.module_el8.5.0+852+0aafc63b.noarch
centos-logos-httpd-85.8-1.el8.noarch
httpd-2.4.37-40.module_el8.5.0+852+0aafc63b.x86_64
httpd-tools-2.4.37-40.module_el8.5.0+852+0aafc63b.x86_64

// 查看apache服务启动情况
[root@node1 ~]# systemctl status httpd
● httpd.service - The Apache HTTP Server
   Loaded: loaded (/usr/lib/systemd/system/httpd.service; e>
   Active: active (running) since Tue 2021-11-02 14:49:22 C>
     Docs: man:httpd.service(8)
 Main PID: 531114 (httpd)
   Status: "Running, listening on: port 80"
    Tasks: 213 (limit: 23484)
   Memory: 42.8M
   CGroup: /system.slice/httpd.service
           ├─531114 /usr/sbin/httpd -DFOREGROUND
           ├─531789 /usr/sbin/httpd -DFOREGROUND
           ├─531790 /usr/sbin/httpd -DFOREGROUND
           ├─531791 /usr/sbin/httpd -DFOREGROUND
           └─531792 /usr/sbin/httpd -DFOREGROUND

Nov 02 14:49:20 node1 systemd[1]: Starting The Apache HTTP >
Nov 02 14:49:22 node1 httpd[531114]: AH00558: httpd: Could >
Nov 02 14:49:22 node1 systemd[1]: Started The Apache HTTP S>
Nov 02 14:49:41 node1 httpd[531114]: Server configured, lis>

web 页面访问测试
在这里插入图片描述

由以上内容可知apache确实已部署成功。

// 在测试环境里面执行
[root@master base]# tree
.
`-- web
    `-- apache
        `-- install.sls

2 directories, 1 file
[root@master base]# cp -r web ../test
[root@master base]# tree ../test
../test
`-- web
    `-- apache
        `-- install.sls

2 directories, 1 file
[root@master base]# salt '192.168.91.137' state.sls web.apache.install saltenv=test
192.168.91.137:
----------
          ID: apache-install
    Function: pkg.installed
        Name: httpd
      Result: True
     Comment: All specified packages are already installed
     Started: 15:02:53.841175
    Duration: 647.493 ms
     Changes:   
----------
          ID: apache-service
    Function: service.running
        Name: httpd
      Result: True
     Comment: The service httpd is already running
     Started: 15:02:54.490562
    Duration: 44.13 ms
     Changes:   

Summary for 192.168.91.137
------------
Succeeded: 2
Failed:    0
------------
Total states run:     2
Total run time: 691.623 ms

执行状态文件的技巧：

先用test.ping测试需要执行状态文件的主机是否能正常通信，然后再执行状态文件

三、top file

3.1 top file介绍

直接通过命令执行sls文件时够自动化吗？答案是否定的，因为我们还要告诉某台主机要执行某个任务，自动化应该是我们让它干活时，它自己就知道哪台主机要干什么活，但是直接通过命令执行sls文件并不能达到这个目的，为了解决这个问题，top file 应运而生。

top file就是一个入口，top file的文件名可通过在 Master的配置文件中搜索top.sls找出，且此文件必须在 base 环境中，默认情况下此文件必须叫top.sls。

top file的作用就是告诉对应的主机要干什么活，比如让web服务器启动web服务，让数据库服务器安装mysql等等。

top file 实例：
在node1主机上安装httpd，node2主机上安装nginx，node3主机上安装httpd

准备工作

// 先卸载node1主机上的httpd服务
[root@node1 ~]# yum -y remove httpd
卸载过程省略...

[root@node1 ~]# rpm -qa | grep httpd
[root@node1 ~]# 
[root@node1 ~]# ss -antl
State  Recv-Q Send-Q Local Address:Port   Peer Address:Port Process                                                     
LISTEN 0      128          0.0.0.0:22          0.0.0.0:*                                                                
LISTEN 0      128             [::]:22             [::]:*                                                                
[root@node1 ~]# systemctl status httpd
Unit httpd.service could not be found.

// 检查node2主机有没有安装nginx服务
[root@node2 ~]# rpm -qa | grep nginx
[root@node2 ~]# 

// 检查node3主机有没有安装httpd服务
[root@node3 ~]# rpm -qa | grep httpd
[root@node3 ~]#

实际操作

// 创建mariadb目录
[root@master base]# ls
web
[root@master base]# mkdir -p web/nginx
[root@master base]# tree
.
`-- web
    |-- apache
    |   `-- install.sls
    `-- nginx

3 directories, 1 file


// 编写一个nginx的安装文件
[root@master base]# vim web/nginx/install.sls
nginx-install:
  pkg.installed:
    - name: nginx

nginx-service:
  service.running:
    - name: nginx
    - enable: True

[root@master base]# tree
.
`-- web
    |-- apache
    |   `-- install.sls
    `-- nginx
        `-- install.sls

3 directories, 2 files

[root@master base]# pwd
/srv/salt/base
[root@master base]# vim top.sls
base:	// 要执行状态文件的环境
  192.168.91.137:	// 要执行状态文件的目标
    - web.apache.install	// 要执行的状态文件
  node2:
    - web.nginx.install
  node3：
    - web.apache.install

// 检查主机连接情况
[root@master base]# salt '*' test.ping
192.168.91.137:
    True
master:
    True
node2:
    True
node3:
    True


//使用高级状态来执行
[root@master base]# salt '*' state.highstate
master:
----------
          ID: states
    Function: no.None
      Result: False
     Comment: No Top file or master_tops data matches found. Please see master log for details.
     Changes:   // master这里报错，是因为master这台主机上我没有定义，是正常的

Summary for master
------------
Succeeded: 0
Failed:    1
------------
Total states run:     1
Total run time:   0.000 ms
192.168.91.137:
----------
          ID: apache-install
    Function: pkg.installed
        Name: httpd
      Result: True
     Comment: All specified packages are already installed
     Started: 16:31:58.727210
    Duration: 809.511 ms
     Changes:   
----------
          ID: apache-service
    Function: service.running
        Name: httpd
      Result: True
     Comment: The service httpd is already running
     Started: 16:31:59.539214
    Duration: 51.557 ms
     Changes:   

Summary for 192.168.91.137
------------
Succeeded: 2
Failed:    0
------------
Total states run:     2
Total run time: 861.068 ms
node2:
----------
          ID: nginx-isntall
    Function: pkg.installed
        Name: nginx
      Result: True
     Comment: All specified packages are already installed
     Started: 16:32:01.415844
    Duration: 1112.745 ms
     Changes:   
----------
          ID: nginx-service
    Function: service.running
        Name: nginx
      Result: True
     Comment: The service nginx is already running
     Started: 16:32:02.533262
    Duration: 59.586 ms
     Changes:   

Summary for node2
------------
Succeeded: 2
Failed:    0
------------
Total states run:     2
Total run time:   1.172 s
node3:
----------
          ID: apache-install
    Function: pkg.installed
        Name: httpd
      Result: True
     Comment: All specified packages are already installed
     Started: 16:32:02.523591
    Duration: 1346.453 ms
     Changes:   
----------
          ID: apache-service
    Function: service.running
        Name: httpd
      Result: True
     Comment: The service httpd is already running
     Started: 16:32:03.877325
    Duration: 192.106 ms
     Changes:   

Summary for node3
------------
Succeeded: 2
Failed:    0
------------
Total states run:     2
Total run time:   1.539 s

// 检测
[root@node1 ~]# rpm -qa | grep httpd
httpd-2.4.37-40.module_el8.5.0+852+0aafc63b.x86_64
httpd-tools-2.4.37-40.module_el8.5.0+852+0aafc63b.x86_64
httpd-filesystem-2.4.37-40.module_el8.5.0+852+0aafc63b.noarch
centos-logos-httpd-85.8-1.el8.noarch

[root@node2 ~]# rpm -qa | grep nginx
nginx-mod-stream-1.14.1-9.module_el8.0.0+184+e34fea82.x86_64
nginx-filesystem-1.14.1-9.module_el8.0.0+184+e34fea82.noarch
nginx-mod-http-perl-1.14.1-9.module_el8.0.0+184+e34fea82.x86_64
nginx-mod-mail-1.14.1-9.module_el8.0.0+184+e34fea82.x86_64
nginx-1.14.1-9.module_el8.0.0+184+e34fea82.x86_64
nginx-all-modules-1.14.1-9.module_el8.0.0+184+e34fea82.noarch
nginx-mod-http-xslt-filter-1.14.1-9.module_el8.0.0+184+e34fea82.x86_64
nginx-mod-http-image-filter-1.14.1-9.module_el8.0.0+184+e34fea82.x86_64

[root@node3 ~]# rpm -qa | grep httpd
httpd-filesystem-2.4.37-40.module_el8.5.0+852+0aafc63b.noarch
centos-logos-httpd-85.8-1.el8.noarch
httpd-2.4.37-40.module_el8.5.0+852+0aafc63b.x86_64
httpd-tools-2.4.37-40.module_el8.5.0+852+0aafc63b.x86_64


[root@node1 ~]# ss -antl
State  Recv-Q Send-Q Local Address:Port   Peer Address:Port Process                                                     
LISTEN 0      128          0.0.0.0:22          0.0.0.0:*                                                                
LISTEN 0      128                *:80                *:*                                                                
LISTEN 0      128             [::]:22             [::]:*  

[root@node2 ~]# ss -antl
State  Recv-Q Send-Q Local Address:Port   Peer Address:Port Process                                                     
LISTEN 0      128          0.0.0.0:80          0.0.0.0:*                                                                
LISTEN 0      128          0.0.0.0:22          0.0.0.0:*                                                                
LISTEN 0      128             [::]:80             [::]:*                                                                
LISTEN 0      128             [::]:22             [::]:*   

[root@node3 ~]# ss -antl
State  Recv-Q Send-Q Local Address:Port   Peer Address:Port Process                                                     
LISTEN 0      128          0.0.0.0:22          0.0.0.0:*                                                                
LISTEN 0      128                *:80                *:*                                                                
LISTEN 0      128             [::]:22             [::]:*

注意：

若top file里面的目标是用 * 表示的，要注意的是，top file里面的 * 表示的是所有要执行状态的目标，而 salt ‘*’ state.highstate 里面的 * 表示通知所有机器干活，而是否要干活则是由top file来指定的

3.2 高级状态highstate的使用

管理SaltStack时一般最常用的管理操作就是执行高级状态

[root@master ~]# salt '*' state.highstate   //生产环境禁止这样使用salt命令

注意：
上面让所有人执行高级状态，但实际工作当中，一般不会这么用，工作当中一般都是通知某台或某些台目标主机来执行高级状态，具体是否执行则是由top file来决定的。

若在执行高级状态时加上参数test=True，则它会告诉我们它将会做什么，但是它不会真的去执行这个操作

// 停掉node3主机上的httpd服务
[root@node3 ~]# systemctl stop httpd
[root@node3 ~]# systemctl status httpd
● httpd.service - The Apache HTTP Server
   Loaded: loaded (/usr/lib/systemd/system/httpd.service; e>
   Active: inactive (dead) since Tue 2021-11-02 16:37:07 CS>
     Docs: man:httpd.service(8)
  Process: 561432 ExecStart=/usr/sbin/httpd $OPTIONS -DFORE>
 Main PID: 561432 (code=exited, status=0/SUCCESS)
   Status: "Running, listening on: port 80"

Nov 02 16:27:47 node3 systemd[1]: Starting The Apache HTTP >
Nov 02 16:28:07 node3 httpd[561432]: AH00558: httpd: Could >
Nov 02 16:28:07 node3 systemd[1]: Started The Apache HTTP S>
Nov 02 16:28:17 node3 httpd[561432]: Server configured, lis>
Nov 02 16:37:06 node3 systemd[1]: Stopping The Apache HTTP >
Nov 02 16:37:07 node3 systemd[1]: httpd.service: Succeeded.
Nov 02 16:37:07 node3 systemd[1]: Stopped The Apache HTTP S>

// 在master上执行高级状态的测试
[root@master base]# salt 'node3' test.ping
node3:
    True

[root@master base]# salt 'node3' state.highstate test=True
node3:
----------
          ID: apache-install
    Function: pkg.installed
        Name: httpd
      Result: True
     Comment: All specified packages are already installed
     Started: 16:41:47.095885
    Duration: 821.71 ms
     Changes:   
----------
          ID: apache-service
    Function: service.running
        Name: httpd
      Result: None
     Comment: Service httpd is set to start
     Started: 16:41:47.919808
    Duration: 47.748 ms
     Changes:   

Summary for node3
------------
Succeeded: 2 (unchanged=1)
Failed:    0
------------
Total states run:     2
Total run time: 869.458 ms




// 在node3上查看httpd是否启动
[root@node3 ~]# systemctl status httpd
● httpd.service - The Apache HTTP Server
   Loaded: loaded (/usr/lib/systemd/system/httpd.service; e>
   Active: inactive (dead) since Tue 2021-11-02 16:41:33 CS>
     Docs: man:httpd.service(8)
  Process: 580967 ExecStart=/usr/sbin/httpd $OPTIONS -DFORE>
 Main PID: 580967 (code=exited, status=0/SUCCESS)
   Status: "Running, listening on: port 80"

Nov 02 16:37:59 node3 systemd[1]: Starting The Apache HTTP >
Nov 02 16:38:19 node3 httpd[580967]: AH00558: httpd: Could >
Nov 02 16:38:19 node3 systemd[1]: Started The Apache HTTP S>
Nov 02 16:38:30 node3 httpd[580967]: Server configured, lis>
Nov 02 16:41:32 node3 systemd[1]: Stopping The Apache HTTP >
Nov 02 16:41:33 node3 systemd[1]: httpd.service: Succeeded.
Nov 02 16:41:33 node3 systemd[1]: Stopped The Apache HTTP S>


// 由此可见高级状态并没有执行，因为httpd并没有启动