Salt Air 4 – Introducing Salt OverState and Salt Reactor

December 14, 2012 - Thomas Hatch
This image has an empty alt attribute; its file name is Salt_Air.width-800.png

Salt releases version 0.11.0 which includes a new versioning system, Salt OverState, Salt Reactor, module context, multiple package management and search. Watch the full Salt Air 4 episode on Salt OverState and Salt Reactor below!

“It’s time for the fourth installment of Salt Air. We’ve got a lot of exciting news and fun things to talk about today. We’re going to spend a lot of time talking about the new release that we just cut this morning. We’re going to talk about some changes that we’ve have in the versioning system. Let’s get to it. We’re going to be talking about in Salt Air, the latest release of salt 0.11.0. We’re going to talk about why it is not 0.10.6 and what the new versioning system is going to be looking like in Salt. We’re also going to talk a little bit about the old version versioning system or rather I shouldn’t say the old versioning system, we’re talking about the overall versioning system that we’re using inside of Salt for Salt projects. 0.11.0 I’m really excited about this release, granted i’m excited about every release. I put a lot of work into these, as do most of you. We’ve got a couple of features that we’re going to talk about in here, particularly the overstate, I’ve mentioned the overstate before in a few emails and discussions, but the overstate is a mechanism that allows you to roll through state runs on multiple minions all orchestrated from the master in a very clean way. We’re going to talk about the new context system that’s available inside of the modules. We talked about reactors last week, so this is just big hurrah, we actually have reactors now. I shouldn’t say last week, I bombed and didn’t do a Salt Air last week. I apologize I was in meetings all day. We’re also going to be talking about multiple package management. Multiple package management is a really exciting feature that’s going to enable you to dramatically speed up a lot of your state runs. We’re going to talk about the new search system or the bones of the new search system.”

“The overstate, the idea behind the over state is that we’ve got, almost always, many many many minions out there that were communicating with. It would make more sense if we were able to orchestrate the rollout of the state system from the perspective of an infrastructure or a cloud or whatever you call it. Take it from that perspective instead of from the perspective of individual systems going one at a time. That’s what the over state is. The over state allows you to write an SLS file that defines what systems are going to be executing their high state or individual SLS files and in what order they’re going to execute. It also allows you to specify that this group of systems should only run if the previous group ran without any errors. It makes it very easy to say, alright i’ve got an infrastructure and maybe i’m going to roll up dates across all of my web servers. We can have an over state in place that says, I’m going to roll out updates on five at a time and any wherein this upgrade path if something fails we can just stop and cut the cord and stop rolling out potential breakages to more systems. The way the overstate works is that you go in and you define group names and then under those group names you can specify targets so the normal way that we specify into minions and then you have an option to either specify to run state at high state on those minions or too sort to run a specific set of SLS files. Then you can also use a require statement in here to require another group.” – Thomas Hatch

Drive IT security into the 21st century with SaltStack. Your solution to orchestration and automation that remediates security issues in minutes. Check out the new Salt OverState and Salt Reactor video!

Watch Salt Air on: YouTube

Listen to Salt Air on: SoundCloud | Spotify | iTunes