Salt Air 9 – Tom’s vision for Salt as a complete infrastructure controller

February 1, 2013 - Thomas Hatch
This image has an empty alt attribute; its file name is Salt_Air.width-800.png

Legacy systems and configuration management software products don’t meet the needs of today’s dynamic and heterogeneous infrastructures. Salt is a complete infrastructure controller that is much more than just configuration management. Salt was built to be flexible, simple, very pluggable, and to provide a state and flow automation platform for any computing system. In this episode, Tom goes into detail about the core philosophies behind the Salt vision and the infrastructure controller.

“Welcome to Salt Air. I’m really excited about what we’re going to be talking about in Salt Air this week because this is something that’s been weighing heavily on my mind recently. One of the problems that we’ve run into with Salt is that it’s clear that a lot of people really like getting involved. They really like getting on board on Salt. They like the fact that Salt is easy to get up and going and easy to learn the basics. There’s a lot about the vision of Salt, there’s a lot about the ideas behind Salt, that we just haven’t covered. Things that I don’t think I’ve been talking about enough, things that have enabled Salt to become what it is and really defines the long-term direction in the long term goals of the Salt project and everything that we’re making with it. This presentation of Salt Air is going to be focused on the vision of Salt. It’s going to be focused on the ideas behind Salt, the concepts behind Salt, and what it is that we’re trying to make in the long run.”

‘Let me do a recursive screen share here and dive into our presentation. The most important aspect of Salt is something that I felt this little phrase quantifies very well “All your base are belong to YOU” but those of you who have seen, of course, the the joke online “All your base are belong to us”, the idea behind Salt is that I felt very strongly that existing tools out there were still too regimented. They were still too focused on defining certain aspects of your infrastructure and not meeting the needs of dynamic infrastructures. That was one of the core principles behind Salt, was to make something that didn’t run into hiccups in highly dynamic infrastructures but was able to meet the needs of classical or more regimented infrastructures. What’s important I think and what’s going on in the infrastructure world today is that a lot more of technology is leaning against this concept of the cloud and computations happening in data centers. What we’re putting in the hands of people are powerful thin clients. Devices that can do things in a powerful way but that are in other respects very very thin and relatively disposable. Which puts more and more and more weight on backend infrastructures. One of the goals of Salt is that, these infrastructures are going to be dramatically different overtime, these infrastructures are going to have very specific needs based on what it is that they’re managing based on the types of data that they’re managing based on the types of services that they’re managing. Then the fact that that with cloud architectures and virtualization architectures and many of these concepts of anonymous infrastructure management and resource management translating into non virtualized infrastructure. There’s so many different ideas out there. The goal was solved was that it can manage these scenarios without putting any extra constraint on the people that are administering these environments or on the architecture of these environments…” – Thomas Hatch

Learn more about the ultimate infrastructure controller here.

Watch Salt Air on: YouTube

Listen to Salt Air on: SoundCloud | Spotify | iTunes