(v) Slatstack Dynamic Data System pillar

Pillar

Pillar are dynamic, specifying specific data for specific minion. Only minion own data he can see himself (like Top file)

Action Scenario:

1. Define user name and password

2. Dynamic Scenarios

3. Use of sensitive data scenarios

Example:

Look at Master's Pillar.items.

[[email protected] ~]# Salt ' * ' Pillar.items

Salt-client.com:

----------

At this point we see that there is no information, in fact there is, but the default is not shown, we can through the more

Change the configuration file to show:

Specific commands:

[Email protected] ~]# Vim/etc/salt/master

Search Pillar

552 rows

Pillar_opts:true

then save the exit;

#重启salt-master

Description: In the production environment, the configuration of pillar in master configuration file remains the default;

To refresh the configuration command for pillar:

[[Email protected] ~] #salt ' * ' saltutil.refresh_pillar

Pillar Usage Scenarios:

1. Target selection salt-i (specify match)

Specify target: Targeting

Two kinds:

1) related to Minion ID

2) and Minion ID-Independent

Minion ID-related methods:

1.) Wildcard characters:

Salt ' slat-client.com ' test.ping

Salt ' * ' test.ping

2.) List:

Salt-l ' linux-slat1-client.com,linux-slat2-client.com ' test.ping

3.) Regular expression

Salt-e ' linux-(SLAT1|SLAT2) |. Client.com ' test.ping

Description: All matching targets are used in the top file to target.

4.) Mixed match

Salt-c

Grains: Static boot time Collection data query target selection configuration management Grains on Minion side

Pillar: Dynamic master Custom Target selection configuration management sensitive data storage Pillar on the master side

This article is from the "Bill Linux Operations Notes" blog, please be sure to keep this source http://chenshoubiao.blog.51cto.com/6159058/1884487

(v) Slatstack Dynamic Data System pillar