This state is intended for use from the Salt Master. It provides access to sending commands down to minions as well as access to executing master-side modules. These state functions wrap Salt's Python API.
Support for masterless minions was added to thesalt.state
function, so they can run orchestration sls files. This is particularly useful when the rendering of a state is dependent on the execution of another state. Orchestration will render and execute each orchestration block independently, while honoring requisites to ensure the states are applied in the correct order.
Execute a single module function on a remote minion via salt or salt-ssh
glob
10%
.Number of minions from the targeted set to randomly use
New in version 2017.7.0.
Executes multiple runner modules on the master in parallel.
New in version 2017.x.0: (Nitrogen)
A separate thread is spawned for each runner. This state is intended to be used with the orchestrate runner in place of the saltmod.runner
state when different tasks should be run in parallel. In general, Salt states are not safe when used concurrently, so ensure that they are used in a safe way (e.g. by only targeting separate minions in parallel tasks).
parallel-state: salt.parallel_runners: - runners: my_runner_1: - name: state.orchestrate - kwarg: mods: orchestrate_state_1 my_runner_2: - name: state.orchestrate - kwarg: mods: orchestrate_state_2
Execute a runner module on the master
New in version 2014.7.0.
run-manage-up: salt.runner: - name: manage.up
Invoke a state run on a given target
The target specification for the state run.
Masterless support: When running on a masterless minion, the tgt
is ignored and will always be the local minion.
glob
test=true
or test=false
through to the state function. This can be used to overide a test mode set in the minion's config file. If left as the default of None and the 'test' mode is supplied on the command line, that value is passed instead.pillar
kwarg through to the state functionThe pillar environment to grab pillars from
New in version 2017.7.0.
Allow multiple state runs to occur at once.
WARNING: This flag is potentially dangerous. It is designed for use when multiple state runs can safely be run at the same Do not use this flag for performance optimization.
queue=true
through to the state functionExecute the command in batches. E.g.: 10%
.
New in version 2016.3.0.
Number of minions from the targeted set to randomly use
New in version 2017.7.0.
Examples:
Run a list of sls files via state.sls
on target minions:
webservers: salt.state: - tgt: 'web*' - sls: - apache - django - core - saltenv: prod
Run a full state.highstate
on target mininons.
databases: salt.state: - tgt: role:database - tgt_type: grain - highstate: True
Watch Salt's event bus and block until a condition is met
New in version 2014.7.0.
event_id
, if found it is removed from id_list
. When id_list
is empty this function returns success.id
for the minion ID, another common value is name
for use with orchestrating salt-cloud events.The following example blocks until all the listed minions complete a restart and reconnect to the Salt master:
reboot_all_minions: salt.function: - name: system.reboot - tgt: '*' wait_for_reboots: salt.wait_for_event: - name: salt/minion/*/start - id_list: - jerry - stuart - dave - phil - kevin - mike - require: - salt: reboot_all_minions
Execute a wheel module on the master
New in version 2014.7.0.
accept_minion_key: salt.wheel: - name: key.accept - match: frank
© 2019 SaltStack.
Licensed under the Apache License, Version 2.0.
https://docs.saltstack.com/en/latest/ref/states/all/salt.states.saltmod.html