Salt provides several entry points for interfacing with Python applications.
These entry points are often referred to as *Client()
APIs. Each client
accesses different parts of Salt, either from the master or from a minion. Each
client is detailed below.
Note
For Tiamat-bundled Salt distribution, you need to use the bundled Python runtime as the system Python won't be able to access Salt internals.
To execute scripts via bundled Python runtime, either run the script with
/path/to/salt python script.py
or use #!/path/to/salt python
shebang
See also
There are many ways to access Salt programmatically.
Salt can be used from CLI scripts as well as via a REST interface.
See Salt's outputter system to retrieve structured data from Salt as JSON, or as shell-friendly text, or many other formats.
See the state.event
runner to utilize
Salt's event bus from shell scripts.
Salt's netapi module provides access to Salt externally via a REST interface. Review the netapi module documentation for more information.
opts
dictionary¶Some clients require access to Salt's opts
dictionary. (The dictionary
representation of the master or
minion config files.)
A common pattern for fetching the opts
dictionary is to defer to
environment variables if they exist or otherwise fetch the config from the
default location.
Load Master configuration data
Usage:
import salt.config
master_opts = salt.config.client_config('/etc/salt/master')
Returns a dictionary of the Salt Master configuration file with necessary options needed to communicate with a locally-running Salt Master daemon. This function searches for client specific configurations and adds them to the data from the master configuration.
This is useful for master-side operations like
LocalClient
.
Reads in the minion configuration file and sets up special options
This is useful for Minion-side operations, such as the
Caller
class, and manually running the loader
interface.
import salt.config
minion_opts = salt.config.minion_config('/etc/salt/minion')
Modules in the Salt ecosystem are loaded into memory using a custom loader
system. This allows modules to have conditional requirements (OS, OS version,
installed libraries, etc) and allows Salt to inject special variables
(__salt__
, __opts__
, etc).
Most modules can be manually loaded. This is often useful in third-party Python
apps or when writing tests. However some modules require and expect a full,
running Salt system underneath. Notably modules that facilitate
master-to-minion communication such as the mine
,
publish
, and peer
execution
modules. The error KeyError: 'master_uri'
is a likely indicator for this
situation. In those instances use the Caller
class
to execute those modules instead.
Each module type has a corresponding loader function.
Load execution modules
Returns a dictionary of execution modules appropriate for the current system by evaluating the __virtual__() function in each module.
opts (dict) -- The Salt options dictionary
context (dict) -- A Salt context that should be made present inside generated modules in __context__
utils (dict) -- Utility functions which should be made available to Salt modules in __utils__. See utils_dirs in salt.config for additional information about configuration.
whitelist (list) -- A list of modules which should be whitelisted.
initial_load (bool) -- Deprecated flag! Unused.
loaded_base_name (str) -- The imported modules namespace when imported by the salt loader.
notify (bool) -- Flag indicating that an event should be fired upon completion of module loading.
Example:
import salt.config
import salt.loader
__opts__ = salt.config.minion_config('/etc/salt/minion')
__grains__ = salt.loader.grains(__opts__)
__opts__['grains'] = __grains__
__utils__ = salt.loader.utils(__opts__)
__salt__ = salt.loader.minion_mods(__opts__, utils=__utils__)
__salt__['test.ping']()
Returns a single module loaded raw and bypassing the __virtual__ function
Example:
import salt.config
import salt.loader
__opts__ = salt.config.minion_config('/etc/salt/minion')
testmod = salt.loader.raw_mod(__opts__, 'test', None)
testmod['test.ping']()
Returns the state modules
opts (dict) -- The Salt options dictionary
functions (LazyLoader) -- A LazyLoader instance returned from minion_mods
.
runners (LazyLoader) -- A LazyLoader instance returned from runner
.
utils (LazyLoader) -- A LazyLoader instance returned from utils
.
serializers (LazyLoader) -- An optional LazyLoader instance returned from serializers
.
proxy (LazyLoader) -- An optional LazyLoader instance returned from proxy
.
whitelist (list) -- A list of modules which should be whitelisted.
context (dict) -- A Salt context that should be made present inside generated modules in __context__
loaded_base_name (str) -- The imported modules namespace when imported by the salt loader.
import salt.config
import salt.loader
__opts__ = salt.config.minion_config('/etc/salt/minion')
statemods = salt.loader.states(__opts__, None, None)
Return the functions for the dynamic grains and the values for the static grains.
opts (dict) -- The Salt options dictionary
force_refresh (bool) -- Force the refresh of grains
context (dict) -- A Salt context that should be made present inside generated modules in __context__
proxy (LazyLoader) -- An optional LazyLoader instance returned from proxy
.
loaded_base_name (str) -- The imported modules namespace when imported by the salt loader.
Since grains are computed early in the startup process, grains functions do not have __salt__ or __proxy__ available. At proxy-minion startup, this function is called with the proxymodule LazyLoader object so grains functions can communicate with their controlled device.
import salt.config
import salt.loader
__opts__ = salt.config.minion_config('/etc/salt/minion')
__grains__ = salt.loader.grains(__opts__)
print __grains__['id']
Returns the grain functions
opts (dict) -- The Salt options dictionary
context (dict) -- A Salt context that should be made present inside generated modules in __context__
proxy (LazyLoader) -- An optional LazyLoader instance returned from proxy
.
loaded_base_name (str) --
by the salt loader.
import salt.config
import salt.loader
__opts__ = salt.config.minion_config('/etc/salt/minion')
grainfuncs = salt.loader.grain_funcs(__opts__)
The interface used by the salt CLI tool on the Salt Master
LocalClient
is used to send a command to Salt minions to execute
execution modules and return the results to the
Salt Master.
Importing and using LocalClient
must be done on the same machine as the
Salt Master and it must be done using the same user that the Salt Master is
running as. (Unless external_auth
is configured and
authentication credentials are included in the execution).
Note
The LocalClient uses a Tornado IOLoop, this can create issues when using the LocalClient inside an existing IOLoop. If creating the LocalClient in partnership with another IOLoop either create the IOLoop before creating the LocalClient, or when creating the IOLoop use ioloop.current() which will return the ioloop created by LocalClient.
import salt.client
local = salt.client.LocalClient()
local.cmd('*', 'test.fib', [10])
Synchronously execute a command on targeted minions
The cmd method will execute and wait for the timeout period for all minions to reply, then it will return all minion data at once.
>>> import salt.client
>>> local = salt.client.LocalClient()
>>> local.cmd('*', 'cmd.run', ['whoami'])
{'jerry': 'root'}
With extra keyword arguments for the command function to be run:
local.cmd('*', 'test.arg', ['arg1', 'arg2'], kwarg={'foo': 'bar'})
Compound commands can be used for multiple executions in a single publish. Function names and function arguments are provided in separate lists but the index values must correlate and an empty list must be used if no arguments are required.
>>> local.cmd('*', [
'grains.items',
'sys.doc',
'cmd.run',
],
[
[],
[],
['uptime'],
])
tgt (string or list) -- Which minions to target for the execution. Default is shell
glob. Modified by the tgt_type
option.
fun (string or list of strings) --
The module and function to call on the specified minions of
the form module.function
. For example test.ping
or
grains.items
.
Multiple functions may be called in a single publish by passing a list of commands. This can dramatically lower overhead and speed up the application communicating with Salt.
This requires that the arg
param is a list of lists. The
fun
list and the arg
list must correlate by index
meaning a function that does not take arguments must still have
a corresponding empty list at the expected index.
arg (list or list-of-lists) -- A list of arguments to pass to the remote function. If the
function takes no arguments arg
may be omitted except when
executing a compound command.
timeout -- Seconds to wait after the last minion returns but before all minions return.
tgt_type --
The type of tgt
. Allowed values:
glob
- Bash glob completion - Default
pcre
- Perl style regular expression
list
- Python list of hosts
grain
- Match based on a grain comparison
grain_pcre
- Grain comparison with a regex
pillar
- Pillar data comparison
pillar_pcre
- Pillar data comparison with a regex
nodegroup
- Match on nodegroup
range
- Use a Range server for matching
compound
- Pass a compound match string
ipcidr
- Match based on Subnet (CIDR notation) or IPv4 address.
Changed in version 2017.7.0: Renamed from expr_form
to tgt_type
ret -- The returner to use. The value passed can be single returner, or a comma delimited list of returners to call in order on the minions
kwarg -- A dictionary with keyword arguments for the function.
full_return -- Output the job return only (default) or the full return including exit code and other job metadata.
kwargs --
Optional keyword arguments.
Authentication credentials may be passed when using
external_auth
.
For example: local.cmd('*', 'test.ping', username='saltdev',
password='saltdev', eauth='pam')
.
Or: local.cmd('*', 'test.ping',
token='5871821ea51754fdcea8153c1c745433')
A dictionary with the result of the execution, keyed by minion ID. A compound command will return a sub-dictionary keyed by function name.
Asynchronously send a command to connected minions
The function signature is the same as cmd()
with the
following exceptions.
A job ID or 0 on failure.
>>> local.cmd_async('*', 'test.sleep', [300])
'20131219215921857715'
Iteratively execute a command on subsets of minions at a time
The function signature is the same as cmd()
with the
following exceptions.
batch -- The batch identifier of systems to execute on
A generator of minion returns
>>> returns = local.cmd_batch('*', 'state.highstate', batch='10%')
>>> for ret in returns:
... print(ret)
{'jerry': {...}}
{'dave': {...}}
{'stewart': {...}}
Yields the individual minion returns as they come in
The function signature is the same as cmd()
with the
following exceptions.
Normally cmd_iter()
does not yield results for minions that
are not connected. If you want it to return results for disconnected
minions set expect_minions=True in kwargs.
A generator yielding the individual minion returns
>>> ret = local.cmd_iter('*', 'test.ping')
>>> for i in ret:
... print(i)
{'jerry': {'ret': True}}
{'dave': {'ret': True}}
{'stewart': {'ret': True}}
when no returns are available.
The function signature is the same as cmd()
with the
following exceptions.
A generator yielding the individual minion returns, or None when no returns are available. This allows for actions to be injected in between minion returns.
>>> ret = local.cmd_iter_no_block('*', 'test.ping')
>>> for i in ret:
... print(i)
None
{'jerry': {'ret': True}}
{'dave': {'ret': True}}
None
{'stewart': {'ret': True}}
Execute a command on a random subset of the targeted systems
The function signature is the same as cmd()
with the
following exceptions.
subset -- The number of systems to execute on
cli -- When this is set to True, a generator is returned, otherwise a dictionary of the minion returns is returned
>>> SLC.cmd_subset('*', 'test.ping', subset=1)
{'jerry': True}
Starts a watcher looking at the return data for a specified JID
all of the information for the JID
Gather the return data from the event system, break hard when timeout is reached.
Asynchronously send a command to connected minions
Prep the job directory and publish a command to any targeted minions.
A dictionary of (validated) pub_data
or an empty
dictionary on failure. The pub_data
contains the job ID and a
list of all minions that are expected to return data.
>>> local.run_job('*', 'test.sleep', [300])
{'jid': '20131219215650131543', 'minions': ['jerry']}
Caller
is the same interface used by the salt-call
command-line tool on the Salt Minion.
Changed in version 2015.8.0: Added the cmd
method for consistency with the other Salt clients.
The existing function
and sminion.functions
interfaces still
exist but have been removed from the docs.
Importing and using Caller
must be done on the same machine as a
Salt Minion and it must be done using the same user that the Salt Minion is
running as.
Usage:
import salt.client
caller = salt.client.Caller()
caller.cmd('test.ping')
Note, a running master or minion daemon is not required to use this class.
Running salt-call --local
simply sets file_client
to
'local'
. The same can be achieved at the Python level by including that
setting in a minion config file.
New in version 2014.7.0: Pass the minion config as the mopts
dictionary.
import salt.client
import salt.config
__opts__ = salt.config.minion_config('/etc/salt/minion')
__opts__['file_client'] = 'local'
caller = salt.client.Caller(mopts=__opts__)
Call an execution module with the given arguments and keyword arguments
Changed in version 2015.8.0: Added the cmd
method for consistency with the other Salt clients.
The existing function
and sminion.functions
interfaces still
exist but have been removed from the docs.
caller.cmd('test.arg', 'Foo', 'Bar', baz='Baz')
caller.cmd('event.send', 'myco/myevent/something',
data={'foo': 'Foo'}, with_env=['GIT_COMMIT'], with_grains=True)
ProxyCaller
is the same interface used by the salt-call
with the args --proxyid <proxyid>
command-line tool on the Salt Proxy
Minion.
Importing and using ProxyCaller
must be done on the same machine as a
Salt Minion and it must be done using the same user that the Salt Minion is
running as.
Usage:
import salt.client
caller = salt.client.ProxyCaller()
caller.cmd('test.ping')
Note, a running master or minion daemon is not required to use this class.
Running salt-call --local
simply sets file_client
to
'local'
. The same can be achieved at the Python level by including that
setting in a minion config file.
import salt.client
import salt.config
__opts__ = salt.config.proxy_config('/etc/salt/proxy', minion_id='quirky_edison')
__opts__['file_client'] = 'local'
caller = salt.client.ProxyCaller(mopts=__opts__)
Note
To use this for calling proxies, the is_proxy functions
requires that --proxyid
be an
argument on the commandline for the script this is used in, or that the
string proxy
is in the name of the script.
Call an execution module with the given arguments and keyword arguments
caller.cmd('test.arg', 'Foo', 'Bar', baz='Baz')
caller.cmd('event.send', 'myco/myevent/something',
data={'foo': 'Foo'}, with_env=['GIT_COMMIT'], with_grains=True)
The interface used by the salt-run CLI tool on the Salt Master
It executes runner modules which run on the Salt Master.
Importing and using RunnerClient
must be done on the same machine as
the Salt Master and it must be done using the same user that the Salt
Master is running as.
Salt's external_auth
can be used to authenticate calls. The
eauth user must be authorized to execute runner modules: (@runner
).
Only the master_call()
below supports eauth.
Execute the function in a multiprocess and return the event tag to use to watch for the return
Execute a function
>>> opts = salt.config.master_config('/etc/salt/master')
>>> runner = salt.runner.RunnerClient(opts)
>>> runner.cmd('jobs.list_jobs', [])
{
'20131219215650131543': {
'Arguments': [300],
'Function': 'test.sleep',
'StartTime': '2013, Dec 19 21:56:50.131543',
'Target': '*',
'Target-type': 'glob',
'User': 'saltdev'
},
'20131219215921857715': {
'Arguments': [300],
'Function': 'test.sleep',
'StartTime': '2013, Dec 19 21:59:21.857715',
'Target': '*',
'Target-type': 'glob',
'User': 'saltdev'
},
}
Execute a runner function asynchronously; eauth is respected
This function requires that external_auth
is configured
and the user is authorized to execute runner functions: (@runner
).
runner.cmd_async({
'fun': 'jobs.list_jobs',
'username': 'saltdev',
'password': 'saltdev',
'eauth': 'pam',
})
Execute a runner function synchronously; eauth is respected
This function requires that external_auth
is configured
and the user is authorized to execute runner functions: (@runner
).
runner.cmd_sync({
'fun': 'jobs.list_jobs',
'username': 'saltdev',
'password': 'saltdev',
'eauth': 'pam',
})
An interface to Salt's wheel modules
Wheel modules interact with various parts of the Salt Master.
Importing and using WheelClient
must be done on the same machine as the
Salt Master and it must be done using the same user that the Salt Master is
running as. Unless external_auth
is configured and the user
is authorized to execute wheel functions: (@wheel
).
Usage:
import salt.config
import salt.wheel
opts = salt.config.master_config('/etc/salt/master')
wheel = salt.wheel.WheelClient(opts)
Execute the function in a multiprocess and return the event tag to use to watch for the return
Execute a function
>>> wheel.cmd('key.finger', ['jerry'])
{'minions': {'jerry': '5d:f6:79:43:5e:d4:42:3f:57:b8:45:a8:7e:a4:6e:ca'}}
Execute a function asynchronously; eauth is respected
This function requires that external_auth
is configured
and the user is authorized
>>> wheel.cmd_async({
'fun': 'key.finger',
'match': 'jerry',
'eauth': 'auto',
'username': 'saltdev',
'password': 'saltdev',
})
{'jid': '20131219224744416681', 'tag': 'salt/wheel/20131219224744416681'}
Execute a wheel function synchronously; eauth is respected
This function requires that external_auth
is configured
and the user is authorized to execute runner functions: (@wheel
).
>>> wheel.cmd_sync({
'fun': 'key.finger',
'match': 'jerry',
'eauth': 'auto',
'username': 'saltdev',
'password': 'saltdev',
})
{'minions': {'jerry': '5d:f6:79:43:5e:d4:42:3f:57:b8:45:a8:7e:a4:6e:ca'}}
The client class to wrap cloud interactions
Execute a single action via the cloud plugin backend
Examples:
client.action(fun='show_instance', names=['myinstance'])
client.action(fun='show_image', provider='my-ec2-config',
kwargs={'image': 'ami-10314d79'}
)
Create the named VMs, without using a profile
Example:
client.create(provider='my-ec2-config', names=['myinstance'],
image='ami-1624987f', size='t1.micro', ssh_username='ec2-user',
securitygroup='default', delvol_on_destroy=True)
Destroy the named VMs
Perform actions with block storage devices
Example:
client.extra_action(names=['myblock'], action='volume_create',
provider='my-nova', kwargs={'voltype': 'SSD', 'size': 1000}
)
client.extra_action(names=['salt-net'], action='network_create',
provider='my-nova', kwargs={'cidr': '192.168.100.0/24'}
)
Query all instance information
List all available images in configured cloud systems
List all available locations in configured cloud systems
List all available sizes in configured cloud systems
Pass the cloud function and low data structure to run
To execute a map
Query select instance information
Pass in a profile to create, names is a list of vm names to allocate
vm_overrides is a special dict that will be per node options overrides
Example:
>>> client= salt.cloud.CloudClient(path='/etc/salt/cloud')
>>> client.profile('do_512_git', names=['minion01',])
{'minion01': {'backups_active': 'False',
'created_at': '2014-09-04T18:10:15Z',
'droplet': {'event_id': 31000502,
'id': 2530006,
'image_id': 5140006,
'name': 'minion01',
'size_id': 66},
'id': '2530006',
'image_id': '5140006',
'ip_address': '107.XXX.XXX.XXX',
'locked': 'True',
'name': 'minion01',
'private_ip_address': None,
'region_id': '4',
'size_id': '66',
'status': 'new'}}
Query basic instance information
Query select instance information
Create a client object for executing routines via the salt-ssh backend
New in version 2015.5.0.
Execute a single command via the salt-ssh subsystem and return all routines at once
New in version 2015.5.0.
Execute a single command via the salt-ssh subsystem and return a generator
New in version 2015.5.0.