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
#
9 vuotta sitten 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
#
9 vuotta sitten 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
#
9 vuotta sitten |
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874875876877878879880881882883884885886887888889890891892893894895896897898899900901902903904905906907908909910911912913914915916917918919920921922923924925926927928929930931932933934935936937938939940941942943944945946947948949950951952953954955956957958959960961962963964965966967968969970971972973974975976977978979980981982983984985986987988989990991992 |
- # This file managed by Salt, do not edit by hand!!
- # Based on salt version 2014.7 default config
- {% set reserved_keys = ['master', 'minion', 'cloud', 'salt_cloud_certs'] -%}
- {% set cfg_salt = pillar.get('salt', {}) -%}
- {% set cfg_master = cfg_salt.get('master', {}) -%}
- {%- 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] }}
- {%- else -%}
- #{{ configname }}: {{ default_value }}
- {%- endif -%}
- {%- endmacro -%}
- {%- from 'salt/formulas.jinja' import file_roots, formulas with context -%}
- ##### Primary configuration settings #####
- ##########################################
- # This configuration file is used to manage the behavior of the Salt Master
- # Values that are commented out but have no space after the comment are
- # defaults that need not be set in the config. If there is a space after the
- # comment that the value is presented as an example and is not the default.
-
- # 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).
- {{ get_config('default_include', 'master.d/*.conf') }}
-
- # The address of the interface to bind to:
- {{ 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: '::'")
- {{ get_config('ipv6', 'False') }}
-
- # The tcp port used by the publisher:
- {{ get_config('publish_port', '4505') }}
-
- # 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.
- {{ get_config('user', 'root') }}
-
- # 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.
- {{ get_config('worker_threads', '5') }}
-
- # The port used by the communication interface. The ret (return) port is the
- # interface used for the file server, authentication, job returns, etc.
- {{ get_config('ret_port', '4506') }}
-
- # Specify the location of the daemon process ID file:
- {{ get_config('pidfile', '/var/run/salt-master.pid') }}
-
- # The root directory prepended to these options: pki_dir, cachedir,
- # sock_dir, log_file, autosign_file, autoreject_file, extension_modules,
- # key_logfile, pidfile:
- {{ get_config('root_dir', '/') }}
-
- # Directory used to store public key data:
- {{ get_config('pki_dir', '/etc/salt/pki/master') }}
-
- # Directory to store job and cache data:
- {{ get_config('cachedir', '/var/cache/salt/master') }}
-
- # 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>') }}
-
- # Verify and set permissions on configuration directories at startup:
- {{ get_config('verify_env', 'True') }}
-
- # Set the number of hours to keep old job information in the job cache:
- {{ get_config('keep_jobs', '24') }}
-
- # Set the default timeout for the salt command and api. The default is 5
- # seconds.
- {{ get_config('timeout', '5') }}
-
- # The loop_interval option controls the seconds for the master's maintenance
- # process check cycle. This process updates file server backends, cleans the
- # job cache and executes the scheduler.
- {{ get_config('loop_interval', '60') }}
-
- # Set the default outputter used by the salt command. The default is "nested".
- {{ get_config('output', 'nested') }}
-
- # 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.
- {{ get_config('color', 'True') }}
-
- # 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:
- {{ get_config('sock_dir', '/var/run/salt/master') }}
-
- # 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
- # 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.
- {{ get_config('job_cache', 'True') }}
-
- # Cache minion grains and pillar data in the cachedir.
- {{ get_config('minion_data_cache', 'True') }}
-
- # 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') }}
-
- # 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.
- #
- # Include a config file from some other path:
- # include: /etc/salt/extra_config
- #
- # Include config from several files and directories:
- # include:
- # - /etc/salt/extra_config
- {{ get_config('include', '[]') }}
-
- ##### 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!
- {{ get_config('open_mode', 'False') }}
-
- # Enable auto_accept, this setting will automatically accept all incoming
- # public keys from the minions. Note that this is insecure.
- {{ get_config('auto_accept', 'False') }}
-
- # 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.
- {{ get_config('autosign_file', '/etc/salt/autosign.conf') }}
-
- # 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
- # 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.
- {{ get_config('permissive_pki_access', 'False') }}
-
- # 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.
- #client_acl:
- # larry:
- # - test.ping
- # - network.*
- {% 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 %}
-
- # 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 %}
- client_acl_blacklist:
- users:
- {% for user in cfg_salt['client_acl_blacklist'].get('users', []) %}
- - {{ user }}
- {% endfor %}
- modules:
- {% for mod in cfg_salt['client_acl_blacklist'].get('modules', []) %}
- - {{ 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') }}
-
- # The external auth system uses the Salt auth modules to authenticate and
- # validate users to access areas of the Salt system.
- #external_auth:
- # pam:
- # fred:
- # - test.*
- {{ get_config('external_auth', '{}') }}
-
- # Time (in seconds) for a newly generated token to live. Default: 12 hours
- {{ 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') }}
-
- # 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') }}
-
-
- {{ get_config('master_sign_pubkey', 'False') }}
-
-
- ##### Master Module Management #####
- ##########################################
- # Manage how master side modules are loaded.
-
- # Add any additional locations to look for master runners:
- {{ get_config('runner_dirs', '[]') }}
-
- # Enable Cython for master side modules:
- {{ get_config('cython_enable', 'False') }}
-
-
- ##### 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.
- {{ get_config('state_top', 'top.sls') }}
-
- # 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.
- #
- # To gain the capabilities of the classic external_nodes system, use the
- # following configuration:
- # master_tops:
- # ext_nodes: <Shell command which returns yaml>
- #
- {{ get_config('master_tops', '{}') }}
-
- # 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!
- {{ get_config('external_nodes', 'None') }}
-
- # The renderer to use on the minions to render the state data
- {{ get_config('renderer', 'yaml_jinja') }}
-
- # 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') }}
-
- # The failhard option tells the minions to stop immediately after the first
- # failure detected in the state execution, defaults to False
- {{ get_config('failhard', 'False') }}
-
- # 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.
- {{ get_config('state_verbose', 'True') }}
-
- # 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.
- {{ get_config('state_output', 'full') }}
-
- # 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
-
- ##### 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 -%}
- #file_roots:
- # base:
- # - /srv/salt
- {%- endif %}
-
- # The hash_type is the hash to use when discovering the hash of a file on
- # the master server. The default is md5, but sha1, sha224, sha256, sha384
- # and sha512 are also supported.
- #
- # Prior to changing this value, the master should be stopped and all Salt
- # caches should be cleared.
- {{ get_config('hash_type', 'md5') }}
-
- # The buffer size in the file server can be adjusted here:
- {{ get_config('file_buffer_size', '1048576') }}
-
- # 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 %}
- file_ignore_regex:
- {% for regex in cfg_master['file_ignore_regex'] %}
- - {{ regex }}
- {% endfor %}
- {% elif 'file_ignore_regex' in cfg_salt %}
- file_ignore_regex:
- {% for regex in cfg_salt['file_ignore_regex'] %}
- - {{ regex }}
- {% endfor %}
- {% else %}
- #file_ignore_regex:
- # - '/\.svn($|/)'
- # - '/\.git($|/)'
- {% endif %}
-
- # 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 %}
- file_ignore_glob:
- {% for glob in cfg_master['file_ignore_glob'] %}
- - {{ glob }}
- {% endfor %}
- {% elif 'file_ignore_glob' in cfg_salt %}
- file_ignore_glob:
- {% for glob in cfg_salt['file_ignore_glob'] %}
- - {{ glob }}
- {% endfor %}
- {% else %}
- # file_ignore_glob:
- # - '*.pyc'
- # - '*/somefolder/*.bak'
- # - '*.swp'
- {% endif %}
-
- # File Server Backend
- #
- # 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
- #
- # 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') }}
- #
- # 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.
- #
- # 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') }}
-
-
- ##### 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 -%}
- pillar_roots:
- {%- for name, roots in cfg_master['pillar_roots']|dictsort %}
- {{ name }}:
- {%- for dir in roots %}
- - {{ dir }}
- {%- endfor -%}
- {%- endfor -%}
- {% elif 'pillar_roots' in cfg_salt -%}
- pillar_roots:
- {%- for name, roots in cfg_salt['pillar_roots']|dictsort %}
- {{ name }}:
- {%- for dir in roots %}
- - {{ dir }}
- {%- endfor -%}
- {%- endfor -%}
- {%- else -%}
- #pillar_roots:
- # base:
- # - /srv/pillar
- {%- endif %}
- #
- {% if 'ext_pillar' in cfg_master %}
- ext_pillar:
- {% for pillar in cfg_master['ext_pillar'] %}
- - {{ pillar.items()[0][0] }}: {{ pillar.items()[0][1] }}
- {% endfor %}
- {% elif 'ext_pillar' in cfg_salt %}
- ext_pillar:
- {% for pillar in cfg_salt['ext_pillar'] %}
- - {{ pillar.items()[0][0] }}: {{ pillar.items()[0][1] }}
- {% endfor %}
- {% else %}
- #ext_pillar:
- # - hiera: /etc/hiera.yaml
- # - cmd_yaml: cat /etc/salt/yaml
- {% endif %}
-
- # 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') }}
-
- # 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') }}
-
- # 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.
- {{ get_config('pillar_opts', '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') }}
-
- ##### 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 set the "order_masters" setting to True, if this
- # is a master that will be running a syndic daemon for passthrough the
- # "syndic_master" setting needs to be set to the location of the master server
- # to receive commands from.
-
- # Set the order_masters setting to True if this master will command lower
- # masters' syndic interfaces.
- {{ get_config('order_masters', 'False') }}
-
- # If this master will be running a salt syndic daemon, syndic_master tells
- # this master where to receive commands from.
- {{ get_config('syndic_master', 'masterofmaster') }}
-
- # This is the 'ret_port' of the MasterOfMaster:
- {{ get_config('syndic_master_port', '4506') }}
-
- # PID file of the syndic daemon:
- {{ get_config('syndic_pidfile', '/var/run/salt-syndic.pid') }}
-
- # LOG file of the syndic daemon:
- {{ get_config('syndic_log_file', 'syndic.log') }}
-
- ##### 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.*
- #
- # This will allow all minions to execute all commands:
- #peer:
- # .*:
- # - .*
- #
- # 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 %}
- peer:
- {% for name, roots in cfg_master['peer'].items() %}
- {{ name }}:
- {% for mod in roots %}
- - {{ 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 %}
-
- # 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:
- # .*:
- # - .*
- #
- # 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 %}
- peer_run:
- {% for name, roots in cfg_master['peer_run'].items() %}
- {{ name }}:
- {% for mod in roots %}
- - {{ 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 %}
-
-
- ##### 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.
- {% 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.*
- {%- endif %}
-
-
- ##### 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
-
- {{ get_config('log_file', '/var/log/salt/master') }}
- {{ get_config('key_logfile', '/var/log/salt/key') }}
-
- # The level of messages to send to the console.
- # One of 'garbage', 'trace', 'debug', info', 'warning', 'error', 'critical'.
- {{ get_config('log_level', 'warning') }}
-
- # The level of messages to send to the log file.
- # One of 'garbage', 'trace', 'debug', info', 'warning', 'error', 'critical'.
- {{ get_config('log_level_logfile', 'warning') }}
-
- # 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
- {{ get_config('log_datefmt', "'%H:%M:%S'") }}
- {{ get_config('log_datefmt_logfile', "'%Y-%m-%d %H:%M:%S'") }}
-
- # The format of the console logging messages. Allowed formatting options can
- # be seen here: http://docs.python.org/library/logging.html#logrecord-attributes
- {{ get_config('log_fmt_console', "'[%(levelname)-8s] %(message)s'") }}
- {{ get_config('log_fmt_logfile', "'%(asctime)s,%(msecs)03.0f [%(name)-17s][%(levelname)-8s] %(message)s'") }}
-
- # 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'
- # 'salt.modules': 'debug'
- #
- {% if 'log_granular_levels' in cfg_master %}
- log_granular_levels:
- {% for name, lvl in cfg_master['log_granular_levels'].items() %}
- {{ 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 %}
- {% else %}
- #log_granular_levels: {}
- {% endif %}
-
-
- ##### Node Groups #####
- ##########################################
- # 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 %}
- nodegroups:
- {% for name, lvl in cfg_master['nodegroups'].items() %}
- {{ name }}: {{ lvl }}
- {% endfor %}
- {% elif 'nodegroups' in cfg_salt %}
- nodegroups:
- {% for name, lvl in cfg_salt['nodegroups'].items() %}
- {{ name }}: {{ lvl }}
- {% endfor %}
- {% endif %}
-
-
- ##### 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
- #
- {{ get_config('range_server', 'range:80') }}
-
- ##### Windows Software Repo settings #####
- ##############################################
- # Location of the repo on the master:
- {{ get_config('win_repo', '/srv/salt/win/repo') }}
-
- # Location of the master's repo cache file:
- {{ get_config('win_repo_mastercachefile', '/srv/salt/win/repo/winrepo.p') }}
-
- # List of git repositories to include with the local repo:
- {% if 'win_gitrepos' in cfg_master %}
- win_gitrepos:
- {% for repo in cfg_master['win_gitrepos'] %}
- - {{ repo }}
- {% endfor %}
- {% elif 'win_gitrepos' in cfg_salt %}
- win_gitrepos:
- {% for repo in cfg_salt['win_gitrepos'] %}
- - {{ repo }}
- {% endfor %}
- {% else %}
- #win_gitrepos:
- # - 'https://github.com/saltstack/salt-winrepo.git'
- {% endif %}
-
- ##### Returner settings ######
- ############################################
- # Which returner(s) will be used for minion's result:
- #return: mysql
-
- {% 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 %}
- ##### rest_cherrypy #####
- ##########################################
- rest_cherrypy:
- {% for name, value in cfg_master['rest_cherrypy'].items() %}
- {{ 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 %}
|