debian/0000755000000000000000000000000012005462413007163 5ustar debian/salt-common.dirs0000644000000000000000000000003611775345104012310 0ustar /var/log/salt /var/cache/salt debian/salt-syndic.install0000644000000000000000000000010311775345104013011 0ustar usr/bin/salt-syndic debian/salt-syndic.service /lib/systemd/system debian/pydist-overrides0000644000000000000000000000003511775345104012432 0ustar msgpack_python msgpack-pythondebian/salt-minion.init0000644000000000000000000000507011775345104012316 0ustar #!/bin/sh ### BEGIN INIT INFO # Provides: salt-minion # Required-Start: $remote_fs $network # Required-Stop: $remote_fs $network # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: salt minion control daemon # Description: This is a daemon that controls the salt minions ### END INIT INFO # Author: Michael Prokop PATH=/sbin:/usr/sbin:/bin:/usr/bin DESC="salt minion control daemon" NAME=salt-minion DAEMON=/usr/bin/salt-minion DAEMON_ARGS="" PIDFILE=/var/run/$NAME.pid SCRIPTNAME=/etc/init.d/$NAME # Exit if the package is not installed [ -x "$DAEMON" ] || exit 0 # Read configuration variable file if it is present [ -r /etc/default/$NAME ] && . /etc/default/$NAME . /lib/init/vars.sh . /lib/lsb/init-functions do_start() { pid=$(pidofproc -p $PIDFILE $DAEMON) if [ -n "$pid" ] ; then log_begin_msg "$DESC already running." log_end_msg 0 exit 0 fi log_daemon_msg "Starting salt-minion daemon: " start-stop-daemon --start --quiet --background --make-pidfile --pidfile $PIDFILE --exec $DAEMON -- $DAEMON_ARGS log_end_msg $? } do_stop() { log_begin_msg "Stopping $DESC ..." start-stop-daemon --stop --quiet --oknodo --pidfile $PIDFILE RC=$? [ $RC -eq 0 ] && rm -f $PIDFILE log_end_msg $RC } case "$1" in start) [ "$VERBOSE" != no ] && log_daemon_msg "Starting $DESC" "$NAME" do_start case "$?" in 0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;; 2) [ "$VERBOSE" != no ] && log_end_msg 1 ;; esac ;; stop) [ "$VERBOSE" != no ] && log_daemon_msg "Stopping $DESC" "$NAME" do_stop case "$?" in 0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;; 2) [ "$VERBOSE" != no ] && log_end_msg 1 ;; esac ;; status) status_of_proc "$DAEMON" "$NAME" && exit 0 || exit $? ;; #reload) # not implemented #;; restart|force-reload) log_daemon_msg "Restarting $DESC" "$NAME" do_stop case "$?" in 0|1) do_start case "$?" in 0) log_end_msg 0 ;; 1) log_end_msg 1 ;; # Old process is still running *) log_end_msg 1 ;; # Failed to start esac ;; *) # Failed to stop log_end_msg 1 ;; esac ;; *) echo "Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}" >&2 exit 3 ;; esac exit 0 debian/watch0000644000000000000000000000014111775345104010222 0ustar version=3 https://github.com/saltstack/salt/downloads /downloads/saltstack/salt/salt-(.*).tar.gz debian/salt-minion.install0000644000000000000000000000015511775345104013020 0ustar debian/minion /etc/salt usr/bin/salt-minion usr/bin/salt-call debian/salt-minion.service /lib/systemd/system debian/salt-syndic.service0000644000000000000000000000025111775345104013007 0ustar [Unit] Description=The Salt Master Server After=syslog.target network.target [Service] Type=simple ExecStart=/usr/bin/salt-syndic [Install] WantedBy=multi-user.target debian/source/0000755000000000000000000000000011775345104010475 5ustar debian/source/options0000644000000000000000000000006311775345104012112 0ustar extend-diff-ignore=.*|tests/integration/files/file/debian/source/format0000644000000000000000000000001411775345104011703 0ustar 3.0 (quilt) debian/salt-common.manpages0000644000000000000000000000001711771175062013141 0ustar doc/man/salt.7 debian/pyversions0000644000000000000000000000000511775345104011334 0ustar 2.6- debian/salt-common.logrotate0000644000000000000000000000016511775345104013352 0ustar /var/log/salt/master /var/log/salt/minion /var/log/salt/*.log { weekly missingok rotate 7 compress notifempty } debian/gbp.conf0000644000000000000000000000011111775345104010605 0ustar [DEFAULT] debian-branch = debian pristine-tar = True force-create = True debian/salt-master.service0000644000000000000000000000025111775345104013011 0ustar [Unit] Description=The Salt Master Server After=syslog.target network.target [Service] Type=simple ExecStart=/usr/bin/salt-master [Install] WantedBy=multi-user.target debian/copyright0000644000000000000000000000354311775345104011135 0ustar Format: http://dep.debian.net/deps/dep5 Upstream-Name: salt Upstream-Contact: salt-users@googlegroups.com Source: https://github.com/saltstack/salt Files: * Copyright: 2012 Thomas S Hatch License: Apache-2.0 Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at . http://www.apache.org/licenses/LICENSE-2.0 . Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. . On Debian systems, the full text of the Apache Licens, Version 2.0 can be found in the file `/usr/share/common-licenses/Apache-2.0'. Files: debian/* Copyright: 2012 Michael Prokop 2012 Christian Hofstaedtler 2012 Ulrich Dangel 2012 Corey Quinn 2011 Aaron Toponce License: Apache-2.0 Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at . http://www.apache.org/licenses/LICENSE-2.0 . Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. . On Debian systems, the full text of the Apache Licens, Version 2.0 can be found in the file `/usr/share/common-licenses/Apache-2.0'. debian/changelog0000644000000000000000000000355112005462265011046 0ustar salt (0.10.1-3) unstable; urgency=low * [efbd4a8] Change uploaders email address for Ulrich Dangel * [442ead1] Recommends dmidecode instead of Depend to support non-x86 systems. -- Ulrich Dangel Mon, 30 Jul 2012 12:40:53 +0200 salt (0.10.1-2) unstable; urgency=low * [bda6011] Add dmidecode to depends for salt-minion. (Closes: #680410) * [ad4786e] Depend on the same salt version * [671c2c3] Depend on debhelper version fixing #577040 -- Ulrich Dangel Mon, 09 Jul 2012 23:15:27 +0200 salt (0.10.1-1) unstable; urgency=low [ Ulrich Dangel ] * [f1d627c] Always recreate orig.tar.gz with git-buildpackage [ Michael Prokop ] * Merge new upstream release * [ee1806a] Add python-augeas to suggests of salt-minion -- Michael Prokop Fri, 22 Jun 2012 18:56:02 +0200 salt (0.10.0-1) unstable; urgency=low [ Ulrich Dangel ] * Merge new upstream release * [bd10385] Change debian/source/format to quilt * [ba60137] Add ignore options * [54e70de] Copy service files from rpm package * [1d21548] Update install files * [c2737c9] Update pyversions file to use 2.6 * [573b27a] Update salt-common.install to install complete python package * [9b739f5] Update debian/rules to use python support and update build dependencies * [bf51e1c] Provide pydists-overrides for msgpack-python * [4bbd2bf] Add dependency to python-pkg-resources for salt-{minion,master,syndic} * [ad8f712] Update config files to latest version [ Jeroen Dekkers ] * [9ae1aa5] Unapply patches from source * [933c1ee] Add debian/gbp.conf * [be9529b] Add >= 1.0 to python-sphinx build-depend -- Michael Prokop Wed, 20 Jun 2012 22:39:40 +0200 salt (0.9.9-1) unstable; urgency=low * Initial release. [Closes: #643789] -- Michael Prokop Thu, 14 Jun 2012 18:39:17 +0200 debian/salt-syndic.upstart0000644000000000000000000000035711771175062013060 0ustar description "salt-syndic" start on (net-device-up and local-filesystems and runlevel [2345]) stop on runlevel [!2345] respawn limit 10 5 script exec /usr/bin/python /usr/bin/salt-syndic > /dev/null 2>&1 end script debian/rules0000755000000000000000000000107011775345104010253 0ustar #!/usr/bin/make -f #export DH_VERBOSE=1 include /usr/share/python/python.mk %: dh $@ --with python2 override_dh_auto_build: dh_auto_build make -C doc html JS_FILES = searchtools doctools sidebar jquery underscore override_dh_installdocs: dh_installdocs # Remove embedded copies of javascript libs for f in $(JS_FILES) ; do \ cd debian/salt-doc/usr/share/doc/salt/html/_static/ \ && rm $${f}.js \ && ln -s ../../../../javascript/sphinxdoc/1.0/$${f}.js . \ && cd $(CURDIR) ; \ done ; override_dh_auto_clean: make -C doc clean dh_auto_clean debian/salt-minion.manpages0000644000000000000000000000005211771175062013141 0ustar doc/man/salt-call.1 doc/man/salt-minion.1 debian/salt-doc.doc-base0000644000000000000000000000047311775345104012306 0ustar Document: salt-doc Title: Welcome to Salt! Author: Thomas S. Hatch Abstract: This documention provides details about Salt. Salt is a remote execution and configuration management tool. Section: System/Administration Format: HTML Index: /usr/share/doc/salt/html/index.html Files: /usr/share/doc/salt/html/*/*.html debian/salt-common.install0000644000000000000000000000001111775345104013006 0ustar usr/lib/ debian/salt-minion.upstart0000644000000000000000000000035711771175062013060 0ustar description "salt-minion" start on (net-device-up and local-filesystems and runlevel [2345]) stop on runlevel [!2345] respawn limit 10 5 script exec /usr/bin/python /usr/bin/salt-minion > /dev/null 2>&1 end script debian/salt-master.init0000644000000000000000000000503611775345104012322 0ustar #!/bin/sh ### BEGIN INIT INFO # Provides: salt-master # Required-Start: $remote_fs $network # Required-Stop: $remote_fs $network # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: salt master control daemon # Description: This is a daemon that controls the salt minions ### END INIT INFO # Author: Michael Prokop PATH=/sbin:/usr/sbin:/bin:/usr/bin DESC="salt master control daemon" NAME=salt-master DAEMON=/usr/bin/salt-master DAEMON_ARGS="-d" PIDFILE=/var/run/$NAME.pid SCRIPTNAME=/etc/init.d/$NAME # Exit if the package is not installed [ -x "$DAEMON" ] || exit 0 # Read configuration variable file if it is present [ -r /etc/default/$NAME ] && . /etc/default/$NAME . /lib/init/vars.sh . /lib/lsb/init-functions do_start() { pid=$(pidofproc -p $PIDFILE $DAEMON) if [ -n "$pid" ] ; then log_begin_msg "$DESC already running." log_end_msg 0 exit 0 fi log_daemon_msg "Starting salt-master daemon: " start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- $DAEMON_ARGS log_end_msg $? } do_stop() { log_begin_msg "Stopping $DESC ..." start-stop-daemon --stop --quiet --oknodo --pidfile $PIDFILE RC=$? [ $RC -eq 0 ] && rm -f $PIDFILE log_end_msg $RC } case "$1" in start) [ "$VERBOSE" != no ] && log_daemon_msg "Starting $DESC" "$NAME" do_start case "$?" in 0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;; 2) [ "$VERBOSE" != no ] && log_end_msg 1 ;; esac ;; stop) [ "$VERBOSE" != no ] && log_daemon_msg "Stopping $DESC" "$NAME" do_stop case "$?" in 0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;; 2) [ "$VERBOSE" != no ] && log_end_msg 1 ;; esac ;; status) status_of_proc "$DAEMON" "$NAME" && exit 0 || exit $? ;; #reload) # not implemented #;; restart|force-reload) log_daemon_msg "Restarting $DESC" "$NAME" do_stop case "$?" in 0|1) do_start case "$?" in 0) log_end_msg 0 ;; 1) log_end_msg 1 ;; # Old process is still running *) log_end_msg 1 ;; # Failed to start esac ;; *) # Failed to stop log_end_msg 1 ;; esac ;; *) echo "Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}" >&2 exit 3 ;; esac exit 0 debian/salt-minion.service0000644000000000000000000000024211775345104013007 0ustar [Unit] Description=The Salt Minion After=syslog.target network.target [Service] Type=simple ExecStart=/usr/bin/salt-minion [Install] WantedBy=multi-user.target debian/salt-master.install0000644000000000000000000000023211775345104013016 0ustar debian/master /etc/salt usr/bin/salt-master usr/bin/salt-cp usr/bin/salt-run usr/bin/salt-key usr/bin/salt debian/salt-master.service /lib/systemd/system debian/salt-master.manpages0000644000000000000000000000013511771175062013145 0ustar doc/man/salt.1 doc/man/salt-cp.1 doc/man/salt-key.1 doc/man/salt-master.1 doc/man/salt-run.1 debian/salt-syndic.init0000644000000000000000000000503611775345104012320 0ustar #!/bin/sh ### BEGIN INIT INFO # Provides: salt-syndic # Required-Start: $remote_fs $network # Required-Stop: $remote_fs $network # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: salt syndic control daemon # Description: This is a daemon that controls the salt minions ### END INIT INFO # Author: Michael Prokop PATH=/sbin:/usr/sbin:/bin:/usr/bin DESC="salt syndic control daemon" NAME=salt-syndic DAEMON=/usr/bin/salt-syndic DAEMON_ARGS="-d" PIDFILE=/var/run/$NAME.pid SCRIPTNAME=/etc/init.d/$NAME # Exit if the package is not installed [ -x "$DAEMON" ] || exit 0 # Read configuration variable file if it is present [ -r /etc/default/$NAME ] && . /etc/default/$NAME . /lib/init/vars.sh . /lib/lsb/init-functions do_start() { pid=$(pidofproc -p $PIDFILE $DAEMON) if [ -n "$pid" ] ; then log_begin_msg "$DESC already running." log_end_msg 0 exit 0 fi log_daemon_msg "Starting salt-syndic daemon: " start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- $DAEMON_ARGS log_end_msg $? } do_stop() { log_begin_msg "Stopping $DESC ..." start-stop-daemon --stop --quiet --oknodo --pidfile $PIDFILE RC=$? [ $RC -eq 0 ] && rm -f $PIDFILE log_end_msg $RC } case "$1" in start) [ "$VERBOSE" != no ] && log_daemon_msg "Starting $DESC" "$NAME" do_start case "$?" in 0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;; 2) [ "$VERBOSE" != no ] && log_end_msg 1 ;; esac ;; stop) [ "$VERBOSE" != no ] && log_daemon_msg "Stopping $DESC" "$NAME" do_stop case "$?" in 0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;; 2) [ "$VERBOSE" != no ] && log_end_msg 1 ;; esac ;; status) status_of_proc "$DAEMON" "$NAME" && exit 0 || exit $? ;; #reload) # not implemented #;; restart|force-reload) log_daemon_msg "Restarting $DESC" "$NAME" do_stop case "$?" in 0|1) do_start case "$?" in 0) log_end_msg 0 ;; 1) log_end_msg 1 ;; # Old process is still running *) log_end_msg 1 ;; # Failed to start esac ;; *) # Failed to stop log_end_msg 1 ;; esac ;; *) echo "Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}" >&2 exit 3 ;; esac exit 0 debian/minion0000644000000000000000000002022611775345104010413 0ustar ##### Primary configuration settings ##### ########################################## # Set the location of the salt master server, if the master server cannot be # resolved, then the minion will fail to start. #master: salt # Set the port used by the master reply and authentication server #master_port: 4506 # The user to run salt #user: root # The root directory prepended to these options: pki_dir, cachedir, log_file. #root_dir: / # The directory to store the pki information in #pki_dir: /etc/salt/pki # Explicitly declare the id for this minion to use, if left commented the id # will be the hostname as returned by the python call: socket.getfqdn() # Since salt uses detached ids it is possible to run multiple minions on the # same machine but with different ids, this can be useful for salt compute # clusters. #id: # Append a domain to a hostname in the event that it does not exist. This is # useful for systems where socket.getfqdn() does not actually result in a # FQDN (for instance, Solaris). #append_domain: # If the connection to the server is interrupted, the minion will # attempt to reconnect. sub_timeout allows you to control the rate # of reconnection attempts (in seconds). To disable reconnects, set # this value to 0. #sub_timeout: 60 # Where cache data goes #cachedir: /var/cache/salt # The minion can locally cache the return data from jobs sent to it, this # can be a good way to keep track of jobs the minion has executed # (on the minion side). By default this feature is disabled, to enable # set cache_jobs to True #cache_jobs: False # When waiting for a master to accept the minion's public key, salt will # continuously attempt to reconnect until successful. This is the time, in # seconds, between those reconnection attempts. #acceptance_wait_time = 10 # When healing a dns_check is run, this is to make sure that the originally # resolved dns has not changed, if this is something that does not happen in # your environment then set this value to False. #dns_check: True ##### Minion module management ##### ########################################## # Disable specific modules. This allows the admin to limit the level of # access the master has to the minion #disable_modules: [cmd,test] #disable_returners: [] # # Modules can be loaded from arbitrary paths. This enables the easy deployment # of third party modules. Modules for returners and minions can be loaded. # Specify a list of extra directories to search for minion modules and # returners. These paths must be fully qualified! #module_dirs: [] #returner_dirs: [] #states_dirs: [] #render_dirs: [] # # A module provider can be statically overwritten or extended for the minion # via the providers option, in this case the default module will be # overwritten by the specified module. In this example the pkg module will # be provided by the yumpkg5 module instead of the system default. # # providers: # pkg: yumpkg5 # # Enable Cython modules searching and loading. (Default: False) #cython_enable: False ##### State Management Settings ##### ########################################### # The state management system executes all of the state templates on the minion # to enable more granular control of system state management. The type of # template and serialization used for state management needs to be configured # on the minion, the default renderer is yaml_jinja. This is a yaml file # rendered from a jinja template, the available options are: # yaml_jinja # yaml_mako # json_jinja # json_mako # #renderer: yaml_jinja # # state_verbose allows for the data returned from the minion to be more # verbose. Normally only states that fail or states that have changes are # returned, but setting state_verbose to True will return all states that # were checked #state_verbose: False # # autoload_dynamic_modules Turns on automatic loading of modules found in the # environments on the master. This is turned on by default, to turn of # autoloading modules when states run set this value to False #autoload_dynamic_modules: True # # clean_dynamic_modules keeps the dynamic modules on the minion in sync with # the dynamic modules on the master, this means that if a dynamic module is # not on the master it will be deleted from the minion. By default this is # enabled and can be disabled by changing this value to False #clean_dynamic_modules: True # # Normally the minion is not isolated to any single environment on the master # when running states, but the environment can be isolated on the minion side # by statically setting it. Remember that the recommended way to manage # environments is to isolate via the top file. #environment: None # # If using the local file directory, then the state top file name needs to be # defined, by default this is top.sls. #state_top: top.sls ##### File Directory Settings ##### ########################################## # The Salt Minion can redirect all file server operations to a local directory, # this allows for the same state tree that is on the master to be used if # copied completely onto the minion. This is a literal copy of the settings on # the master but used to reference a local directory on the minion. # Set the file client, the client defaults to looking on the master server for # files, but can be directed to look at the local file directory setting # defined below by setting it to local. #file_client: remote # The file directory works on environments passed to the minion, 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 # # Default: #file_roots: # base: # - /srv/salt # The hash_type is the hash to use when discovering the hash of a file in # the minion directory, the default is md5, but sha1, sha224, sha256, sha384 # and sha512 are also supported. #hash_type: md5 # The Salt pillar is searched for locally if file_client is set to local. If # this is the case, and pillar data is defined, then the pillar_roots need to # also be configured on the minion: #pillar_roots: # base: # - /srv/pillar ###### 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! #open_mode: False ###### Thread settings ##### ########################################### # Disable multiprocessing support, by default when a minion receives a # publication a new process is spawned and the command is executed therein. #multiprocessing: True ###### Logging settings ##### ########################################### # The location of the minion log file #log_file: /var/log/salt/minion # # The level of messages to send to the log file. # One of 'info', 'quiet', 'critical', 'error', 'debug', 'warning'. # Default: 'warning' #log_level: warning # # Logger levels can be used to tweak specific loggers logging levels. # For example, if you want to have the salt library at the 'warning' level, # but you still wish to have 'salt.modules' at the 'debug' level: # log_granular_levels: { # 'salt': 'warning', # 'salt.modules': 'debug' # } # #log_granular_levels: {} ###### Module configuration ##### ########################################### # Salt allows for modules to be passed arbitrary configuration data, any data # passed here in valid yaml format will be passed on to the salt minion modules # for use. It is STRONGLY recommended that a naming convention be used in which # the module name is followed by a . and then the value. Also, all top level # data must be applied via the yaml dict construct, some examples: # # A simple value for the test module: #test.foo: foo # # A list for the test module: #test.bar: [baz,quo] # # A dict for the test module: #test.baz: {spam: sausage, cheese: bread} debian/salt-doc.install0000644000000000000000000000005411775345104012272 0ustar doc/_build/html/* /usr/share/doc/salt/html/ debian/control0000644000000000000000000001313612005416752010577 0ustar Source: salt Section: admin Priority: optional Maintainer: Michael Prokop Uploaders: Christian Hofstaedtler , Ulrich Dangel DM-Upload-Allowed: yes Build-Depends: debhelper (>= 9.20120410~), cython, libzmq-dev (>= 2.1.9), python | python-all | python-dev | python-all-dev, python-crypto, python-jinja2, python-m2crypto, python-setuptools, python-sphinx (>= 1.0), python-yaml, python-zmq (>= 2.1.9) Standards-Version: 3.9.3 Homepage: http://saltstack.org/ Package: salt-common Architecture: all Depends: ${python:Depends}, ${misc:Depends}, ${shlibs:Depends}, msgpack-python, python, python-crypto, python-jinja2, python-m2crypto, python-yaml, python-zmq (>= 2.1.9) Description: shared libraries that salt requires for all packages salt is a powerful remote execution manager that can be used to administer servers in a fast and efficient way. . It allows commands to be executed across large groups of servers. This means systems can be easily managed, but data can also be easily gathered. Quick introspection into running systems becomes a reality. . Remote execution is usually used to set up a certain state on a remote system. Salt addresses this problem as well, the salt state system uses salt state files to define the state a server needs to be in. . Between the remote execution system, and state management Salt addresses the backbone of cloud and data center management. . This particular package provides shared libraries that salt-master, salt-minion, and salt-syndic require to function. Package: salt-master Architecture: all Depends: ${misc:Depends}, python, python-pkg-resources, salt-common (= ${source:Version}) Description: remote manager to administer servers via salt salt is a powerful remote execution manager that can be used to administer servers in a fast and efficient way. . It allows commands to be executed across large groups of servers. This means systems can be easily managed, but data can also be easily gathered. Quick introspection into running systems becomes a reality. . Remote execution is usually used to set up a certain state on a remote system. Salt addresses this problem as well, the salt state system uses salt state files to define the state a server needs to be in. . Between the remote execution system, and state management Salt addresses the backbone of cloud and data center management. . This particular package provides the salt controller. Package: salt-minion Architecture: all Depends: ${misc:Depends}, python, python-pkg-resources, salt-common (= ${source:Version}) Recommends: dmidecode Suggests: python-augeas Description: client package for salt, the distributed remote execution system salt is a powerful remote execution manager that can be used to administer servers in a fast and efficient way. . It allows commands to be executed across large groups of servers. This means systems can be easily managed, but data can also be easily gathered. Quick introspection into running systems becomes a reality. . Remote execution is usually used to set up a certain state on a remote system. Salt addresses this problem as well, the salt state system uses salt state files to define the state a server needs to be in. . Between the remote execution system, and state management Salt addresses the backbone of cloud and data center management. . This particular package provides the worker / agent for salt. Package: salt-syndic Architecture: all Depends: ${misc:Depends}, python, python-pkg-resources, salt-master (= ${source:Version}) Description: master-of-masters for salt, the distributed remote execution system salt is a powerful remote execution manager that can be used to administer servers in a fast and efficient way. . It allows commands to be executed across large groups of servers. This means systems can be easily managed, but data can also be easily gathered. Quick introspection into running systems becomes a reality. . Remote execution is usually used to set up a certain state on a remote system. Salt addresses this problem as well, the salt state system uses salt state files to define the state a server needs to be in. . Between the remote execution system, and state management Salt addresses the backbone of cloud and data center management. . This particular package provides the master of masters for salt - it enables the management of multiple masters at a time. Package: salt-doc Architecture: all Section: doc Depends: ${misc:Depends}, libjs-sphinxdoc Description: additional documentation for salt, the distributed remote execution system salt is a powerful remote execution manager that can be used to administer servers in a fast and efficient way. . It allows commands to be executed across large groups of servers. This means systems can be easily managed, but data can also be easily gathered. Quick introspection into running systems becomes a reality. . Remote execution is usually used to set up a certain state on a remote system. Salt addresses this problem as well, the salt state system uses salt state files to define the state a server needs to be in. . Between the remote execution system, and state management Salt addresses the backbone of cloud and data center management. . This particular package provides the HTML documentation for salt. debian/salt-syndic.manpages0000644000000000000000000000002611771175062013142 0ustar doc/man/salt-syndic.1 debian/compat0000644000000000000000000000000211771175062010373 0ustar 8 debian/master0000644000000000000000000002230411775345104010414 0ustar ##### Primary configuration settings ##### ########################################## # The address of the interface to bind to #interface: 0.0.0.0 # The port used by the publisher #publish_port: 4505 # The user to run salt #user: root # 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 #worker_threads: 5 # The port used by the communication interface #ret_port: 4506 # The root directory prepended to these options: pki_dir, cachedir, # sock_dir, log_file. #root_dir: / # Directory used to store public key data #pki_dir: /etc/salt/pki # Directory to store job and cache data #cachedir: /var/cache/salt # Set the number of hours to keep old job information #keep_jobs: 24 # Set the default timeout for the salt command and api, the default is 5 # seconds #timeout: 5 # Set the directory used to hold unix sockets #sock_dir: /tmp/salt-unix # 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. # #job_cache: True # Set the acceptance level for serialization of messages. This should only be # set if the master is newer than 0.9.5 and the minion are older. This option # allows a 0.9.5 and newer master to communicate with minions 0.9.4 and # earlier. It is not recommended to keep this setting on if the minions are # all 0.9.5 or higher, as leaving pickle as the serialization medium is slow # and opens up security risks # #serial: msgpack ##### 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! #open_mode: False # Enable auto_accept, this setting will automatically accept all incoming # public keys from the minions. Note that this is insecure. #auto_accept: False ##### Master Module Management ##### ########################################## # Manage how master side modules are loaded # # Add any additional locations to look for master runners #runner_dirs: [] # #Enable Cython for master side modules #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. #state_top: top.sls # # 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! #external_nodes: None # # The renderer to use on the minions to render the state data #renderer: yaml_jinja # # The failhard option tells the minions to stop immediately after the first # failure detected in the state execution, defaults to False #failhard: 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 # # Default: #file_roots: # base: # - /srv/salt # 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. #hash_type: md5 # The buffer size in the file server can be adjusted here: #file_buffer_size: 1048576 # Pillar Configurations: # The Salt Pillar, is a system that allows for the building of global data # that is refined based on minion. Basically, the pillar creates data that # can be generated to be specific based on the grains of the minion. Pillar # is laid out in the same fashion as the file server, with environments, a top # file and sls files. The difference is that the data does not need to be # in the highstate format, and is generally just key/value pairs. # #pillar_roots: # base: # - /srv/pillar # #ext_pillar: # - hiera: /etc/hiera.yaml # - cmd: cat /etc/salt/yaml # ##### 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. #order_masters: False # # If this master will be running a salt syndic daemon, syndic_master tells # this master where to receive commands from. #syndic_master: masterofmaster ##### 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! # # 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 # ##### Cluster settings ##### ########################################## # Salt supports automatic clustering, salt creates a single ip address which # is shared among the individual salt components using ucarp. The private key # and all of the minion keys are maintained across the defined cluster masters. # The failover service is automatically managed via these settings # List the identifiers for the other cluster masters in this manner: # [saltmaster-01.foo.com,saltmaster-02.foo.com,saltmaster-03.foo.com] # The members of this master array must be running as salt minions to # facilitate the distribution of cluster information #cluster_masters: [] # The cluster modes are "paranoid" and "full" # paranoid will only distribute the accepted minion public keys. # full will also distribute the master private key. #cluster_mode: paranoid ##### Logging settings ##### ########################################## # The location of the master log file #log_file: /var/log/salt/master # # The level of messages to send to the log file. # One of 'info', 'quiet', 'critical', 'error', 'debug', 'warning'. # Default: 'warning' #log_level: warning # # Logger levels can be used to tweak specific loggers logging levels. # For example, if you want to have the salt library at the 'warning' level, # but you still wish to have 'salt.modules' at the 'debug' level: # log_granular_levels: # 'salt': 'warning', # 'salt.modules': 'debug' # #log_granular_levels: {} ##### 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' ##### Range Cluster settings ##### ########################################## # The range server (and optional port) that # serves your cluster information #range_server: range:80 debian/salt-master.upstart0000644000000000000000000000030011771175062013046 0ustar description "salt-master" start on (net-device-up and local-filesystems and runlevel [2345]) stop on runlevel [!2345] expect daemon respawn exec /usr/bin/salt-master -d