0
0
mirror of https://github.com/saltstack-formulas/salt-formula.git synced 2024-12-27 06:43:33 +01:00
salt-formula/salt/files/master.d/f_defaults.conf

1235 lines
46 KiB
Plaintext
Raw Normal View History

2013-08-13 19:20:10 +02:00
# This file managed by Salt, do not edit by hand!!
# Based on salt version 2015.8.7 default config
2014-10-03 10:43:59 +02:00
{% set reserved_keys = ['master', 'minion', 'cloud', 'salt_cloud_certs'] -%}
{% set cfg_salt = pillar.get('salt', {}) -%}
{% set cfg_master = cfg_salt.get('master', {}) -%}
2013-08-13 23:00:08 +02:00
{%- macro get_config(configname, default_value) -%}
{%- if configname in cfg_master -%}
{{ configname }}: {{ cfg_master[configname] }}
{%- elif configname in cfg_salt and configname not in reserved_keys -%}
{{ configname }}: {{ cfg_salt[configname] }}
2013-08-13 23:00:08 +02:00
{%- else -%}
#{{ configname }}: {{ default_value }}
{%- endif -%}
{%- endmacro -%}
{%- from 'salt/formulas.jinja' import file_roots, formulas with context -%}
2013-06-13 01:53:26 +02:00
##### Primary configuration settings #####
##########################################
# This configuration file is used to manage the behavior of the Salt Master.
# Values that are commented out but have an empty line after the comment are
# defaults that do not need to be set in the config. If there is no blank line
# after the comment then the value is presented as an example and is not the
# default.
2013-06-13 01:53:26 +02:00
# Per default, the master will automatically include all config files
# from master.d/*.conf (master.d is a directory in the same directory
# as the main master config file).
2013-08-13 23:00:08 +02:00
{{ get_config('default_include', 'master.d/*.conf') }}
2013-06-13 01:53:26 +02:00
# The address of the interface to bind to:
2013-08-13 23:00:08 +02:00
{{ get_config('interface', '0.0.0.0') }}
# Whether the master should listen for IPv6 connections. If this is set to True,
# the interface option must be adjusted, too. (For example: "interface: '::'")
2013-08-13 23:00:08 +02:00
{{ get_config('ipv6', 'False') }}
2013-06-13 01:53:26 +02:00
# The tcp port used by the publisher:
2013-08-13 23:00:08 +02:00
{{ get_config('publish_port', '4505') }}
2013-06-13 01:53:26 +02:00
# The user under which the salt master will run. Salt will update all
# permissions to allow the specified user to run the master. The exception is
# the job cache, which must be deleted if this user is changed. If the
# modified files cause conflicts, set verify_env to False.
2013-08-13 23:00:08 +02:00
{{ get_config('user', 'root') }}
2013-06-13 01:53:26 +02:00
# The port used by the communication interface. The ret (return) port is the
# interface used for the file server, authentication, job returns, etc.
2013-08-13 23:00:08 +02:00
{{ get_config('ret_port', '4506') }}
2013-06-13 01:53:26 +02:00
# Specify the location of the daemon process ID file:
2013-08-13 23:00:08 +02:00
{{ get_config('pidfile', '/var/run/salt-master.pid') }}
2013-06-13 01:53:26 +02:00
# The root directory prepended to these options: pki_dir, cachedir,
# sock_dir, log_file, autosign_file, autoreject_file, extension_modules,
# key_logfile, pidfile:
2013-08-13 23:00:08 +02:00
{{ get_config('root_dir', '/') }}
2013-06-13 01:53:26 +02:00
# Directory used to store public key data:
2013-08-13 23:00:08 +02:00
{{ get_config('pki_dir', '/etc/salt/pki/master') }}
2013-06-13 01:53:26 +02:00
# Directory to store job and cache data:
# This directory may contain sensitive data and should be protected accordingly.
#
2013-08-13 23:00:08 +02:00
{{ get_config('cachedir', '/var/cache/salt/master') }}
2013-06-13 01:53:26 +02:00
# Directory for custom modules. This directory can contain subdirectories for
# each of Salt's module types such as "runners", "output", "wheel", "modules",
# "states", "returners", etc.
{{ get_config('extension_modules', '<no default>') }}
# Directory for custom modules. This directory can contain subdirectories for
# each of Salt's module types such as "runners", "output", "wheel", "modules",
# "states", "returners", etc.
# Like 'extension_modules' but can take an array of paths
{% if 'module_dirs' in cfg_master -%}
module_dirs:
{%- for dir in cfg_master['module_dirs'] %}
- {{ dir}}
{%- endfor -%}
{% elif 'module_dirs' in cfg_salt -%}
module_dirs:
{%- for dir in cfg_salt['module_dirs'] %}
- {{ dir}}
{%- endfor -%}
{% else -%}
#module_dirs: <no default>
# - /var/cache/salt/minion/extmods
{% endif %}
# Verify and set permissions on configuration directories at startup:
2013-08-13 23:00:08 +02:00
{{ get_config('verify_env', 'True') }}
2013-06-13 01:53:26 +02:00
# Set the number of hours to keep old job information in the job cache:
2013-08-13 23:00:08 +02:00
{{ get_config('keep_jobs', '24') }}
2013-06-13 01:53:26 +02:00
# Set the default timeout for the salt command and api. The default is 5
# seconds.
2013-08-13 23:00:08 +02:00
{{ get_config('timeout', '5') }}
2013-06-13 01:53:26 +02:00
# The loop_interval option controls the seconds for the master's maintenance
2013-06-13 01:53:26 +02:00
# process check cycle. This process updates file server backends, cleans the
# job cache and executes the scheduler.
2013-08-13 23:00:08 +02:00
{{ get_config('loop_interval', '60') }}
2013-06-13 01:53:26 +02:00
# Set the default outputter used by the salt command. The default is "nested".
2013-08-13 23:00:08 +02:00
{{ get_config('output', 'nested') }}
2013-06-13 01:53:26 +02:00
# Return minions that timeout when running commands like test.ping
{{ get_config('show_timeout', 'True') }}
# By default, output is colored. To disable colored output, set the color value
# to False.
2013-08-13 23:00:08 +02:00
{{ get_config('color', 'True') }}
2013-06-13 01:53:26 +02:00
# Do not strip off the colored output from nested results and state outputs
# (true by default).
{{ get_config('strip_colors', 'False') }}
# Set the directory used to hold unix sockets:
2013-08-13 23:00:08 +02:00
{{ get_config('sock_dir', '/var/run/salt/master') }}
2013-06-13 01:53:26 +02:00
# The master can take a while to start up when lspci and/or dmidecode is used
# to populate the grains for the master. Enable if you want to see GPU hardware
# data for your master.
{{ get_config('enable_gpu_grains', 'False') }}
# The master maintains a job cache. While this is a great addition, it can be
2013-06-13 01:53:26 +02:00
# a burden on the master for larger deployments (over 5000 minions).
# Disabling the job cache will make previously executed jobs unavailable to
# the jobs system and is not generally recommended.
2013-08-13 23:00:08 +02:00
{{ get_config('job_cache', 'True') }}
2013-06-13 01:53:26 +02:00
# Cache minion grains and pillar data in the cachedir.
2013-08-13 23:00:08 +02:00
{{ get_config('minion_data_cache', 'True') }}
2013-06-13 01:53:26 +02:00
# Store all returns in the given returner.
# Setting this option requires that any returner-specific configuration also
# be set. See various returners in salt/returners for details on required
# configuration values. (See also, event_return_queue below.)
{{ get_config('event_return', 'mysql') }}
# On busy systems, enabling event_returns can cause a considerable load on
# the storage system for returners. Events can be queued on the master and
# stored in a batched fashion using a single transaction for multiple events.
# By default, events are not queued.
{{ get_config('event_return_queue', '0') }}
# Only events returns matching tags in a whitelist
{% if 'event_return_whitelist' in cfg_master -%}
event_return_whitelist:
{%- for event_return in cfg_master['event_return_whitelist'] %}
- {{ event_return }}
{%- endfor -%}
{% elif 'event_return_whitelist' in cfg_salt -%}
event_return_whitelist:
{%- for event_return in cfg_salt['event_return_whitelist'] %}
- {{ event_return }}
{%- endfor -%}
{% else -%}
# event_return_whitelist:
# - salt/master/a_tag
# - salt/master/another_tag
{% endif %}
# Store all event returns _except_ the tags in a blacklist
{% if 'event_return_blacklist' in cfg_master -%}
event_return_blacklist:
{%- for event_return in cfg_master['event_return_blacklist'] %}
- {{ event_return }}
{%- endfor -%}
{% elif 'event_return_blacklist' in cfg_salt -%}
event_return_blacklist:
{%- for event_return in cfg_salt['event_return_blacklist'] %}
- {{ event_return }}
{%- endfor -%}
{% else -%}
# event_return_blacklist:
# - salt/master/not_this_tag
# - salt/master/or_this_one
{% endif %}
# Passing very large events can cause the minion to consume large amounts of
# memory. This value tunes the maximum size of a message allowed onto the
# master event bus. The value is expressed in bytes.
{{ get_config('max_event_size', '1048576') }}
# By default, the master AES key rotates every 24 hours. The next command
# following a key rotation will trigger a key refresh from the minion which may
# result in minions which do not respond to the first command after a key refresh.
#
# To tell the master to ping all minions immediately after an AES key refresh, set
# ping_on_rotate to True. This should mitigate the issue where a minion does not
# appear to initially respond after a key is rotated.
#
# Note that ping_on_rotate may cause high load on the master immediately after
# the key rotation event as minions reconnect. Consider this carefully if this
# salt master is managing a large number of minions.
#
# If disabled, it is recommended to handle this event by listening for the
# 'aes_key_rotate' event with the 'key' tag and acting appropriately.
{{ get_config('ping_on_rotate', 'False') }}
# By default, the master deletes its cache of minion data when the key for that
# minion is removed. To preserve the cache after key deletion, set
# 'preserve_minion_cache' to True.
#
# WARNING: This may have security implications if compromised minions auth with
# a previous deleted minion ID.
{{ get_config('preserve_minion_cache', 'False') }}
# If max_minions is used in large installations, the master might experience
# high-load situations because of having to check the number of connected
# minions for every authentication. This cache provides the minion-ids of
# all connected minions to all MWorker-processes and greatly improves the
# performance of max_minions.
{{ get_config('con_cache', 'False') }}
2013-06-13 01:53:26 +02:00
# The master can include configuration from other files. To enable this,
# pass a list of paths to this option. The paths can be either relative or
# absolute; if relative, they are considered to be relative to the directory
# the main master configuration file lives in (this file). Paths can make use
# of shell-style globbing. If no files are matched by a path passed to this
# option, then the master will log a warning message.
2013-06-13 01:53:26 +02:00
#
# Include a config file from some other path:
# include: /etc/salt/extra_config
2013-06-13 01:53:26 +02:00
#
# Include config from several files and directories:
# include:
# - /etc/salt/extra_config
2013-08-13 23:00:08 +02:00
{{ get_config('include', '[]') }}
2013-06-13 01:53:26 +02:00
##### Large-scale tuning settings #####
##########################################
# Max open files
#
# Each minion connecting to the master uses AT LEAST one file descriptor, the
# master subscription connection. If enough minions connect you might start
# seeing on the console (and then salt-master crashes):
# Too many open files (tcp_listener.cpp:335)
# Aborted (core dumped)
#
# By default this value will be the one of `ulimit -Hn`, ie, the hard limit for
# max open files.
#
# If you wish to set a different value than the default one, uncomment and
# configure this setting. Remember that this value CANNOT be higher than the
# hard limit. Raising the hard limit depends on your OS and/or distribution,
# a good way to find the limit is to search the internet. For example:
# raise max open files hard limit debian
#
{{ get_config('max_open_files', '100000') }}
# The number of worker threads to start. These threads are used to manage
# return calls made from minions to the master. If the master seems to be
# running slowly, increase the number of threads. This setting can not be
# set lower than 3.
{{ get_config('worker_threads', '5') }}
# Set the ZeroMQ high water marks
# http://api.zeromq.org/3-2:zmq-setsockopt
# The publisher interface ZeroMQPubServerChannel
{{ get_config('pub_hwm', '1000') }}
# These two ZMQ HWM settings, salt_event_pub_hwm and event_publisher_pub_hwm
# are significant for masters with thousands of minions. When these are
# insufficiently high it will manifest in random responses missing in the CLI
# and even missing from the job cache. Masters that have fast CPUs and many
# cores with appropriate worker_threads will not need these set as high.
# On deployment with 8,000 minions, 2.4GHz CPUs, 24 cores, 32GiB memory has
# these settings:
#
# salt_event_pub_hwm: 128000
# event_publisher_pub_hwm: 64000
# ZMQ high-water-mark for SaltEvent pub socket
{{ get_config('salt_event_pub_hwm', '20000') }}
# ZMQ high-water-mark for EventPublisher pub socket
{{ get_config('event_publisher_pub_hwm', '10000') }}
2013-06-13 01:53:26 +02:00
##### Security settings #####
##########################################
# Enable "open mode", this mode still maintains encryption, but turns off
# authentication, this is only intended for highly secure environments or for
# the situation where your keys end up in a bad state. If you run in open mode
# you do so at your own risk!
2013-08-13 23:00:08 +02:00
{{ get_config('open_mode', 'False') }}
2013-06-13 01:53:26 +02:00
# Enable auto_accept, this setting will automatically accept all incoming
# public keys from the minions. Note that this is insecure.
2013-08-13 23:00:08 +02:00
{{ get_config('auto_accept', 'False') }}
2013-06-13 01:53:26 +02:00
# Time in minutes that a incoming public key with a matching name found in
# pki_dir/minion_autosign/keyid is automatically accepted. Expired autosign keys
# are removed when the master checks the minion_autosign directory.
# 0 equals no timeout
{{ get_config('autosign_timeout', '120') }}
# If the autosign_file is specified, incoming keys specified in the
# autosign_file will be automatically accepted. This is insecure. Regular
# expressions as well as globing lines are supported.
2013-08-13 23:00:08 +02:00
{{ get_config('autosign_file', '/etc/salt/autosign.conf') }}
2013-06-13 01:53:26 +02:00
# Works like autosign_file, but instead allows you to specify minion IDs for
# which keys will automatically be rejected. Will override both membership in
# the autosign_file and the auto_accept setting.
{{ get_config('autoreject_file', '/etc/salt/autoreject.conf') }}
# Enable permissive access to the salt keys. This allows you to run the
2013-06-13 01:53:26 +02:00
# master or minion as root, but have a non-root group be given access to
# your pki_dir. To make the access explicit, root must belong to the group
# you've given access to. This is potentially quite insecure. If an autosign_file
# is specified, enabling permissive_pki_access will allow group access to that
# specific file.
2013-08-13 23:00:08 +02:00
{{ get_config('permissive_pki_access', 'False') }}
2013-06-13 01:53:26 +02:00
# Allow users on the master access to execute specific commands on minions.
# This setting should be treated with care since it opens up execution
# capabilities to non root users. By default this capability is completely
# disabled.
{% if 'client_acl' in cfg_master -%}
client_acl:
{%- for name, user in cfg_master['client_acl']|dictsort %}
{{ name}}:
{%- for command in user %}
- {% raw %}'{% endraw %}{{ command }}{% raw %}'{% endraw %}
{%- endfor -%}
{%- endfor -%}
{% elif 'client_acl' in cfg_salt -%}
client_acl:
{%- for name, user in cfg_salt['client_acl']|dictsort %}
{{ name }}:
{%- for command in user %}
- {% raw %}'{% endraw %}{{ command }}{% raw %}'{% endraw %}
{%- endfor -%}
{%- endfor -%}
{% else -%}
#client_acl:
# larry:
# - test.ping
# - network.*
{%- endif %}
2013-06-13 01:53:26 +02:00
# Blacklist any of the following users or modules
#
# This example would blacklist all non sudo users, including root from
# running any commands. It would also blacklist any use of the "cmd"
# module. This is completely disabled by default.
{% if 'client_acl_blacklist' in cfg_master %}
client_acl_blacklist:
users:
{% for user in cfg_master['client_acl_blacklist'].get('users', []) %}
- {{ user }}
{% endfor %}
modules:
{% for mod in cfg_master['client_acl_blacklist'].get('modules', []) %}
- {{ mod }}
{% endfor %}
{% elif 'client_acl_blacklist' in cfg_salt %}
2013-08-13 23:00:08 +02:00
client_acl_blacklist:
users:
{% for user in cfg_salt['client_acl_blacklist'].get('users', []) %}
2013-08-13 23:00:08 +02:00
- {{ user }}
{% endfor %}
2013-08-13 23:00:08 +02:00
modules:
{% for mod in cfg_salt['client_acl_blacklist'].get('modules', []) %}
2013-08-13 23:00:08 +02:00
- {{ mod }}
{% endfor %}
{% else %}
#client_acl_blacklist:
# users:
# - root
# - '^(?!sudo_).*$' # all non sudo users
# modules:
# - cmd
{% endif %}
# Enforce client_acl & client_acl_blacklist when users have sudo
# access to the salt command.
{{ get_config('sudo_acl', 'False') }}
2013-06-13 01:53:26 +02:00
# The external auth system uses the Salt auth modules to authenticate and
2013-08-13 23:00:08 +02:00
# validate users to access areas of the Salt system.
#external_auth:
# pam:
# fred:
# - test.*
2013-08-13 23:00:08 +02:00
{{ get_config('external_auth', '{}') }}
2013-06-13 01:53:26 +02:00
# Time (in seconds) for a newly generated token to live. Default: 12 hours
2013-08-13 23:00:08 +02:00
{{ get_config('token_expire', '43200') }}
# Allow minions to push files to the master. This is disabled by default, for
# security purposes.
{{ get_config('file_recv', 'False') }}
2013-06-13 01:53:26 +02:00
# Set a hard-limit on the size of the files that can be pushed to the master.
# It will be interpreted as megabytes. Default: 100
{{ get_config('file_recv_max_size', '100') }}
# Signature verification on messages published from the master.
# This causes the master to cryptographically sign all messages published to its event
# bus, and minions then verify that signature before acting on the message.
#
# This is False by default.
#
# Note that to facilitate interoperability with masters and minions that are different
# versions, if sign_pub_messages is True but a message is received by a minion with
# no signature, it will still be accepted, and a warning message will be logged.
# Conversely, if sign_pub_messages is False, but a minion receives a signed
# message it will be accepted, the signature will not be checked, and a warning message
# will be logged. This behavior went away in Salt 2014.1.0 and these two situations
# will cause minion to throw an exception and drop the message.
{{ get_config('sign_pub_message', 'False') }}
# Sign the master auth-replies with a cryptographic signature of the masters public key.
# Please see the tutorial how to use these settings in the Multimaster-PKI with Failover Tutorial
2015-07-24 16:41:49 +02:00
{{ get_config('master_sign_pubkey', 'False') }}
# The customizable name of the signing-key-pair without suffix.
# master_sign_key_name: <filename_without_suffix>
{{ get_config('master_sign', '{}') }}
# The name of the file in the masters pki-directory that holds the pre-calculated
# signature of the masters public-key.
# master_pubkey_signature: <filename>
{{ get_config('master_pubkey_signature', '{}') }}
# Instead of computing the signature for each auth-reply, use a pre-calculated signature.
# The master_pubkey_signature must also be set for this.
{{ get_config('master_use_pubkey_signature', 'False') }}
# Rotate the salt-masters AES-key when a minion-public is deleted with salt-key.
# This is a very important security-setting. Disabling it will enable deleted minions to still
# listen in on the messages published by the salt-master.
# Do not disable this unless it is absolutely clear what this does.
{{ get_config('rotate_aes_key', 'True') }}
##### Salt-SSH Configuration #####
##########################################
# Pass in an alternative location for the salt-ssh roster file
{{ get_config('roster_file', '/etc/salt/roster') }}
# Pass in minion option overrides that will be inserted into the SHIM for
# salt-ssh calls. The local minion config is not used for salt-ssh. Can be
# overridden on a per-minion basis in the roster (`minion_opts`)
#ssh_minion_opts:
# gpg_keydir: /root/gpg
{{ get_config('ssh_minion_opts', '{}') }}
2015-07-24 16:41:49 +02:00
2013-06-13 01:53:26 +02:00
##### Master Module Management #####
##########################################
# Manage how master side modules are loaded.
2013-06-13 01:53:26 +02:00
# Add any additional locations to look for master runners:
2013-08-13 23:00:08 +02:00
{{ get_config('runner_dirs', '[]') }}
2013-06-13 01:53:26 +02:00
# Enable Cython for master side modules:
2013-08-13 23:00:08 +02:00
{{ get_config('cython_enable', 'False') }}
2013-06-13 01:53:26 +02:00
##### State System settings #####
##########################################
# The state system uses a "top" file to tell the minions what environment to
# use and what modules to use. The state_top file is defined relative to the
# root of the base environment as defined in "File Server settings" below.
2013-08-13 23:00:08 +02:00
{{ get_config('state_top', 'top.sls') }}
2013-06-13 01:53:26 +02:00
# The master_tops option replaces the external_nodes option by creating
# a plugable system for the generation of external top data. The external_nodes
# option is deprecated by the master_tops option.
#
2013-06-13 01:53:26 +02:00
# To gain the capabilities of the classic external_nodes system, use the
# following configuration:
# master_tops:
# ext_nodes: <Shell command which returns yaml>
#
#master_tops: {}
{% if 'master_tops' in cfg_master %}
master_tops:
{%- for master in cfg_master['master_tops'] -%}
{%- if cfg_master['master_tops'][master] is string %}
{{ master }}: {{ cfg_master['master_tops'][master] }}
{%- else %}
{{ master}}:
{%- for parameter in cfg_master['master_tops'][master] %}
{{ parameter }}: {{ cfg_master['master_tops'][master][parameter] }}
{%- endfor -%}
{%- endif -%}
{%- endfor %}
{% endif %}
2013-06-13 01:53:26 +02:00
# The external_nodes option allows Salt to gather data that would normally be
# placed in a top file. The external_nodes option is the executable that will
# return the ENC data. Remember that Salt will look for external nodes AND top
# files and combine the results if both are enabled!
2013-08-13 23:00:08 +02:00
{{ get_config('external_nodes', 'None') }}
2013-06-13 01:53:26 +02:00
# The renderer to use on the minions to render the state data
2013-08-13 23:00:08 +02:00
{{ get_config('renderer', 'yaml_jinja') }}
2013-06-13 01:53:26 +02:00
# The Jinja renderer can strip extra carriage returns and whitespace
# See http://jinja.pocoo.org/docs/api/#high-level-api
#
# If this is set to True the first newline after a Jinja block is removed
# (block, not variable tag!). Defaults to False, corresponds to the Jinja
# environment init variable "trim_blocks".
{{ get_config('jinja_trim_blocks', 'False') }}
# If this is set to True leading spaces and tabs are stripped from the start
# of a line to a block. Defaults to False, corresponds to the Jinja
# environment init variable "lstrip_blocks".
{{ get_config('jinja_lstrip_blocks', 'False') }}
2013-06-13 01:53:26 +02:00
# The failhard option tells the minions to stop immediately after the first
# failure detected in the state execution, defaults to False
2013-08-13 23:00:08 +02:00
{{ get_config('failhard', 'False') }}
2013-06-13 01:53:26 +02:00
# The state_verbose and state_output settings can be used to change the way
# state system data is printed to the display. By default all data is printed.
# The state_verbose setting can be set to True or False, when set to False
# all data that has a result of True and no changes will be suppressed.
2013-08-13 23:00:08 +02:00
{{ get_config('state_verbose', 'True') }}
2013-06-13 01:53:26 +02:00
# The state_output setting changes if the output is the full multi line
# output for each changed state if set to 'full', but if set to 'terse'
# the output will be shortened to a single line. If set to 'mixed', the output
# will be terse unless a state failed, in which case that output will be full.
# If set to 'changes', the output will be full unless the state didn't change.
2013-08-13 23:00:08 +02:00
{{ get_config('state_output', 'full') }}
2013-06-13 01:53:26 +02:00
# Automatically aggregate all states that have support for mod_aggregate by
# setting to 'True'. Or pass a list of state module names to automatically
# aggregate just those types.
#
# state_aggregate:
# - pkg
#
#state_aggregate: False
{{ get_config('state_aggregate', '{}') }}
# Send progress events as each function in a state run completes execution
# by setting to 'True'. Progress events are in the format
# 'salt/job/<JID>/prog/<MID>/<RUN NUM>'.
{{ get_config('state_events', 'False') }}
2013-06-13 01:53:26 +02:00
##### File Server settings #####
##########################################
# Salt runs a lightweight file server written in zeromq to deliver files to
# minions. This file server is built into the master daemon and does not
# require a dedicated port.
# The file server works on environments passed to the master, each environment
# can have multiple root directories, the subdirectories in the multiple file
# roots cannot match, otherwise the downloaded files will not be able to be
# reliably ensured. A base environment is required to house the top file.
# Example:
# file_roots:
# base:
# - /srv/salt/
# dev:
# - /srv/salt/dev/services
# - /srv/salt/dev/states
# prod:
# - /srv/salt/prod/services
# - /srv/salt/prod/states
#
{% if 'file_roots' in cfg_master -%}
{{ file_roots(cfg_master['file_roots']) }}
{%- elif 'file_roots' in cfg_salt -%}
{{ file_roots(cfg_salt['file_roots']) }}
{%- elif formulas|length -%}
{{ file_roots({'base': ['/srv/salt']}) }}
{%- else -%}
2013-06-13 01:53:26 +02:00
#file_roots:
# base:
# - /srv/salt
2013-08-13 23:00:08 +02:00
{%- endif %}
2013-06-13 01:53:26 +02:00
# When using multiple environments, each with their own top file, the
# default behaviour is an unordered merge. To prevent top files from
# being merged together and instead to only use the top file from the
# requested environment, set this value to 'same'.
{{ get_config('top_file_merging_stragety', 'merge') }}
# To specify the order in which environments are merged, set the ordering
# in the env_order option. Given a conflict, the last matching value will
# win.
{{ get_config('env_order', '["base", "dev", "prod"]') }}
# If top_file_merging_strategy is set to 'same' and an environment does not
# contain a top file, the top file in the environment specified by default_top
# will be used instead.
{{ get_config('default_top', 'base') }}
2013-06-13 01:53:26 +02:00
# The hash_type is the hash to use when discovering the hash of a file on
2013-08-13 23:00:08 +02:00
# the master server. The default is md5, but sha1, sha224, sha256, sha384
2013-06-13 01:53:26 +02:00
# and sha512 are also supported.
#
# Prior to changing this value, the master should be stopped and all Salt
# caches should be cleared.
2013-08-13 23:00:08 +02:00
{{ get_config('hash_type', 'md5') }}
2013-06-13 01:53:26 +02:00
# The buffer size in the file server can be adjusted here:
2013-08-13 23:00:08 +02:00
{{ get_config('file_buffer_size', '1048576') }}
2013-06-13 01:53:26 +02:00
# A regular expression (or a list of expressions) that will be matched
# against the file path before syncing the modules and states to the minions.
# This includes files affected by the file.recurse state.
# For example, if you manage your custom modules and states in subversion
# and don't want all the '.svn' folders and content synced to your minions,
# you could set this to '/\.svn($|/)'. By default nothing is ignored.
{% if 'file_ignore_regex' in cfg_master %}
2013-08-13 23:00:08 +02:00
file_ignore_regex:
{% for regex in cfg_master['file_ignore_regex'] %}
2013-08-13 23:00:08 +02:00
- {{ regex }}
{% endfor %}
{% elif 'file_ignore_regex' in cfg_salt %}
2013-08-13 23:00:08 +02:00
file_ignore_regex:
{% for regex in cfg_salt['file_ignore_regex'] %}
2013-08-13 23:00:08 +02:00
- {{ regex }}
{% endfor %}
{% else %}
2013-08-13 23:00:08 +02:00
#file_ignore_regex:
# - '/\.svn($|/)'
# - '/\.git($|/)'
{% endif %}
2013-06-13 01:53:26 +02:00
# A file glob (or list of file globs) that will be matched against the file
# path before syncing the modules and states to the minions. This is similar
# to file_ignore_regex above, but works on globs instead of regex. By default
# nothing is ignored.
{% if 'file_ignore_glob' in cfg_master %}
2013-08-13 23:00:08 +02:00
file_ignore_glob:
{% for glob in cfg_master['file_ignore_glob'] %}
2013-08-13 23:00:08 +02:00
- {{ glob }}
{% endfor %}
{% elif 'file_ignore_glob' in cfg_salt %}
2013-08-13 23:00:08 +02:00
file_ignore_glob:
{% for glob in cfg_salt['file_ignore_glob'] %}
2013-08-13 23:00:08 +02:00
- {{ glob }}
{% endfor %}
{% else %}
# file_ignore_glob:
2013-08-13 23:00:08 +02:00
# - '*.pyc'
# - '*/somefolder/*.bak'
# - '*.swp'
{% endif %}
2013-06-13 01:53:26 +02:00
# File Server Backend
#
2013-06-13 01:53:26 +02:00
# Salt supports a modular fileserver backend system, this system allows
# the salt master to link directly to third party systems to gather and
# manage the files available to minions. Multiple backends can be
# configured and will be searched for the requested file in the order in which
# they are defined here. The default setting only enables the standard backend
# "roots" which uses the "file_roots" option.
#fileserver_backend:
# - roots
#
2013-06-13 01:53:26 +02:00
# To use multiple backends list them in the order they are searched:
#fileserver_backend:
# - git
# - roots
{% if 'fileserver_backend' in cfg_master -%}
fileserver_backend:
{%- for backend in cfg_master['fileserver_backend'] %}
- {{ backend }}
{%- endfor -%}
{%- endif %}
# Uncomment the line below if you do not want the file_server to follow
# symlinks when walking the filesystem tree. This is set to True
# by default. Currently this only applies to the default roots
# fileserver_backend.
{{ get_config('fileserver_followsymlinks', 'False') }}
# Uncomment the line below if you do not want symlinks to be
# treated as the files they are pointing to. By default this is set to
# False. By uncommenting the line below, any detected symlink while listing
# files on the Master will not be returned to the Minion.
{{ get_config('fileserver_ignoresymlinks', 'True') }}
# By default, the Salt fileserver recurses fully into all defined environments
# to attempt to find files. To limit this behavior so that the fileserver only
# traverses directories with SLS files and special Salt directories like _modules,
# enable the option below. This might be useful for installations where a file root
# has a very large number of files and performance is impacted. Default is False.
{{ get_config('fileserver_limit_traversal', 'False') }}
# The fileserver can fire events off every time the fileserver is updated,
# these are disabled by default, but can be easily turned on by setting this
# flag to True
{{ get_config('fileserver_events', 'False') }}
# Git File Server Backend Configuration
#
# Gitfs can be provided by one of two python modules: GitPython or pygit2. If
# using pygit2, both libgit2 and git must also be installed.
{{ get_config('gitfs_provider', 'gitpython') }}
2013-06-13 01:53:26 +02:00
# When using the git fileserver backend at least one git remote needs to be
# defined. The user running the salt master will need read access to the repo.
#
2013-06-13 01:53:26 +02:00
# The repos will be searched in order to find the file requested by a client
# and the first repo to have the file will return it.
# When using the git backend branches and tags are translated into salt
# environments.
# Note: file:// repos will be treated as a remote, so refs you want used must
# exist in that repo as *local* refs.
{% if 'gitfs_remotes' in cfg_master -%}
gitfs_remotes:
{%- for remote in cfg_master['gitfs_remotes'] %}
{%- if remote is iterable and remote is not string %}
{%- for repo, children in remote.items() %}
- {{ repo }}:
{%- for child in children %}
{%- for key, value in child.items() %}
- {{ key }}: {{ value }}
{%- endfor -%}
{%- endfor -%}
{%- endfor -%}
{%- else %}
- {{ remote }}
{%- endif -%}
{%- endfor -%}
{%- endif %}
#gitfs_remotes:
# - git://github.com/saltstack/salt-states.git
# - file:///var/git/saltmaster
#
# The gitfs_ssl_verify option specifies whether to ignore ssl certificate
# errors when contacting the gitfs backend. You might want to set this to
# false if you're using a git backend that uses a self-signed certificate but
# keep in mind that setting this flag to anything other than the default of True
# is a security concern, you may want to try using the ssh transport.
{{ get_config('gitfs_ssl_verify', 'True') }}
# The gitfs_root option gives the ability to serve files from a subdirectory
# within the repository. The path is defined relative to the root of the
# repository and defaults to the repository root.
{{ get_config('gitfs_root', 'somefolder/otherfolder') }}
2013-06-13 01:53:26 +02:00
2015-12-11 13:42:16 +01:00
# The gitfs_env_whitelist and gitfs_env_blacklist parameters allow for greater
# control over which branches/tags are exposed as fileserver environments.
{% if 'gitfs_env_whitelist' in cfg_master -%}
gitfs_env_whitelist:
{%- for git_env in cfg_master['gitfs_env_whitelist'] %}
- {{ git_env }}
{%- endfor -%}
{% else -%}
# gitfs_env_whitelist:
# - base
# - v1.*
{% endif %}
{% if 'gitfs_env_blacklist' in cfg_master -%}
gitfs_env_blacklist:
{%- for git_env in cfg_master['gitfs_env_blacklist'] %}
- {{ git_env }}
{%- endfor -%}
{% else -%}
# gitfs_env_blacklist:
# - bug/*
# - feature/*
{% endif %}
2013-06-13 01:53:26 +02:00
##### Pillar settings #####
##########################################
# Salt Pillars allow for the building of global data that can be made selectively
# available to different minions based on minion grain filtering. The Salt
# Pillar is laid out in the same fashion as the file server, with environments,
# a top file and sls files. However, pillar data does not need to be in the
# highstate format, and is generally just key/value pairs.
{% if 'pillar_roots' in cfg_master -%}
2013-08-13 23:00:08 +02:00
pillar_roots:
{%- for name, roots in cfg_master['pillar_roots']|dictsort %}
2013-08-13 23:00:08 +02:00
{{ name }}:
{%- for dir in roots %}
- {{ dir }}
{%- endfor -%}
Fixed pillar_roots generation for salt-master. With a simple pillar like this:: $ sudo salt-call --config-dir /srv/etc/bootstrap --pillar-root /srv/pillar pillar.get salt:pillar_roots local: ---------- base: - /srv/pillar This was generated in /etc/salt/master.d/f_defaults.conf:: # highstate format, and is generally just key/value pairs. pillar_roots:base:- /srv/pillar # Resulting in parse errors by salt:: $ sudo salt '*' state.highstate [ERROR ] Error parsing configuration file: /etc/salt/master.d/f_defaults.conf - while scanning a simple key in "<string>", line 531, column 1: pillar_roots:base:- /srv/pillar ^ could not found expected ':' in "<string>", line 532, column 1: # ^ [ERROR ] Error parsing configuration file: /etc/salt/master.d/f_defaults.conf - while scanning a simple key in "<string>", line 531, column 1: pillar_roots:base:- /srv/pillar ^ could not found expected ':' in "<string>", line 532, column 1: # ^ This patch will fix it as such:: ID: salt-master Function: file.recurse Name: /etc/salt/master.d Result: True Comment: Recursively updated /etc/salt/master.d Started: 11:37:12.946823 Duration: 6255.296 ms Changes: ---------- /etc/salt/master.d/f_defaults.conf: ---------- diff: --- +++ @@ -528,7 +528,9 @@ # Pillar is laid out in the same fashion as the file server, with environments, # a top file and sls files. However, pillar data does not need to be in the # highstate format, and is generally just key/value pairs. -pillar_roots:base:- /srv/pillar +pillar_roots: + base: + - /srv/pillar # Resulting in:: # highstate format, and is generally just key/value pairs. pillar_roots: base: - /srv/pillar #
2015-08-06 11:35:20 +02:00
{%- endfor -%}
{% elif 'pillar_roots' in cfg_salt -%}
pillar_roots:
Fixed pillar_roots generation for salt-master. With a simple pillar like this:: $ sudo salt-call --config-dir /srv/etc/bootstrap --pillar-root /srv/pillar pillar.get salt:pillar_roots local: ---------- base: - /srv/pillar This was generated in /etc/salt/master.d/f_defaults.conf:: # highstate format, and is generally just key/value pairs. pillar_roots:base:- /srv/pillar # Resulting in parse errors by salt:: $ sudo salt '*' state.highstate [ERROR ] Error parsing configuration file: /etc/salt/master.d/f_defaults.conf - while scanning a simple key in "<string>", line 531, column 1: pillar_roots:base:- /srv/pillar ^ could not found expected ':' in "<string>", line 532, column 1: # ^ [ERROR ] Error parsing configuration file: /etc/salt/master.d/f_defaults.conf - while scanning a simple key in "<string>", line 531, column 1: pillar_roots:base:- /srv/pillar ^ could not found expected ':' in "<string>", line 532, column 1: # ^ This patch will fix it as such:: ID: salt-master Function: file.recurse Name: /etc/salt/master.d Result: True Comment: Recursively updated /etc/salt/master.d Started: 11:37:12.946823 Duration: 6255.296 ms Changes: ---------- /etc/salt/master.d/f_defaults.conf: ---------- diff: --- +++ @@ -528,7 +528,9 @@ # Pillar is laid out in the same fashion as the file server, with environments, # a top file and sls files. However, pillar data does not need to be in the # highstate format, and is generally just key/value pairs. -pillar_roots:base:- /srv/pillar +pillar_roots: + base: + - /srv/pillar # Resulting in:: # highstate format, and is generally just key/value pairs. pillar_roots: base: - /srv/pillar #
2015-08-06 11:35:20 +02:00
{%- for name, roots in cfg_salt['pillar_roots']|dictsort %}
{{ name }}:
Fixed pillar_roots generation for salt-master. With a simple pillar like this:: $ sudo salt-call --config-dir /srv/etc/bootstrap --pillar-root /srv/pillar pillar.get salt:pillar_roots local: ---------- base: - /srv/pillar This was generated in /etc/salt/master.d/f_defaults.conf:: # highstate format, and is generally just key/value pairs. pillar_roots:base:- /srv/pillar # Resulting in parse errors by salt:: $ sudo salt '*' state.highstate [ERROR ] Error parsing configuration file: /etc/salt/master.d/f_defaults.conf - while scanning a simple key in "<string>", line 531, column 1: pillar_roots:base:- /srv/pillar ^ could not found expected ':' in "<string>", line 532, column 1: # ^ [ERROR ] Error parsing configuration file: /etc/salt/master.d/f_defaults.conf - while scanning a simple key in "<string>", line 531, column 1: pillar_roots:base:- /srv/pillar ^ could not found expected ':' in "<string>", line 532, column 1: # ^ This patch will fix it as such:: ID: salt-master Function: file.recurse Name: /etc/salt/master.d Result: True Comment: Recursively updated /etc/salt/master.d Started: 11:37:12.946823 Duration: 6255.296 ms Changes: ---------- /etc/salt/master.d/f_defaults.conf: ---------- diff: --- +++ @@ -528,7 +528,9 @@ # Pillar is laid out in the same fashion as the file server, with environments, # a top file and sls files. However, pillar data does not need to be in the # highstate format, and is generally just key/value pairs. -pillar_roots:base:- /srv/pillar +pillar_roots: + base: + - /srv/pillar # Resulting in:: # highstate format, and is generally just key/value pairs. pillar_roots: base: - /srv/pillar #
2015-08-06 11:35:20 +02:00
{%- for dir in roots %}
- {{ dir }}
{%- endfor -%}
{%- endfor -%}
{%- else -%}
2013-06-13 01:53:26 +02:00
#pillar_roots:
# base:
# - /srv/pillar
2015-05-16 14:51:19 +02:00
{%- endif %}
{% if 'ext_pillar' in cfg_master %}
2013-08-13 23:00:08 +02:00
ext_pillar:
{%- for pillar in cfg_master['ext_pillar'] -%}
{%- for key in pillar -%}
{%- if pillar[key] is string %}
- {{ key }}: {{ pillar[key] }}
{%- elif pillar[key] is iterable and pillar[key] is not mapping %}
- {{ key }}:
{%- for parameter in pillar[key] %}
- {{ parameter }}
{%- endfor -%}
{%- elif pillar[key] is mapping and pillar[key] is not string %}
- {{ key }}:
{%- for parameter in pillar[key] %}
{{ parameter }}: {{pillar[key][parameter]}}
{%- endfor %}
{%- else %}
# Error in rendering {{ key }}, please read https://docs.saltstack.com/en/latest/topics/development/external_pillars.html#configuration
{% endif %}
{%- endfor -%}
{%- endfor %}
{% elif 'ext_pillar' in cfg_salt %}
2013-08-13 23:00:08 +02:00
ext_pillar:
{% for pillar in cfg_salt['ext_pillar'] %}
2013-08-27 17:33:06 +02:00
- {{ pillar.items()[0][0] }}: {{ pillar.items()[0][1] }}
{% endfor %}
2013-08-13 23:00:08 +02:00
{% else %}
#ext_pillar:
# - hiera: /etc/hiera.yaml
# - cmd_yaml: cat /etc/salt/yaml
{% endif %}
2013-06-13 01:53:26 +02:00
# The ext_pillar_first option allows for external pillar sources to populate
# before file system pillar. This allows for targeting file system pillar from
# ext_pillar.
{{ get_config('ext_pillar_first', 'False') }}
2013-06-13 01:53:26 +02:00
# The pillar_gitfs_ssl_verify option specifies whether to ignore ssl certificate
# errors when contacting the pillar gitfs backend. You might want to set this to
# false if you're using a git backend that uses a self-signed certificate but
# keep in mind that setting this flag to anything other than the default of True
# is a security concern, you may want to try using the ssh transport.
{{ get_config('pillar_gitfs_ssl_verify', 'True') }}
2013-06-13 01:53:26 +02:00
# The pillar_opts option adds the master configuration file data to a dict in
# the pillar called "master". This is used to set simple configurations in the
# master config file that can then be used on minions.
2013-08-13 23:00:08 +02:00
{{ get_config('pillar_opts', 'True') }}
2013-06-13 01:53:26 +02:00
# The pillar_safe_render_error option prevents the master from passing pillar
# render errors to the minion. This is set on by default because the error could
# contain templating data which would give that minion information it shouldn't
# have, like a password! When set true the error message will only show:
# Rendering SLS 'my.sls' failed. Please see master log for details.
{{ get_config('pillar_safe_render_error', 'True') }}
# The pillar_source_merging_strategy option allows you to configure merging strategy
# between different sources. It accepts four values: recurse, aggregate, overwrite,
# or smart. Recurse will merge recursively mapping of data. Aggregate instructs
# aggregation of elements between sources that use the #!yamlex renderer. Overwrite
# will verwrite elements according the order in which they are processed. This is
# behavior of the 2014.1 branch and earlier. Smart guesses the best strategy based
# on the "renderer" setting and is the default value.
{{ get_config('pillar_source_merging_strategy', 'smart') }}
2013-06-13 01:53:26 +02:00
# Recursively merge lists by aggregating them instead of replacing them.
{{ get_config('pillar_merge_lists', 'False') }}
2013-06-13 01:53:26 +02:00
##### Syndic settings #####
##########################################
# The Salt syndic is used to pass commands through a master from a higher
# master. Using the syndic is simple. If this is a master that will have
# syndic servers(s) below it, then set the "order_masters" setting to True.
#
# If this is a master that will be running a syndic daemon for passthrough, then
# the "syndic_master" setting needs to be set to the location of the master server
2013-06-13 01:53:26 +02:00
# to receive commands from.
# Set the order_masters setting to True if this master will command lower
# masters' syndic interfaces.
2013-08-13 23:00:08 +02:00
{{ get_config('order_masters', 'False') }}
2013-06-13 01:53:26 +02:00
# If this master will be running a salt syndic daemon, syndic_master tells
# this master where to receive commands from.
2013-08-13 23:00:08 +02:00
{{ get_config('syndic_master', 'masterofmaster') }}
# This is the 'ret_port' of the MasterOfMaster:
2013-08-13 23:00:08 +02:00
{{ get_config('syndic_master_port', '4506') }}
# PID file of the syndic daemon:
2013-08-13 23:00:08 +02:00
{{ get_config('syndic_pidfile', '/var/run/salt-syndic.pid') }}
2013-06-13 01:53:26 +02:00
# LOG file of the syndic daemon:
2013-08-13 23:00:08 +02:00
{{ get_config('syndic_log_file', 'syndic.log') }}
2013-06-13 01:53:26 +02:00
2013-06-13 01:53:26 +02:00
##### Peer Publish settings #####
##########################################
# Salt minions can send commands to other minions, but only if the minion is
# allowed to. By default "Peer Publication" is disabled, and when enabled it
# is enabled for specific minions and specific commands. This allows secure
# compartmentalization of commands based on individual minions.
# The configuration uses regular expressions to match minions and then a list
# of regular expressions to match functions. The following will allow the
# minion authenticated as foo.example.com to execute functions from the test
# and pkg modules.
#peer:
# foo.example.com:
# - test.*
# - pkg.*
2013-06-13 01:53:26 +02:00
#
# This will allow all minions to execute all commands:
#peer:
# .*:
# - .*
#
2013-06-13 01:53:26 +02:00
# This is not recommended, since it would allow anyone who gets root on any
# single minion to instantly have root on all of the minions!
{% if 'peer' in cfg_master %}
2013-08-13 23:00:08 +02:00
peer:
{% for name, roots in cfg_master['peer'].items() %}
2013-08-13 23:00:08 +02:00
{{ name }}:
{% for mod in roots %}
2013-08-13 23:00:08 +02:00
- {{ mod }}
{% endfor %}
{% endfor %}
{% elif 'peer' in cfg_salt %}
peer:
{% for name, roots in cfg_salt['peer'].items() %}
{{ name }}:
{% for mod in roots %}
- {{ mod }}
{% endfor %}
{% endfor %}
{% endif %}
2013-06-13 01:53:26 +02:00
# Minions can also be allowed to execute runners from the salt master.
# Since executing a runner from the minion could be considered a security risk,
# it needs to be enabled. This setting functions just like the peer setting
# except that it opens up runners instead of module functions.
#
# All peer runner support is turned off by default and must be enabled before
# using. This will enable all peer runners for all minions:
#peer_run:
# .*:
# - .*
2013-06-13 01:53:26 +02:00
#
# To enable just the manage.up runner for the minion foo.example.com:
#peer_run:
# foo.example.com:
# - manage.up
{% if 'peer_run' in cfg_master %}
2013-08-13 23:00:08 +02:00
peer_run:
{% for name, roots in cfg_master['peer_run'].items() %}
2013-08-13 23:00:08 +02:00
{{ name }}:
{% for mod in roots %}
2013-08-13 23:00:08 +02:00
- {{ mod }}
{% endfor %}
{% endfor %}
{% elif 'peer_run' in cfg_salt %}
peer_run:
{% for name, roots in cfg_salt['peer_run'].items() %}
{{ name }}:
{% for mod in roots %}
- {{ mod }}
{% endfor %}
{% endfor %}
{% endif %}
2013-06-13 01:53:26 +02:00
##### Mine settings #####
#####################################
# Restrict mine.get access from minions. By default any minion has a full access
# to get all mine data from master cache. In acl definion below, only pcre matches
# are allowed.
# mine_get:
# .*:
# - .*
#
# The example below enables minion foo.example.com to get 'network.interfaces' mine
# data only, minions web* to get all network.* and disk.* mine data and all other
# minions won't get any mine data.
2015-02-19 21:59:44 +01:00
{% if 'mine_get' in cfg_master -%}
mine_get:
{%- for minion, data in cfg_master['mine_get']|dictsort %}
{{ minion }}:
{%- for command in data %}
- {% raw %}'{% endraw %}{{ command }}{% raw %}'{% endraw %}
{%- endfor -%}
{%- endfor -%}
{% elif 'mine_get' in cfg_salt -%}
mine_get:
{%- for minion, data in cfg_salt['mine_get']|dictsort %}
{{ minion }}:
{%- for command in data %}
- {% raw %}'{% endraw %}{{ command }}{% raw %}'{% endraw %}
{%- endfor -%}
{%- endfor -%}
{% else -%}
# mine_get:
# foo.example.com:
# - network.interfaces
# web.*:
# - network.*
# - disk.*
2015-02-19 21:59:44 +01:00
{%- endif %}
2013-06-13 01:53:26 +02:00
##### Logging settings #####
##########################################
# The location of the master log file
# The master log can be sent to a regular file, local path name, or network
# location. Remote logging works best when configured to use rsyslogd(8) (e.g.:
# ``file:///dev/log``), with rsyslogd(8) configured for network logging. The URI
# format is: <file|udp|tcp>://<host|socketpath>:<port-if-required>/<log-facility>
#log_file: /var/log/salt/master
#log_file: file:///dev/log
#log_file: udp://loghost:10514
2013-08-13 23:00:08 +02:00
{{ get_config('log_file', '/var/log/salt/master') }}
{{ get_config('key_logfile', '/var/log/salt/key') }}
2013-06-13 01:53:26 +02:00
# The level of messages to send to the console.
# One of 'garbage', 'trace', 'debug', info', 'warning', 'error', 'critical'.
#
# The following log levels are considered INSECURE and may log sensitive data:
# ['garbage', 'trace', 'debug']
#
2013-08-13 23:00:08 +02:00
{{ get_config('log_level', 'warning') }}
2013-06-13 01:53:26 +02:00
# The level of messages to send to the log file.
# One of 'garbage', 'trace', 'debug', info', 'warning', 'error', 'critical'.
# If using 'log_granular_levels' this must be set to the highest desired level.
2013-08-13 23:00:08 +02:00
{{ get_config('log_level_logfile', 'warning') }}
2013-06-13 01:53:26 +02:00
# The date and time format used in log messages. Allowed date/time formating
# can be seen here: http://docs.python.org/library/time.html#time.strftime
2013-08-13 23:17:53 +02:00
{{ get_config('log_datefmt', "'%H:%M:%S'") }}
2013-08-13 23:00:08 +02:00
{{ get_config('log_datefmt_logfile', "'%Y-%m-%d %H:%M:%S'") }}
2013-06-13 01:53:26 +02:00
# The format of the console logging messages. Allowed formatting options can
# be seen here: http://docs.python.org/library/logging.html#logrecord-attributes
#
# Console log colors are specified by these additional formatters:
#
# %(colorlevel)s
# %(colorname)s
# %(colorprocess)s
# %(colormsg)s
#
# Since it is desirable to include the surrounding brackets, '[' and ']', in
# the coloring of the messages, these color formatters also include padding as
# well. Color LogRecord attributes are only available for console logging.
#
{{ get_config('log_fmt_console', "'%(colorlevel)s %(colormsg)s'") }}
2013-08-13 23:00:08 +02:00
{{ get_config('log_fmt_console', "'[%(levelname)-8s] %(message)s'") }}
2013-08-13 23:00:08 +02:00
{{ get_config('log_fmt_logfile', "'%(asctime)s,%(msecs)03.0f [%(name)-17s][%(levelname)-8s] %(message)s'") }}
2013-06-13 01:53:26 +02:00
# This can be used to control logging levels more specificically. This
# example sets the main salt library at the 'warning' level, but sets
# 'salt.modules' to log at the 'debug' level:
# log_granular_levels:
# 'salt': 'warning'
2013-06-13 01:53:26 +02:00
# 'salt.modules': 'debug'
#
{% if 'log_granular_levels' in cfg_master %}
2013-08-13 23:00:08 +02:00
log_granular_levels:
{% for name, lvl in cfg_master['log_granular_levels'].items() %}
2013-08-13 23:00:08 +02:00
{{ name }}: {{ lvl }}
{% endfor %}
{% elif 'log_granular_levels' in cfg_salt %}
log_granular_levels:
{% for name, lvl in cfg_salt['log_granular_levels'].items() %}
{{ name }}: {{ lvl }}
{% endfor %}
2013-08-13 23:00:08 +02:00
{% else %}
#log_granular_levels: {}
{% endif %}
2013-06-13 01:53:26 +02:00
##### Node Groups ######
2013-06-13 01:53:26 +02:00
##########################################
# Node groups allow for logical groupings of minion nodes. A group consists of a group
# name and a compound target.
#nodegroups:
# group1: 'L@foo.domain.com,bar.domain.com,baz.domain.com and bl*.domain.com'
# group2: 'G@os:Debian and foo.domain.com'
{% if 'nodegroups' in cfg_master %}
2013-08-13 23:00:08 +02:00
nodegroups:
{% for name, lvl in cfg_master['nodegroups'].items() %}
2013-08-13 23:00:08 +02:00
{{ name }}: {{ lvl }}
{% endfor %}
{% elif 'nodegroups' in cfg_salt %}
nodegroups:
{% for name, lvl in cfg_salt['nodegroups'].items() %}
{{ name }}: {{ lvl }}
{% endfor %}
{% endif %}
2013-06-13 01:53:26 +02:00
##### Range Cluster settings #####
##########################################
# The range server (and optional port) that serves your cluster information
# https://github.com/ytoolshed/range/wiki/%22yamlfile%22-module-file-spec
2013-06-13 01:53:26 +02:00
#
2013-08-13 23:00:08 +02:00
{{ get_config('range_server', 'range:80') }}
2013-06-13 01:53:26 +02:00
##### Windows Software Repo settings #####
###########################################
# Repo settings for 2015.8+ master used with 2015.8+ Windows minions
#
# Location of the repo on the master:
{{ get_config('winrepo_dir_ng', '/srv/salt/win/repo-ng') }}
# List of git repositories to include with the local repo:
{% if 'winrepo_remotes_ng' in cfg_master %}
winrepo_remotes_ng:
{% for repo in cfg_master['winrepo_remotes_ng'] %}
- {{ repo }}
{% endfor %}
{% elif 'winrepo_remotes_ng' in cfg_salt %}
winrepo_remotes_ng:
{% for repo in cfg_salt['winrepo_remotes_ng'] %}
- {{ repo }}
{% endfor %}
{% else %}
#winrepo_remotes_ng:
# - 'https://github.com/saltstack/salt-winrepo-ng.git'
{% endif %}
# Repo settings for 2015.8+ master used with pre-2015.8 Windows minions
#
# Location of the repo on the master:
{{ get_config('winrepo_dir', '/srv/salt/win/repo') }}
# Location of the master's repo cache file:
{{ get_config('winrepo_cachefile', 'winrepo.p') }}
# List of git repositories to include with the local repo:
{% if 'winrepo_remotes' in cfg_master %}
winrepo_remotes:
{% for repo in cfg_master['winrepo_remotes'] %}
- {{ repo }}
{% endfor %}
{% elif 'winrepo_remotes' in cfg_salt %}
winrepo_remotes:
{% for repo in cfg_salt['winrepo_remotes'] %}
- {{ repo }}
{% endfor %}
{% else %}
#winrepo_remotes:
# - 'https://github.com/saltstack/salt-winrepo.git'
{% endif %}
##### Windows Software Repo settings - Pre 2015.8 #####
########################################################
# Legacy repo settings for pre-2015.8 Windows minions.
#
# Location of the repo on the master:
2013-08-13 23:00:08 +02:00
{{ get_config('win_repo', '/srv/salt/win/repo') }}
2013-06-13 01:53:26 +02:00
# Location of the master's repo cache file:
2013-08-13 23:00:08 +02:00
{{ get_config('win_repo_mastercachefile', '/srv/salt/win/repo/winrepo.p') }}
2013-06-13 01:53:26 +02:00
# List of git repositories to include with the local repo:
{% if 'win_gitrepos' in cfg_master %}
2013-08-13 23:00:08 +02:00
win_gitrepos:
{% for repo in cfg_master['win_gitrepos'] %}
2013-08-13 23:00:08 +02:00
- {{ repo }}
{% endfor %}
{% elif 'win_gitrepos' in cfg_salt %}
2013-08-13 23:00:08 +02:00
win_gitrepos:
{% for repo in cfg_salt['win_gitrepos'] %}
2013-08-13 23:00:08 +02:00
- {{ repo }}
{% endfor %}
2013-08-13 23:00:08 +02:00
{% else %}
#winrepo_remotes:
# - 'https://github.com/saltstack/salt-winrepo.git'
2013-08-13 23:00:08 +02:00
{% endif %}
##### Returner settings ######
############################################
# Which returner(s) will be used for minion's result:
#return: mysql
{{ get_config('return', '')}}
###### Miscellaneous settings ######
############################################
# Default match type for filtering events tags: startswith, endswith, find, regex, fnmatch
{{ get_config('event_match_type', 'startswith') }}
{%- if 'halite' in cfg_master %}
##### Halite #####
##########################################
halite:
{%- for name, value in cfg_master['halite'].items() %}
{{ name }}: {{ value }}
{%- endfor %}
{%- endif %}
{%- if 'rest_cherrypy' in cfg_master %}
2014-08-23 05:57:21 +02:00
##### rest_cherrypy #####
##########################################
rest_cherrypy:
{%- for name, value in cfg_master['rest_cherrypy'].items() %}
2014-08-23 05:57:21 +02:00
{{ name }}: {{ value }}
{%- endfor %}
{%- endif %}
{%- if 'rest_tornado' in cfg_master %}
##### rest_tornado #####
###########################################
rest_tornado:
{%- for name, value in cfg_master['rest_tornado'].items() %}
{{ name }}: {{ value }}
{%- endfor %}
{%- endif %}
{%- if 'presence_events' in cfg_master %}
##### presence events #####
##########################################
{{ get_config('presence_events', 'False') }}
{%- endif %}
2016-01-13 14:04:22 +01:00
{%- if 'consul_config' in cfg_master %}
2016-01-13 14:04:22 +01:00
##### consul_config #####
##########################################
consul_config:
{%- for name, value in cfg_master['consul_config'].items() %}
2016-01-13 14:04:22 +01:00
{{ name }}: {{ value }}
{%- endfor %}
{%- endif %}