Tom leaves the slides at home and spends this entire Salt Air providing a demo of Salt pillar, modular file system, integration with gitfs, how to write Salt execution modules in Python, and more.
“It looks like we’re ready for another round of Salt Air. I’m going to be doing things a little differently this time. Instead of having a slide deck, I decided that I was going to go through, demo, and run through some examples of the couple of Salt technologies. I’m entirely shooting from the hip this week. I haven’t prepared anything and we’re just going to start talking about different things that Salt is capable of doing. We’re going to start out with pillar and we’re going to see how far we get from there. If we are able to get through that quickly then I’m going to move on to talking about the new modular filesystem back end and get FS. If we have time after that I’m going to talk about making writing code. We’ll see how far we get we’ve got about a half hour. Let’s talk about coding. Let’s start by talking about what color is, why you might need it. Sitting here on my laptop explaining pillar, the idea behind pillar is that often times you want to store information away from the minion that you can make that’s private. You want this information to be information that can be dynamically allocated based on what the minion is that you’re interfacing with. You want this information to be available. What pillar does is that it makes information available not just to your Salt formulas. Pillar also makes information available to Salt itself. It’s commonly used as a configuration medium, as a communication medium for for just spreading data around, and it’s used to keep track of private information because it can be minion specific data. I’m going to start by being my reckless self, I generally run my my environment off Git, so this is everything that’s happened since I did a good poll on this. I think it’s been a couple of days on this particular machine. I’ve been doing most of my work on my smaller laptop. Install Salt and let’s get this guy cooking.”
“Let’s start by looking at the master config file. I’ve got a few things in here that we’re going to talk about a little later on that I’ve recently been working on. The first thing that we do for pillar, is set up a pillar routes directive. The pillar routes directive works the same way as file routes. It’s environment based and takes a list of directories. By default this is what the pillar routes looks like, so you don’t need to go into your config file and change anything. If you just start making your pillar show up under /srv/pillar. If you wanted to add more environments to your pillar or if you wanted to add more directories or change the directories that pillar is located in, then we can add them inside of this directive…” – Thomas Hatch
Learn more about powerful automation and orchestration for the entire IT team with SaltStack.
Watch Salt Air on: YouTube