一、Jinja模板简介
Jinja是一种基于python的模板引擎,在SLS文件里可以直接使用jinja模板来做一些操作。
通过jinja模板可以为不同服务器定义各自的变量。
两种分隔符: {% … %} 和 {{ … }},前者用于执行诸如 for 循环 或赋值的语句,后者把表达式的结果打印到模板上(引用)。
二、Jinja模板使用方式
使用控制结构包装条件
Jinja最基本的用法是使用控制结构包装条件:
[root@server1 salt]# vim test.sls
[root@server1 salt]# cat test.sls
/mnt/testfile:
file.append:
{% if grains['fqdn'] == 'server2' %}
- text: server2
{% elif grains['fqdn'] == 'server3' %}
- text: server3
{% endif %}
以上文件的内容表示在server2和server3创建文件/mnt/testfile,并将不同的内容添加进入文件。
推送:
[root@server1 salt]# salt '*' state.sls test
在server2查看:
[root@server2 ~]# cd /mnt/
[root@server2 mnt]# cat testfile
server2
在server3查看:
[root@server3 ~]# cd /mnt/
[root@server3 mnt]# cat testfile
server3
Jinja在普通文件的使用:
[root@server1 salt]# cd apache/
[root@server1 apache]# vim init.sls
[root@server1 apache]# cat init.sls
apache:
pkg.installed:
- pkgs:
- {{ pillar['webserver'] }}
service.running:
- name: httpd
- reload: true
- enable: true
- watch:
- file: /etc/httpd/conf/httpd.conf
/etc/httpd/conf/httpd.conf:
file.managed:
- source: salt://apache/httpd.conf
- template: jinja
- context:
bind: 172.25.63.3
port: 80
其中:
- template: jinja #启用jinja模板
- context:
bind: 172.25.63.3 #定义变量
port: 80
表示启用jinja模板和定义变量,接下来在配置文件中调用变量:
[root@server1 apache]# vim httpd.conf
[root@server1 apache]# cat -n httpd.conf | grep 42
42 Listen {{ bind }}:{{ port }}
推送
[root@server1 apache]# salt server3 state.sls apache
Jinja与grins和pillar结合在普通文件使用
主机数量增多后就不太合适,我们可以结合grains和pillar来进行调用:
[root@server1 apache]# vim init.sls
[root@server1 apache]# cat init.sls
apache:
pkg.installed:
- pkgs:
- {{ pillar['webserver'] }}
service.running:
- name: httpd
- reload: true
- enable: true
- watch:
- file: /etc/httpd/conf/httpd.conf
/etc/httpd/conf/httpd.conf:
file.managed:
- source: salt://apache/httpd.conf
- template: jinja
- context:
bind: {{ grains['ipv4'][-1] }}
port: {{ pillar['port'] }}
推送:
[root@server1 apache]# salt server3 state.sls apache
当然也可以直接在配置文件中调用grains或者pillar:
[root@server1 apache]# vim init.sls
[root@server1 apache]# cat init.sls
apache:
pkg.installed:
- pkgs:
- {{ pillar['webserver'] }}
service.running:
- name: httpd
- reload: true
- enable: true
- watch:
- file: /etc/httpd/conf/httpd.conf
/etc/httpd/conf/httpd.conf:
file.managed:
- source: salt://apache/httpd.conf
- template: jinja #注意需要启用jinja模板
[root@server1 apache]# vim httpd.conf
[root@server1 apache]# cat -n httpd.conf | grep 42
42 Listen {{ grains['ipv4'][-1] }}:{{ pillar['port'] }}
然后推送:
[root@server1 apache]# salt server3 state.sls apache
import方式
第三种方式为import方式,可在state文件之间共享:
定义变量文件:
[root@server1 salt]# vim lib.sls
[root@server1 salt]# cat lib.sls
{% set port = 80 %}
在普通文件中导入模板,并调用:
[root@server1 salt]# cd apache/
[root@server1 apache]# vim httpd.conf
[root@server1 apache]# head -1 httpd.conf
{% from 'lib.sls' import port %}
[root@server1 apache]# cat -n httpd.conf | grep 43
43 Listen {{ grains['ipv4'][-1] }}:{{ port }}
推送:
[root@server1 apache]# salt server3 state.sls apache
在server3查看可以看出配置已经生效:
[root@server3 ~]# netstat -antlpe | grep httpd
tcp 0 0 172.25.63.3:80 0.0.0.0:* LISTEN 0 45983 3749/httpd
通过import的方式导入的变量优先级高于在init文件中定义的变量,原因是在运行的时候最后读取的是import方式导入的变量。
注意:一般习惯将变量都定义在init文件中,然后在其他文件中引用即可。
三、Jinja模板应用之部署keepalived高可用集群
我们这里准备将server2设置为master节点,server3为backup节点,vip为172.25.63.100。
编辑init文件:
[root@server1 salt]# mkdir keepalived
[root@server1 salt]# cd keepalived/
[root@server1 keepalived]# vim init.sls
[root@server1 keepalived]# cat init.sls
install-kp:
pkg.installed:
- name: keepalived
file.managed:
- name: /etc/keepalived/keepalived.conf
- source: salt://keepalived/keepalived.conf
service.running:
- name: keepalived
- reload: true
- watch:
- file: install-kp
复制配置文件:
[root@server1 keepalived]# scp server2:/etc/keepalived/keepalived.conf .
[root@server1 keepalived]# ls
init.sls keepalived.conf
编辑配置文件:
[root@server1 keepalived]# vim keepalived.conf
[root@server1 keepalived]# cat keepalived.conf
! Configuration File for keepalived
global_defs {
notification_email {
root@localhost
}
notification_email_from keepalived@localhost
smtp_server 127.0.0.1
smtp_connect_timeout 30
router_id LVS_DEVEL
}
vrrp_instance VI_1 {
state MASTER
interface eth0
virtual_router_id 51
priority 100
advert_int 1
authentication {
auth_type PASS
auth_pass 1111
}
virtual_ipaddress {
172.25.63.100
}
}
可以看出配置文件中的角色为master,优先级为100,vip为172.25.63.100。
推送给server2测试:
[root@server1 keepalived]# salt server2 state.sls keepalived
server2部署成功,但是现在有一个问题,server3(backup节点)的配置文件和server2不同,不能直接推送,我们可以结合jinja模板与pillar实现不同主机的配置文件不同。
更改配置文件:
[root@server1 keepalived]# vim keepalived.conf
[root@server1 keepalived]# cat keepalived.conf
! Configuration File for keepalived
global_defs {
notification_email {
root@localhost
}
notification_email_from keepalived@localhost
smtp_server 127.0.0.1
smtp_connect_timeout 30
router_id LVS_DEVEL
}
vrrp_instance VI_1 {
state {{ STATE }}
interface eth0
virtual_router_id 51
priority {{ PRI }}
advert_int 1
authentication {
auth_type PASS
auth_pass 1111
}
virtual_ipaddress {
{{ VIP }}
}
}
其中STATE、PRI、VIP为变量
在init文件中将pillar变量赋值给配置文件中的三个变量:
[root@server1 pillar]# cd -
/srv/salt/keepalived
[root@server1 keepalived]# vim init.sls
[root@server1 keepalived]# cat init.sls
install-kp:
pkg.installed:
- name: keepalived
file.managed:
- name: /etc/keepalived/keepalived.conf
- source: salt://keepalived/keepalived.conf
- template: jinja
- context:
STATE: {{ pillar['kpstate'] }} #将pillar变量赋值给配置文件中的三个变量
PRI: {{ pillar['kppri'] }}
VIP: {{ pillar['vip'] }}
service.running:
- name: keepalived
- reload: true
- watch:
- file: install-kp
接下来我们就需要定义pillar变量:
[root@server1 keepalived]# cd /srv/pillar/
[root@server1 pillar]# vim web.sls
[root@server1 pillar]# cat web.sls
{% if grains['fqdn'] == 'server2' %}
kpstate: MASTER
kppri: 100
{% elif grains['fqdn'] == 'server3' %}
kpstate: BACKUP
kppri: 50
{% endif %}
现在给两个节点推送pillar和init。sls:
[root@server1 keepalived]# salt '*' state.sls keepalived