SaltStack数据系统
SaltStack有两大数据系统:
- Grains
- Pillar
SaltStack数据系统组件
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/
- 信息查询示例:
[root@master ~]# salt 'node1' grains.items
node1:
----------
biosreleasedate:
07/29/2019
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
- 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
- invpcid_single
- ssbd
- ibrs
- ibpb
- stibp
- ibrs_enhanced
- fsgsbase
- tsc_adjust
- bmi1
- avx2
- smep
- bmi2
- invpcid
- mpx
- rdseed
- adx
- smap
- clflushopt
- xsaveopt
- xsavec
- xsaves
- arat
- pku
- ospke
- md_clear
- flush_l1d
- arch_capabilities
cpu_model:
Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz
cpuarch:
x86_64
cwd:
/
disks:
- sr0
- sda
dns:
----------
domain:
ip4_nameservers:
- 192.168.218.2
ip6_nameservers:
nameservers:
- 192.168.218.2
options:
search:
- localdomain
sortlist:
domain:
efi:
False
efi-secure-boot:
False
fqdn:
node1
fqdn_ip4:
- 192.168.218.133
fqdn_ip6:
- fe80::6faa:c998:4390:2ee4
fqdns:
- 192.168.218.133
- node1
gid:
0
gpus:
|_
----------
model:
SVGA II Adapter
vendor:
vmware
groupname:
root
host:
node1
hwaddr_interfaces:
----------
ens160:
00:0c:29:03:ca:ed
lo:
00:00:00:00:00:00
id:
node1
init:
systemd
ip4_gw:
192.168.218.2
ip4_interfaces:
----------
ens160:
- 192.168.218.133
lo:
- 127.0.0.1
ip6_gw:
False
ip6_interfaces:
----------
ens160:
- fe80::6faa:c998:4390:2ee4
lo:
- ::1
ip_gw:
True
ip_interfaces:
----------
ens160:
- 192.168.218.133
- fe80::6faa:c998:4390:2ee4
lo:
- 127.0.0.1
- ::1
ipv4:
- 127.0.0.1
- 192.168.218.133
ipv6:
- ::1
- fe80::6faa:c998:4390:2ee4
kernel:
Linux
kernelparams:
|_
- BOOT_IMAGE
- (hd0,msdos1)/vmlinuz-4.18.0-257.el8.x86_64
|_
- root
- /dev/mapper/cs-root
|_
- ro
- None
|_
- resume
- /dev/mapper/cs-swap
|_
- rd.lvm.lv
- cs/root
|_
- rd.lvm.lv
- cs/swap
|_
- rhgb
- None
|_
- quiet
- None
kernelrelease:
4.18.0-257.el8.x86_64
kernelversion:
#1 SMP Thu Dec 3 22:16:23 UTC 2020
locale_info:
----------
defaultencoding:
UTF-8
defaultlanguage:
en_US
detectedencoding:
UTF-8
timezone:
CST
localhost:
node1
lsb_distrib_codename:
CentOS Stream 8
lsb_distrib_id:
CentOS Stream
lsb_distrib_release:
8
lvm:
----------
cs:
- root
- swap
machine_id:
6d0fd154891c4c2698acf2a352474a2f
manufacturer:
VMware, Inc.
master:
192.168.218.132
mdadm:
mem_total:
940
nodename:
node1
num_cpus:
1
num_gpus:
1
os:
CentOS Stream
os_family:
RedHat
osarch:
x86_64
oscodename:
CentOS Stream 8
osfinger:
CentOS Stream-8
osfullname:
CentOS Stream
osmajorrelease:
8
osrelease:
8
osrelease_info:
- 8
path:
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
pid:
1438
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 8c 4b 32 2c 0b e1-71 3e 10 7d 9d 03 ca ed
server_id:
1797241226
shell:
/bin/sh
ssds:
swap_total:
1023
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:
4b8c4d56-2c32-e10b-713e-107d9d03caed
virtual:
VMware
zfs_feature_flags:
False
zfs_support:
False
zmqversion:
4.3.4
//查询某个key的值,比如想获取ip地址
[root@master ~]# salt '*' grains.get fqdn_ip4
node2:
- 192.168.218.130
node1:
- 192.168.218.133
master:
- 127.0.0.1
[root@master ~]# salt '*' grains.get ip4_interfaces:ens160
master:
- 192.168.218.132
node1:
- 192.168.218.133
node2:
- 192.168.218.130
- 命令行下进行目标匹配
//在所有centos系统中执行命令
[root@master ~]# salt -G 'os:CentOS Stream' test.ping
node1:
True
master:
True
- 在top file里面使用Grains
[root@master base]# cat top.sls
base:
'os:CentOS Stream':
- match: grains //再top file中使用时必须加上此行
- web.apache.install
自定义Grains的两种方法:
- minion配置文件,在配置文件中搜索grains(在实际生产环境中,所有的minion主机的配置文件应当保持一致,方便与控制,不推荐此方式)
- 在/etc/salt下生成一个grains文件,在此文件中定义(推荐方式)
//需重启minion方式,自定义Grains
[root@node1 ~]# vim /etc/salt/grains
[root@node1 ~]# cat /etc/salt/grains
test: xiaobaixueyunwei
[root@node1 ~]# systemctl restart salt-minion
[root@master ~]# salt 'node1' grains.items //查看是否生效
......
test:
xiaobaixueyunwei //已生效
......
//不需要重启minion方式,自定义Grains
[root@node1 ~]# cat /etc/salt/grains
test: xiaobaixueyunwei
test2: nulixueyunwei
[root@master ~]# salt 'node1' saltutil.sync_grains //不需要重启被控机的minion,只需要再master上同步
node1: //同步完成
[root@master ~]# salt 'node1' grains.items //查看是否生效
......
test:
xiaobaixueyunwei
test2:
nulixueyunwei //已生效
......
SaltStack组件之Pillar
Pillar也是SaltStack组件中非常重要的组件之一,是数据管理中心,经常配置states在大规模的配置管理工作中使用它。Pillar在SaltStack中主要的作用就是存储和定义配置管理中需要的一些数据,比如软件版本号、用户名密码等信息,它的定义存储格式与Grains类似,都是YAML格式。
在Master配置文件中有一段Pillar settings选项专门定义Pillar相关的一些参数:
#pillar_roots:
# base:
# - /srv/pillar
默认Base环境下Pillar的工作目录在/srv/pillar目录下。若你想定义多个环境不同的Pillar工作目录,只需要修改此处配置文件即可。
[root@master ~]# vim /etc/salt/master
......
pillar_roots:
base:
- /srv/pillar/base
......
[root@master ~]# systemctl restart salt-master
[root@master ~]# mkdir /srv/pillar/base -p
[root@master ~]# tree /srv
/srv
├── pillar
│ └── base
└── salt
├── base
│ ├── top.sls
│ └── web
│ ├── apache
│ │ └── install.sls
│ └── nginx
│ └── install.sls
├── dev
├── prod
└── test
Pillar的特点:
- 可以给指定的minion定义它需要的数据
- 只有指定的人才能看到定义的数据
- 在master配置文件里设置
//查看pillar的信息
[root@master ~]# salt '*' pillar.items
master:
----------
node2:
----------
node1:
----------
默认pillar是没有任何信息的,如果想查看信息,需要在 master 配置文件上把 pillar_opts的注释取消,并将其值设为 True(但是打开以后显示的信息过于冗长,不方便查看,一般此选项选择默认不打开)。
pillar自定义数据
在master的配置文件里找pillar_roots可以看到其存放pillar的位置
[root@master ~]# tree /srv/pillar/
/srv/pillar/
└── base
[root@master base]# pwd
/srv/pillar/base
[root@master base]# vim web.sls
[root@master base]# cat web.sls
{% if grains['os'] == 'CentOs' %}
package: httpd
{% elif grains['os'] == 'CentOS Stream' %}
package: nginx
{% endif %}
//定义top file入口文件
[root@master base]# vim top.sls
base:
'node*': //指定主机
- web //引用web.sls
//这个top.sls文件的意思表示的是node开头的所有主机的base环境能够访问到apache这个pillar
//在salt下修改apache的状态文件,引用pillar的数据,之前我们再/srv/salt/base/web下写过一个安装apache的状态文件,这里修改引用以下piilar数据
[root@master apache]# cat install.sls
web-install:
pkg.installed:
- name: {{ pillar['package'] }}
web-service:
service.running:
- name: {{ pillar['package'] }}
- enable: True
//执行高级状态文件
[root@master ~]# salt 'node*' state.highstate
node1:
----------
ID: nginx-install
Function: pkg.installed
Name: nginx
Result: True
Comment: All specified packages are already installed
Started: 10:39:43.653283
Duration: 893.9 ms
Changes:
----------
ID: nginx-service
Function: service.running
Name: nginx
Result: True
Comment: The service nginx is already running
Started: 10:39:44.549079
Duration: 43.952 ms
Changes:
Summary for node1
------------
Succeeded: 2
Failed: 0
------------
Total states run: 2
Total run time: 937.852 ms
node2:
----------
ID: web-install
Function: pkg.installed
Name: httpd
Result: True
Comment: All specified packages are already installed
Started: 10:39:45.799977
Duration: 1020.221 ms
Changes:
----------
ID: web-service
Function: service.running
Name: httpd
Result: True
Comment: The service httpd is already running
Started: 10:39:46.826099
Duration: 45.933 ms
Changes:
Summary for node2
------------
Succeeded: 2
Failed: 0
------------
Total states run: 2
Total run time: 1.066 s
Grains与Pillar的区别
存储位置 | 类型 | 采集方式 | ||
---|---|---|---|---|
Grains | minion | 静态 | minion启动时采集,可通过刷新避免重启minion服务 | 1.信息查询 2.在命令行下进行目标匹配 3.在top file中进行目标匹配 4.在模板中进行目标匹配 |
Pillar | master | 动态 | 指定,实时生效 | 1.目标匹配 2.敏感数据配置 |