1========================= 2Salt 0.10.0 Release Notes 3========================= 4 5:release: 2012-06-16 6 70.10.0 has arrived! This release comes with MANY bug fixes, and new 8capabilities which greatly enhance performance and reliability. This 9release is primarily a bug fix release with many new tests and many repaired 10bugs. This release also introduces a few new key features which were brought 11in primarily to repair bugs and some limitations found in some of the 12components of the original architecture. 13 14Major Features 15============== 16 17Event System 18------------ 19 20The Salt Master now comes equipped with a new event system. This event system 21has replaced some of the back end of the Salt client and offers the beginning of 22a system which will make plugging external applications into Salt. The event 23system relies on a local ZeroMQ publish socket and other processes can connect 24to this socket and listen for events. The new events can be easily managed via 25Salt's event library. 26 27Unprivileged User Updates 28------------------------- 29 30Some enhancements have been added to Salt for running as a user other than 31root. These new additions should make switching the user that the Salt Master 32is running as very painless, simply change the ``user`` option in the master 33configuration and restart the master, Salt will take care of all of the 34particulars for you. 35 36Peer Runner Execution 37--------------------- 38 39Salt has long had the peer communication system used to allow minions to send 40commands via the salt master. 0.10.0 adds a new capability here, now the 41master can be configured to allow for minions to execute Salt runners via 42the ``peer_run`` option in the salt master configuration. 43 44YAML Parsing Updates 45-------------------- 46 47In the past the YAML parser for sls files would return the incorrect numbers 48when the file mode was set with a preceding 0. The YAML parser used in Salt 49has been modified to no longer convert these number into octal but to keep 50them as the correct value so that sls files can be a little cleaner to write. 51 52State Call Data Files 53===================== 54 55It was requested that the minion keep a local cache of the most recent executed 56state run. This has been added and now with state runs the data is stored in a 57msgpack file in the minion's cachedir. 58 59Turning Off the Job Cache 60========================= 61 62A new option has been added to the master configuration file. In previous 63releases the Salt client would look over the Salt job cache to read in 64the minion return data. With the addition of the event system the Salt client 65can now watch for events directly from the master worker processes. 66 67This means that the job cache is no longer a hard requirement. Keep in mind 68though, that turning off the job cache means that historic job execution data 69cannot be retrieved. 70 71Test Updates 72============ 73 74Minion Swarms Are Faster 75------------------------ 76 77To continue our efforts with testing Salt's ability to scale the minionswarm 78script has been updated. The minionswarm can now start up minions much faster 79than it could before and comes with a new feature allowing modules to be 80disabled, thus lowering the minion's footprint when making a swarm. These new 81updates have allows us to test 82 83.. code-block:: bash 84 85 # python minionswarm.py -m 20 --master salt-master 86 87 88Many Fixes 89========== 90 91To get a good idea for the number of bugfixes this release offers take a look 92at the closed tickets for 0.10.0, this is a very substantial update: 93 94https://github.com/saltstack/salt/issues?milestone=12&state=closed 95 96Master and Minion Stability Fixes 97--------------------------------- 98 99As Salt deployments grow new ways to break Salt are discovered. 0.10.0 comes 100with a number of fixes for the minions and master greatly improving Salt 101stability.