SaltStack之数据系统

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的功能：

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

模板中进行目标匹配请看

信息查询实例：

//列出所有grains的key和value
[root@vm1 ~]# salt 'vm1' grains.items
vm1:
    ----------
    SSDs:
    biosreleasedate:
        07/29/2019
    biosversion:
        6.00
    cpu_flags:         //cpu相关的属性
        - fpu
        - vme
        - de
        - pse
        - tsc
        - msr
        - pae
        - mce
        - cx8
        - apic
        - sep
        - mtrr
        - pge
        - mca
        - cmov
        - pat
        - pse36
        - clflush
        - mmx
        - fxsr
        - sse
        - sse2
        - ss
        - syscall
        - nx
        - pdpe1gb
        - rdtscp
        - lm
        - constant_tsc
        - arch_perfmon
        - nopl
        - xtopology
        - tsc_reliable
        - nonstop_tsc
        - eagerfpu
        - 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
        - fsgsbase
        - tsc_adjust
        - bmi1
        - avx2
        - smep
        - bmi2
        - invpcid
        - mpx
        - rdseed
        - adx
        - smap
        - clflushopt
        - xsaveopt
        - xsavec
        - ibpb
        - ibrs
        - stibp
        - arat
        - spec_ctrl
        - intel_stibp
        - arch_capabilities
    cpu_model:
        Intel(R) Core(TM) i3-9100F CPU @ 3.60GHz
    cpuarch:
        x86_64
    cwd:
        /
    disks:
        - sda
        - sr0
        - dm-0
        - dm-1
    dns:
        ----------
        domain:
        ip4_nameservers:
            - 114.114.114.114
        ip6_nameservers:
        nameservers:
            - 114.114.114.114
        options:
        search:
        sortlist:
    domain:
        localdomain
    fqdn:
        localhost.localdomain
    fqdn_ip4:
        - 127.0.0.1
    fqdn_ip6:
        - ::1
    fqdns:
    gid:
        0
    gpus:
        |_
          ----------
          model:
              SVGA II Adapter
          vendor:
              vmware
    groupname:
        root
    host:
        localhost
    hwaddr_interfaces:
        ----------
        ens33:
            00:0c:29:e9:2e:d1
        lo:
            00:00:00:00:00:00
    id:
        vm1
    init:
        systemd
    ip4_gw:
        192.168.30.2
    ip4_interfaces:
        ----------
        ens33:
            - 192.168.30.100
        lo:
            - 127.0.0.1
    ip6_gw:
        False
    ip6_interfaces:
        ----------
        ens33:
            - fe80::20c:29ff:fee9:2ed1
        lo:
            - ::1
    ip_gw:
        True
    ip_interfaces:
        ----------
        ens33:
            - 192.168.30.100
            - fe80::20c:29ff:fee9:2ed1
        lo:
            - 127.0.0.1
            - ::1
    ipv4:
        - 127.0.0.1
        - 192.168.30.100
    ipv6:
        - ::1
        - fe80::20c:29ff:fee9:2ed1
    kernel:
        Linux
    kernelrelease:
        3.10.0-862.el7.x86_64
    kernelversion:
        #1 SMP Fri Apr 20 16:44:24 UTC 2018
    locale_info:
        ----------
        defaultencoding:
            UTF-8
        defaultlanguage:
            en_US
        detectedencoding:
            UTF-8
        timezone:
            unknown
    localhost:
        localhost.localdomain
    lsb_distrib_codename:
        CentOS Linux 7 (Core)
    lsb_distrib_id:
        CentOS Linux
    machine_id:
        133563fc63ee4915b7789dc9c16b9989
    manufacturer:
        VMware, Inc.
    master:
        192.168.30.100
    mdadm:
    mem_total:
        1821
    nodename:
        localhost.localdomain
    num_cpus:
        1
    num_gpus:
        1
    os:
        CentOS
    os_family:
        RedHat
    osarch:
        x86_64
    oscodename:
        CentOS Linux 7 (Core)
    osfinger:
        CentOS Linux-7
    osfullname:
        CentOS Linux
    osmajorrelease:
        7
    osrelease:
        7.5.1804
    osrelease_info:
        - 7
        - 5
        - 1804
    path:
        /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
    pid:
        1587
    productname:
        VMware Virtual Platform
    ps:
        ps -efHww
    pythonexecutable:
        /usr/bin/python
    pythonpath:
        - /usr/bin
        - /usr/lib64/python27.zip
        - /usr/lib64/python2.7
        - /usr/lib64/python2.7/plat-linux2
        - /usr/lib64/python2.7/lib-tk
        - /usr/lib64/python2.7/lib-old
        - /usr/lib64/python2.7/lib-dynload
        - /usr/lib64/python2.7/site-packages
        - /usr/lib/python2.7/site-packages
    pythonversion:
        - 2
        - 7
        - 5
        - final
        - 0
    saltpath:
        /usr/lib/python2.7/site-packages/salt
    saltversion:
        3000.3
    saltversioninfo:
        - 3000
        - 3
    selinux:
        ----------
        enabled:
            False
        enforced:
            Disabled
    serialnumber:
        VMware-56 4d c4 ee 08 78 5f ce-99 23 cf ef 41 e9 2e d1
    server_id:
        147626591
    shell:
        /bin/sh
    swap_total:
        1023
    systemd:
        ----------
        features:
            +PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD +IDN
        version:
            219
    uid:
        0
    username:
        root
    uuid:
        eec44d56-7808-ce5f-9923-cfef41e92ed1
    virtual:
        VMware
    zfs_feature_flags:
        False
    zfs_support:
        False
    zmqversion:
        4.1.4

//只查询所有的grains的key

[root@vm1 ~]# salt 'vm1' grains.ls
vm1:
    - SSDs
    - biosreleasedate
    - biosversion
    - cpu_flags
    - cpu_model
    - cpuarch
    - cwd
    - disks
    - dns
    - domain
    - 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
    - kernelrelease
    - kernelversion
    - locale_info
    - localhost
    - lsb_distrib_codename
    - lsb_distrib_id
    - 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
    - swap_total
    - systemd
    - uid
    - username
    - uuid
    - virtual
    - zfs_feature_flags
    - zfs_support
    - zmqversion



//查询某个key的值，比如想获取ip地址

[root@vm1 ~]# salt 'vm1' grains.get fqdn_ip4
vm1:
    - 127.0.0.1

[root@vm1 ~]# salt 'vm2' grains.get ip4_interfaces
vm2:
    ----------
    ens33:
        - 192.168.30.128
        - 192.168.30.130
    lo:
        - 127.0.0.1

[root@vm1 ~]# salt '*' grains.get ip4_interfaces:ens33
vm2:
    - 192.168.30.128
    - 192.168.30.130
vm1:
    - 192.168.30.100

目标匹配实例

用Grains来匹配minion：

//在所有centos系统中执行命令
[root@vm1 ~]# salt -G 'os:CentoS' cmd.run 'uptime'
vm1:
     21:52:38 up 41 min,  2 users,  load average: 0.09, 0.25, 0.24
vm2:
     21:52:38 up 41 min,  1 user,  load average: 0.00, 0.01, 0.05

在top file里面使用Grains：

[root@vm1 ~]# vim /srv/salt/base/top.sls

base:
  'os:CentoS':
    - match: grain
    - web.apache.apache


[root@vm1 ~]# salt '*' state.highstate
vm2:
----------
          ID: apache-install
    Function: pkg.installed
        Name: httpd
      Result: True
     Comment: All specified packages are already installed
     Started: 21:56:33.174026
    Duration: 651.464 ms
     Changes:   
----------
          ID: apache-services
    Function: service.running
        Name: httpd
      Result: True
     Comment: The service httpd is already running
     Started: 21:56:33.826485
    Duration: 61.248 ms
     Changes:   

Summary for vm2
------------
Succeeded: 2
Failed:    0
------------
Total states run:     2
Total run time: 712.712 ms
vm1:
----------
          ID: apache-install
    Function: pkg.installed
        Name: httpd
      Result: True
     Comment: All specified packages are already installed
     Started: 21:56:33.212518
    Duration: 701.662 ms
     Changes:   
----------
          ID: apache-services
    Function: service.running
        Name: httpd
      Result: True
     Comment: The service httpd is already running
     Started: 21:56:33.915166
    Duration: 70.135 ms
     Changes:   

Summary for vm1
------------
Succeeded: 2
Failed:    0
------------
Total states run:     2
Total run time: 771.797 ms

自定义Grains的两种方法：

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

// minion配置
[root@vm2 ~]# vim /etc/salt/minion

grains:
   roles:
     - webserver

#  deployment: datacenter4

[root@vm1 ~]# salt -G 'os:CentoS' grains.get roles
vm2:
    - webserver
vm1:

//在/etc/salt下生成一个grains文件

[root@vm1 ~]# vim /etc/salt/grains
[root@vm1 ~]# cat /etc/salt/grains
role: webserver
[root@vm1 ~]# salt-cp '*' /etc/salt/grains /etc/salt/grains
vm1:
    ----------
    /etc/salt/grains:
        True
vm2:
    ----------
    /etc/salt/grains:
        True
[root@vm1 ~]# salt '*' saltutil.sync_grains
vm1:
vm2:
[root@vm1 ~]# salt '*' grains.get role
vm2:
    webserver
vm1:
    webserver

2.2 SaltStack组件之Pillar

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

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

[root@vm1 ~]# vim /etc/salt/master
# highstate format, and is generally just key/value pairs.
------
#pillar_roots:
#  base:
#    - /srv/pillar
#

-----

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

Pillar的特点：

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

//查看pillar的信息

[root@vm1 ~]# salt '*' pillar.items
vm2:
    ----------
vm1:
    ----------

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

[root@vm1 ~]# vim /etc/salt/master

# the pillar called "master". This is used to set simple configurations in the
# master config file that can then be used on minions.
pillar_opts: True

# The pillar_safe_render_error option prevents the master from passing pillar
# render errors to the minion. This is set on by default because the error co

//重启master并查看pillar的信息

[root@vm1 ~]# systemctl restart salt-master
 [root@vm1 ~]# salt '*' pillar.items      
      
        thorium_roots:
            ----------
            base:
                - /srv/thorium
        thorium_top:
            top.sls
        thoriumenv:
            None
        timeout:
            5
        token_dir:
            /var/cache/salt/master/tokens
        token_expire:
            43200
        token_expire_user_override:
            False
        top_file_merging_strategy:
            merge
        transport:
            zeromq
        unique_jid:
            False
        user:
            root
        utils_dirs:
            - /var/cache/salt/master/extmods/utils
        verify_env:
            True
        winrepo_branch:
            master
        winrepo_cachefile:
            winrepo.p
        winrepo_dir:
            /srv/salt/win/repo
        winrepo_dir_ng:
            /srv/salt/win/repo-ng
        winrepo_insecure_auth:
            False
        winrepo_passphrase:
        winrepo_password:
        winrepo_privkey:
        winrepo_pubkey:
        winrepo_refspecs:
            - +refs/heads/*:refs/remotes/origin/*
            - +refs/tags/*:refs/tags/*
        winrepo_remotes:
            - https://github.com/saltstack/salt-winrepo.git
        winrepo_remotes_ng:
            - https://github.com/saltstack/salt-winrepo-ng.git
        winrepo_ssl_verify:
            True
        winrepo_user:
        worker_threads:
            5
        zmq_backlog:
            1000
        zmq_filtering:
            False
        zmq_monitor:
            False
vm1:
    ----------
    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:
            /var/cache/salt/master
        clean_dynamic_modules:
            True
        cli_summary:
            False
        client_acl_verify:
            True
        cluster_mode:
            False
        con_cache:
            False
        conf_file:
            /etc/salt/master
        config_dir:
            /etc/salt
        cython_enable:
            False
        daemon:
            False
        decrypt_pillar:
        decrypt_pillar_default:
            gpg
        decrypt_pillar_delimiter:
            :
        decrypt_pillar_renderers:
            - gpg
        default_include:
            master.d/*.conf
        default_top:
            base
        discovery:
            False
        django_auth_path:
        django_auth_settings:
        drop_messages_signature_fail:
            False
        dummy_pub:
            False
        eauth_acl_module:
        eauth_tokens:
            localfs
        enable_gpu_grains:
            False
        enable_ssh_minions:
            False
        enforce_mine_cache:
            False
        engines:
        env_order:
        event_match_type:
            startswith
        event_return:
        event_return_blacklist:
        event_return_queue:
            0
        event_return_whitelist:
        ext_job_cache:
        ext_pillar:
        extension_modules:
 

pillar自定义数据：

在master的配置文件里找pillar_roots可以看到其存放pillar的位置

[root@vm1 ~]# vim /etc/salt/master

# highstate format, and is generally just key/value pairs.
pillar_roots:
  base:
    - /srv/pillar/base
#
#ext_pillar:

[root@vm1 ~]# mkdir -p /srv/pillar/base
[root@vm1 ~]# systemctl restart salt-master
[root@vm1 ~]# vim /srv/pillar/base/apache.sls
[root@vm1 ~]# cat /srv/pillar/base/apache.sls
{% if grains['os'] == 'CentOS' %}
apache: httpd
{% elif grains['os'] == 'Debian' %}
apache: apache2
{% endif %}

//定义top file入口文件
[root@vm1 ~]# cat /srv/pillar/base/top.sls
base:        //指定环境
  'vm1':         //指定目标 
    - apache       //引用apache.sls或apache/init.sls

//这个top.sls文件的意思表示的是vm1这台主机的base环境能够访问到apache这个pillar
[root@vm1 ~]# vim /etc/salt/master
# master config file that can then be used on minions.
#pillar_opts: True

[root@vm1 ~]# systemctl restart salt-master
[root@vm1 ~]# salt '*' pillar.items
vm2:
    ----------
vm1:
    ----------
    apache:
        httpd

//在salt下修改apache的状态文件，引用pillar的数据

[root@vm1 ~]# vim /srv/salt/base/web/apache/apache.sls

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

apache-services:
  service.running:
    - name: {{ pillar['apache'] }}
    - enable: True

//执行高级状态文件

[root@vm1 ~]# salt 'vm1' state.highstate
vm1:
----------
          ID: apache-install
    Function: pkg.installed
        Name: httpd
      Result: True
     Comment: All specified packages are already installed
     Started: 22:56:30.139663
    Duration: 635.878 ms
     Changes:   
----------
          ID: apache-services
    Function: service.running
        Name: httpd
      Result: True
     Comment: The service httpd is already running
     Started: 22:56:30.776506
    Duration: 56.911 ms
     Changes:   

Summary for vm1
------------
Succeeded: 2
Failed:    0
------------
Total states run:     2
Total run time: 692.789 ms

2.3 Grains与Pillar的区别

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