SaltStack Enterprise Architecture
SaltStack Enterprise was created to make the power of Salt orchestration and automation available to the entire IT organization. What’s more SaltStack Enterprise is designed to amplify the ability of every IT employee to help better manage and secure digital business. Watch this episode of Salt Air to learn more about the SaltStack Enterprise architecture including the Salt automation engine, the SaltStack operations framework, the SaltStack command and control console, and pluggable solutions for ITOps, NetOps, and SecOps use cases.
“Welcome to another episode of salt air. My name is Tom Hatch I am the creator of Salt and the CTO of SaltStack. Today, I want to talk a little bit about the SaltStack enterprise architecture. A lot of people don’t understand or they’re not aware of some of the enterprise offerings that SaltStack has put together. We spent a considerable amount of time working with customers working with open source users of Salt to try and understand what it is that they really wanted on top of Salt. Then spend a lot of time making it, so we were able to expose those interfaces in a really good and consistent way. A lot of what we see in SaltStack Enterprise foundation-ally is taking concepts that many of our larger and more sophisticated open-source users have built on their own, combining those concepts, and then offering them to a wide array of customers and users. When we look at SaltStack Enterprise what we have is the normal Salt architecture that a lot of people are probably familiar with. With the master and then a collection of minions that are all tied into that master or many masters. Some think Enterprise sits above multiple masters and those masters tie up into the SaltStack enterprise system in similar way to how the minions tie up to the master, so that we’re able to maintain a consistent continual architecture. What we’re looking at is also the fact that the SaltStack Enterprise system, it has all of its interfaces communicating over HTTP, restful endpoints, and WebSockets. The SaltStack Enterprise can be scaled out and loaded up behind a web balancer and so it’s easy for SaltStack Enterprise to be able to deal with a large scale that multiple systems and larger infrastructures need to be able to work with. SaltStack Enterprise also comes with Postgres database. That Postgres database we’ve also been able to scale in numerous ways. Postgres has its own scaling capabilities built in. What we run into, is that now inside of this database were able to save information for a longer period of time, we’re able to make sure that all of the information that we’re dealing with inside of the Salt ecosystem is preserved, and more audible. This was one of the first things that people asked us for. Inside of Salt itself, if you’re running remote execution commands, it only keeps that history for 24 hours. It’s keeping it in flat files on the master. The master itself is made to be easy to set up, it’s easy to manage as possible, given the workload that it has to deal with. It doesn’t require did you have a database directly connected to it. SaltStack Enterprise gives you that ability to have a long-term audit control and audit trail for all of the commands that we’ve executed. One of the other common situations that we ran into is that we would have that core DevOps or SRE team set up Salt and they use it extensively and they love using it, but they notice that other teams wanted to have that power at their fingertips as well. But of course those of you who use Salt understand that that’s a lot of power and so SaltStack Enterprise added significant role based access controls…” – Thomas Hatch
Watch Salt Air on: YouTube