Not all of the options for the master and Minion end profiles are described here, but rather the usual ones.
I. Description ofMaster Common configuration options
Cat/etc/salt/master
Interface : Specify the address of bind (default is 0.0.0.0)
Publish_port : Specify a publishing port (default is 4505)
Ret_port : Specifies the result return port, corresponding to the Master_port in the Minion configuration file (default = 4506)
User : Specifies the running user of the master process and, if adjusted, needs to adjust permissions for some directories (default is root)
-
timeout Span style= "font-family: ' The song body '; background: #FFFF00;" >※ : Specify timeout time, if minion large scale or poor network condition, it is recommended to increase this value (default 5s General 5 seconds is not enough, the recommended amount of increase.
Keep_jobs : By default,Minion returns the execution result to master,and master caches it to the local cachedir directory, which specifies how long the cache To view the results of the previous execution, it consumes disk space (default is 24h)
Job_cache : If master caches execution results, if it is large (over the platform), it is recommended to use another way to store jobs, turn off this option (by default , True )
File_recv : Whether to allow Minion to transfer files to master (false by default )
File_roots: Specifies the file server directory, by default:
File_roots:
Base
-/srv/salt
Pillar_roots:
Base
-/srv/pillar
Log_level : Execution log level, supported log levels are garbage,trace,debug,info,warning,error ,critical(default = "warning")
max_open_files: 100000 : Default value is 100000. The maximum file descriptor that can be opened.
worker_threads: 5 : The default value is 5, when the cluster size becomes larger, you can increase this value appropriately
Second, Minion common configuration options Description
Cat/etc/salt/minion
Master : Specify Master host (default is salt)
Master_port : Specifies which port of authentication and execution results are sent to master, corresponding to the Ret_port in the master configuration file (default is 4506)
ID : Specifies the identity of the Minion, andthe salt internally uses the ID as the identity (default is the host name)
User : Specifies the user who runs minion. Because the installation package, the start service and other operations require a privileged user, it is recommended to use root(default is root)
Cache_jobs :Minion whether to cache execution results (default = False)
Backup_mode : Specifies the backup destination if the file changes when the file operation (file.managed or File.recurese) occurs. The currently valid value is Minion, backed up in the cachedir/file_backups directory, named with the original file name and timestamp (default = disabled)
providers : Specifies the module corresponding to the providers, as in the Rhel series,pkg corresponding to the providers is Yumpkg5
renderer : Specifies the renderer in the Configuration management system (default:yaml_jinja)
file_client : Specify where the file client should go ( remote or local) to find files by default(remote is the default )
loglevel : Specify the log level (default is warning)
tcp_keepalive :minion keepalive check with master ,zeromq3 keepalive bug in the following version Causes the link exception to occur in some cases after minion cannot re-connect master. Recommended if conditional upgrade to ZEROMQ3 or later (default true)
This article is from the "Gdlwolf blog" blog, make sure to keep this source http://gdlwolf.blog.51cto.com/343866/1786912
Saltstack-gdlwolf Self-study summary fourth: Salt-master and salt-minion configuration file options Description