saltstack/salt
1
0
Fork 0
mirror of https://github.com/saltstack/salt.git synced 2025-04-17 10:10:20 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

Update nodegroups.rst

Browse source 
cleaned up text lines that were too long
This commit is contained in:
sdm24 2015-10-26 11:31:57 -07:00
parent b2c3307c2e
commit 02cac9d8c0
1 changed files with 16 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

25
doc/topics/targeting/nodegroups.rst
View file

@ -71,17 +71,22 @@ nodegroup`` on the line directly following the nodegroup name.
Using Nodegroups in SLS files
=============================
To use Nodegroups in Jinja logic for SLS files, the :conf_master:'pillar_opts' option in ``/etc/salt/master`` must be set to "True". This will pass the master's configuration as Pillar data to each minion.
To use Nodegroups in Jinja logic for SLS files, the :conf_master:'pillar_opts' option in
``/etc/salt/master`` must be set to "True". This will pass the master's configuration as
Pillar data to each minion.
.. note::
If the master's configuration contains any sensitive data, this will be passed to each minion. Do not enable this
option if you have any configuration data that you do not want to get on your minions.
If the master's configuration contains any sensitive data, this will be passed to each minion.
Do not enable this option if you have any configuration data that you do not want to get
on your minions.
Also, if you make changes to your nodegroups, you might need to run ``salt '*' saltutil.refresh_pillar`` after
restarting the master.
Also, if you make changes to your nodegroups, you might need to run
``salt '*' saltutil.refresh_pillar`` after restarting the master.
Once pillar_opts is enabled, you can find the nodegroups under the "master" pillar. To make sure that only the correct minions are targeted, you should use each matcher for the nodegroup definition.
Once pillar_opts is enabled, you can find the nodegroups under the "master" pillar.
To make sure that only the correct minions are targeted,
you should use each matcher for the nodegroup definition.
For example, to check if a minion is in the 'webserver' nodegroup:
.. code-block:: yaml
@ -91,11 +96,13 @@ For example, to check if a minion is in the 'webserver' nodegroup:
.. code-block:: yaml
{% if grains.id in salt['pillar.get']('master:nodegroups:webserver', []) and grains.os in salt['pillar.get']('master:nodegroups:webserver', []) %}
{% if grains.id in salt['pillar.get']('master:nodegroups:webserver', [])
and grains.os in salt['pillar.get']('master:nodegroups:webserver', []) %}
...
{% endif %}
.. note::
If you do not include all of the matchers used to define a nodegroup, Salt might incorrectly target minions
that meet some of the nodegroup requirements, but not all of them.
If you do not include all of the matchers used to define a nodegroup,
Salt might incorrectly target minions that meet some of the nodegroup
requirements, but not all of them.