satlstack 数据系统组件

satlstack 数据系统组件

1.SaltStack数据系统

SaltStack有两大数据系统，分别是：

• Grains
• Pillar

2. SaltStack数据系统组件

2.1 SaltStack组件之Grains

Grains是SaltStack的一个组件，其存放着minion启动时收集到的信息。

Grains是SaltStack组件中非常重要的组件之一，因为我们在做配置部署的过程中会经常使用它，Grains是SaltStack记录minion的一些静态信息的组件。可简单理解为Grains记录着每台minion的一些常用属性，比如CPU、内存、磁盘、网络信息等。我们可以通过grains.items查看某台minion的所有Grains信息。

Grains的功能：

• 收集资产信息

Grains应用场景：

• 信息查询
• 在命令行下进行目标匹配
• 在top file中进行目标匹配
• 在模板中进行目标匹配

模板中进行目标匹配请看：https://docs.saltstack.com/en/latest/topics/pillar/

信息查询实例：

//列出所有的key和value
[root@master base]# salt '192.168.200.147' grains.items
192.168.200.147:
    ----------
    biosreleasedate:
        07/22/2020
    biosversion:
        6.00
    cpu_flags:
        - fpu
        - vme
        - de
        - pse
        - tsc
        - msr
        - pae
        - mce
        - cx8
        - apic
        - sep
        - mtrr
        - pge
        - mca
        - cmov
        - pat
        - pse36
        - clflush
        - mmx
        - fxsr
        - sse
        - sse2
        - ss
        - ht
        - syscall
        - nx
        - pdpe1gb
        - rdtscp
        - lm
        - constant_tsc
        - arch_perfmon
        - nopl
        - xtopology
        - tsc_reliable
        - nonstop_tsc
        - cpuid
        - pni
        - pclmulqdq
        - ssse3
        - fma
        - cx16
        - pcid
        - sse4_1
        - sse4_2
        - x2apic
        - movbe
        - popcnt
        - tsc_deadline_timer
        - aes
        - xsave
        - avx
        - f16c
        - rdrand
        - hypervisor
        - lahf_lm
        - abm
        - 3dnowprefetch
        - cpuid_fault
        - invpcid_single
        - pti
        - ssbd
        - ibrs
        - ibpb
        - stibp
        - fsgsbase
        - tsc_adjust
        - bmi1
        - avx2
        - smep
        - bmi2
        - invpcid
        - rdseed
        - adx
        - smap
        - clflushopt
        - xsaveopt
        - xsavec
        - xgetbv1
        - xsaves
        - arat
        - md_clear
        - flush_l1d
        - arch_capabilities
    cpu_model:
        Intel(R) Core(TM) i5-9300H CPU @ 2.40GHz
    cpuarch:
        x86_64
    cwd:
        /
    disks:
        - sr0
    dns:
        ----------
        domain:
        ip4_nameservers:
            - 192.168.200.2
        ip6_nameservers:
        nameservers:
            - 192.168.200.2
        options:
        search:
            - localdomain
        sortlist:
    domain:
    efi:
        False
    efi-secure-boot:
        False
    fqdn:
        node1
    fqdn_ip4:
        - 192.168.200.147
    fqdn_ip6:
        - fe80::1968:9343:fc27:ceca
        - fe80::4f7c:18b3:7c7c:c8bf
    fqdns:
        - node1
    gid:
        0
    gpus:
        |_
          ----------
          model:
              SVGA II Adapter
          vendor:
              vmware
    groupname:
        root
    host:
        node1
    hwaddr_interfaces:
        ----------
        ens160:
            00:0c:29:da:ff:45
        lo:
            00:00:00:00:00:00
    id:
        192.168.200.147
    init:
        systemd
    ip4_gw:
        192.168.200.2
    ip4_interfaces:
        ----------
        ens160:
            - 192.168.200.147
        lo:
            - 127.0.0.1
    ip6_gw:
        False
    ip6_interfaces:
        ----------
        ens160:
            - fe80::4f7c:18b3:7c7c:c8bf
            - fe80::1968:9343:fc27:ceca
        lo:
            - ::1
    ip_gw:
        True
    ip_interfaces:
        ----------
        ens160:
            - 192.168.200.147
            - fe80::4f7c:18b3:7c7c:c8bf
            - fe80::1968:9343:fc27:ceca
        lo:
            - 127.0.0.1
            - ::1
    ipv4:
        - 127.0.0.1
        - 192.168.200.147
    ipv6:
        - ::1
        - fe80::1968:9343:fc27:ceca
        - fe80::4f7c:18b3:7c7c:c8bf
    kernel:
        Linux
    kernelparams:
        |_
          - BOOT_IMAGE
          - (hd0,msdos1)/vmlinuz-4.18.0-193.el8.x86_64
        |_
          - root
          - /dev/mapper/rhel-root
        |_
          - ro
          - None
        |_
          - crashkernel
          - auto
        |_
          - resume
          - /dev/mapper/rhel-swap
        |_
          - rd.lvm.lv
          - rhel/root
        |_
          - rd.lvm.lv
          - rhel/swap
        |_
          - rhgb
          - None
        |_
          - quiet
          - None
    kernelrelease:
        4.18.0-193.el8.x86_64
    kernelversion:
        #1 SMP Fri Mar 27 14:35:58 UTC 2020
    locale_info:
        ----------
        defaultencoding:
            UTF-8
        defaultlanguage:
            zh_CN
        detectedencoding:
            UTF-8
        timezone:
            EDT
    localhost:
        node1
    lsb_distrib_codename:
        Red Hat Enterprise Linux 8.2 (Ootpa)
    lsb_distrib_id:
        Red Hat Enterprise Linux
    lsb_distrib_release:
        8.2
    lvm:
        ----------
        rhel:
            - root
            - swap
    machine_id:
        a48a7d7c14d9496ba7c8db879eb7319b
    manufacturer:
        VMware, Inc.
    master:
        192.168.200.142
    mdadm:
    mem_total:
        1800
    nodename:
        minion
    num_cpus:
        4
    num_gpus:
        1
    os:
        RedHat
    os_family:
        RedHat
    osarch:
        x86_64
    oscodename:
        Ootpa
    osfinger:
        Red Hat Enterprise Linux-8
    osfullname:
        Red Hat Enterprise Linux
    osmajorrelease:
        8
    osrelease:
        8.2
    osrelease_info:
        - 8
        - 2
    path:
        /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
    pid:
        1596
    productname:
        VMware Virtual Platform
    ps:
        ps -efHww
    pythonexecutable:
        /usr/bin/python3.6
    pythonpath:
        - /usr/bin
        - /usr/lib64/python36.zip
        - /usr/lib64/python3.6
        - /usr/lib64/python3.6/lib-dynload
        - /usr/lib64/python3.6/site-packages
        - /usr/lib/python3.6/site-packages
    pythonversion:
        - 3
        - 6
        - 8
        - final
        - 0
    saltpath:
        /usr/lib/python3.6/site-packages/salt
    saltversion:
        3004
    saltversioninfo:
        - 3004
    selinux:
        ----------
        enabled:
            False
        enforced:
            Disabled
    serialnumber:
        VMware-56 4d a7 af e1 bc 72 91-12 b1 97 9b d1 da ff 45
    server_id:
        542807568
    shell:
        /bin/sh
    ssds:
        - nvme0n1
    swap_total:
        5119
    systemd:
        ----------
        features:
            +PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=legacy
        version:
            239
    systempath:
        - /usr/local/sbin
        - /usr/local/bin
        - /usr/sbin
        - /usr/bin
    transactional:
        False
    uid:
        0
    username:
        root
    uuid:
        afa74d56-bce1-9172-12b1-979bd1daff45
    virtual:
        VMware
    zfs_feature_flags:
        False
    zfs_support:
        False
    zmqversion:
        4.3.4

//只查询所有的grains的key
[root@master base]# salt '192.168.200.147' grains.ls
192.168.200.147:
    - biosreleasedate
    - biosversion
    - cpu_flags
    - cpu_model
    - cpuarch
    - cwd
    - disks
    - dns
    - domain
    - efi
    - efi-secure-boot
    - fqdn
    - fqdn_ip4
    - fqdn_ip6
    - fqdns
    - gid
    - gpus
    - groupname
    - host
    - hwaddr_interfaces
    - id
    - init
    - ip4_gw
    - ip4_interfaces
    - ip6_gw
    - ip6_interfaces
    - ip_gw
    - ip_interfaces
    - ipv4
    - ipv6
    - kernel
    - kernelparams
    - kernelrelease
    - kernelversion
    - locale_info
    - localhost
    - lsb_distrib_codename
    - lsb_distrib_id
    - lsb_distrib_release
    - lvm
    - machine_id
    - manufacturer
    - master
    - mdadm
    - mem_total
    - nodename
    - num_cpus
    - num_gpus
    - os
    - os_family
    - osarch
    - oscodename
    - osfinger
    - osfullname
    - osmajorrelease
    - osrelease
    - osrelease_info
    - path
    - pid
    - productname
    - ps
    - pythonexecutable
    - pythonpath
    - pythonversion
    - saltpath
    - saltversion
    - saltversioninfo
    - selinux
    - serialnumber
    - server_id
    - shell
    - ssds
    - swap_total
    - systemd
    - systempath
    - transactional
    - uid
    - username
    - uuid
    - virtual
    - zfs_feature_flags
    - zfs_support
    - zmqversion

//查询某个key的值，比如想获取ip地址
[root@master base]# salt '192.168.200.147' grains.get hostnae
192.168.200.147:
[root@master base]# salt '192.168.200.147' grains.get ip4_interfaces
192.168.200.147:
    ----------
    ens160:
        - 192.168.200.147
    lo:
        - 127.0.0.1
[root@master base]# salt '192.168.200.147' grains.get ip4_interfaces:ens160
192.168.200.147:
    - 192.168.200.147

目标匹配实例：
用Grains来匹配minion：

//在所有RedHat系统中执行命令
[root@master base]# cat top.sls
base: 
  '192.168.200.147': 
    - web.nginx.install
  'os:RedHat':
    - match: grain
    - database.mariadb.install 
[root@master base]# salt -G 'os:RedHat' state.highstate

自定义Grains的两种方法：

• minion配置文件，在配置文件中搜索grains
• 在/etc/salt下生成一个grains文件，在此文件中定义(推荐方式)

[root@node1 ~]# vim /etc/salt/minion
.....
grains:
  重生之:
    - 我是熊可他爹
.......
[root@node1 ~]# systemctl restart salt-minion.service

[root@master base]# salt '192.168.200.147' grains.items
.......
 transactional:
        False
    uid:
        0
    username:
        root
    uuid:
        afa74d56-bce1-9172-12b1-979bd1daff45
    virtual:
        VMware
    zfs_feature_flags:
        False
    zfs_support:
        False
    zmqversion:
        4.3.4
    重生之:
        - 我是熊可他爹

//不重启的定义Grains
[root@node1 ~]# cat /etc/salt/grains
重生之: 徐猛是道格耳

[root@master base]# salt '192.168.200.147' saltutil.sync_grains
[root@master base]# salt '192.168.200.147' grains.items
.....
uuid:
        afa74d56-bce1-9172-12b1-979bd1daff45
    virtual:
        VMware
    zfs_feature_flags:
        False
    zfs_support:
        False
    zmqversion:
        4.3.4
    重生之:
        徐猛是道格耳

2.2 SaltStack组件之Pillar

Pillar也是SaltStack组件中非常重要的组件之一，是数据管理中心，经常配置states在大规模的配置管理工作中使用它。Pillar在SaltStack中主要的作用就是存储和定义配置管理中需要的一些数据，比如软件版本号、用户名密码等信息，它的定义存储格式与Grains类似，都是YAML格式。

在Master配置文件中有一段Pillar settings选项专门定义Pillar相关的一些参数：

//配置
[root@master base]# vim /etc/salt/master
pillar_roots:
  base:
    - /srv/pillar/base    
[root@master base]# vim /etc/salt/master
[root@master base]# mkdir /srv/piller
[root@master base]# systemctl restart salt-master.service

默认Base环境下Pillar的工作目录在/srv/pillar目录下。若你想定义多个环境不同的Pillar工作目录，只需要修改此处配置文件即可。

Pillar的特点：

• 可以给指定的minion定义它需要的数据
• 只有指定的人才能看到定义的数据
• 在master配置文件里设置

[root@master base]# salt '*' pillar.items
master:
    ----------
192.168.200.145:
    ----------
192.168.200.146:
    ----------
192.168.200.147:
    ----------

默认pillar是没有任何信息的，如果想查看信息，需要在 master 配置文件上把 pillar_opts的注释取消，并将其值设为 True

[root@master base]# vim /etc/salt/master
# master config file that can then be used on minions.
pillar_opts: True
....

//重启master并查看pillar的信息
[root@master base]# salt '*' pillar.items
192.168.200.147:
    ----------
    master:
        ----------
        __cli:
            salt-master
        __role:
            master
        allow_minion_key_revoke:
            True
        archive_jobs:
            False
        auth_events:
            True
        auth_mode:
            1
        auto_accept:
            False
        azurefs_update_interval:
            60
        cache:
            localfs
        cache_sreqs:
            True
        cachedir:
.......

pillar自定义数据：
在master的配置文件里找pillar_roots可以看到其存放pillar的位置

[root@master piller]# cd base/
[root@master base]# ls
nginx.sls  top.sls
[root@master base]# cat nginx.sls 
{% if grains['os'] == 'RedHat' %}
webserver: httpd
{% elif grains['os'] == 'CentOS' %}
webserver: nginx
{% endif %}

//定义top file入口文件
[root@master base]# cat top.sls 
base: 
  '192.168.200.147': 
    - nginx

[root@master base]# salt '*' pillar.items
192.168.200.147:
    ----------
    webserver:
        httpd
master:
    ----------
192.168.200.145:
    ----------
192.168.200.146:
    ----------

[root@master base]# vim /srv/salt/base/web/nginx/install.sls 
nginx-install: 
  pkg.installed: 
    - name: {{ pillar['webserver'] }}

nginx-service: 
  service.running: 
    - name: {{ pillar['webserver'] }}
    - enable: true

[root@master base]# salt '*' state.highstate
192.168.200.145:
----------
          ID: mariadb-install
    Function: pkg.installed
        Name: mariadb-server
      Result: True
     Comment: All specified packages are already installed
     Started: 16:10:55.574038
    Duration: 1112.796 ms
     Changes:   
----------
          ID: mariadb-service
    Function: service.running
        Name: mariadb
      Result: True
     Comment: The service mariadb is already running
     Started: 16:10:56.690152
    Duration: 70.354 ms
     Changes:   

Summary for 192.168.200.145
------------
Succeeded: 2
Failed:    0
------------
Total states run:     2
Total run time:   1.183 s
master:
----------
          ID: mariadb-install
    Function: pkg.installed
        Name: mariadb-server
      Result: True
     Comment: All specified packages are already installed
     Started: 04:10:57.056956
    Duration: 994.459 ms
     Changes:   
----------
          ID: mariadb-service
    Function: service.running
        Name: mariadb
      Result: True
     Comment: The service mariadb is already running
     Started: 04:10:58.053975
    Duration: 72.909 ms
     Changes:   

Summary for master
------------
Succeeded: 2
Failed:    0
------------
Total states run:     2
Total run time:   1.067 s
192.168.200.146:
----------
          ID: mariadb-install
    Function: pkg.installed
        Name: mariadb-server
      Result: True
     Comment: All specified packages are already installed
     Started: 16:10:56.701788
    Duration: 1407.126 ms
     Changes:   
----------
          ID: mariadb-service
    Function: service.running
        Name: mariadb
      Result: True
     Comment: The service mariadb is already running
     Started: 16:10:58.112526
    Duration: 67.226 ms
     Changes:   
...........

2.3 Grains与Pillar的区别

	存储位置	类型	采集方式	应用场景
Grains	minion	静态	minion启动时采集 可通过刷新避免重启minion服务	1.信息查询 2.在命令行下进行目标匹配 3.在top file中进行目标匹配 4.在模板中进行目标匹配
Pillar	master	动态	指定，实时生效	1.目标匹配 2.敏感数据配置