We only need one fancy pillar example to match our state.

This commit is contained in:
rallytime 2015-11-16 20:08:52 -07:00
parent e2926b1996
commit d53713ddba

View File

@ -4,7 +4,7 @@ Manage chassis via Salt Proxies.
.. versionadded:: 2015.8.2
Below is an example state that sets parameters just to show the basics.
Below is an example state that sets basic parameters:
.. code-block:: yaml
@ -31,7 +31,9 @@ data in pillar. Here's an example pillar structure:
proxy:
host: 10.27.20.18
admin_username: root
admin_password: saltstack
admin_password: super-secret
fallback_admin_username: root
fallback_admin_password: old-secret
proxytype: fx2
chassis:
@ -86,33 +88,8 @@ data in pillar. Here's an example pillar structure:
snmp: nonpublic
password: saltstack1
And to go with it, here's an example state that pulls the data from pillar.
This example assumes that the pillar data would be structured like:
Pillar:
.. code-block:: yaml
proxy:
host: 192.168.1.1
admin_username: root
admin_password: sekrit
fallback_admin_username: root
fallback_admin_password: old_sekrit
proxytype: fx2
chassis:
name: fx2-1
username: root
datacenter: UT1
location: UT1
management_mode: 2
idrac_launch: 0
slot_names:
1: blade1
2: blade2
State:
And to go with it, here's an example state that pulls the data from the
pillar stated above:
.. code-block:: yaml
@ -140,7 +117,7 @@ State:
{% endfor %}
blade_powercycle:
chassis.chassis:
dellchassis.chassis:
- blade_power_states:
- server-1: powercycle
- server-2: powercycle