TRANSKRIBEERI 🔗
WEBVTT
NOTE
Transcription provided by Podhome.fm
Created: 7/6/2024 5:01:05 PM
Duration: 4010.870
Channels: 1
1
00:00:14.724 --> 00:00:16.425
Hello and welcome to podcast.
2
00:00:16.884 --> 00:00:20.170
Init. We are recording today on April 8,
3
00:00:20.870 --> 00:00:25.530
and we have Chris Patti and myself, Tobias Massey, as your hosts.
4
00:00:25.994 --> 00:00:29.454
Today, we're interviewing Thomas Hatch, the creator of SaltStack.
5
00:00:30.394 --> 00:00:48.385
So I just wanted to say a quick word about, I just came back from ChefConf in, Santa Clara, California last week. And I know this is a Python podcast, and, moreover, we're talking to the man behind SaltStack. So Chet might be just a little bit out of out of topic. But, I just had to say, on on the Python
6
00:00:48.765 --> 00:00:52.225
front, it's amazing to see how much
7
00:00:52.670 --> 00:00:53.969
the polyglot programming,
8
00:00:55.149 --> 00:01:16.020
way of life has taken. There was a lot of Python talk in the in the hallway track there, And, some of it may spawn some interviews that we may have in upcoming episodes, and I'm really looking forward to. It's, it's neat to see people becoming more open minded about tools, and when you get smart people using interesting things, it's, only coolness can result.
9
00:01:16.480 --> 00:01:19.605
So that was great. I had a great time. I highly recommend it.
10
00:01:20.405 --> 00:01:24.965
Also, on the community front, but back more towards Python, I just wanna mention that,
11
00:01:25.685 --> 00:01:37.355
there's another podcast out there. It came out right around the same time as, you know, we kinda looked around and said, hey, there are no Python podcasts out there. We should make 1. And it's called talk Python to me. It's at
12
00:01:38.295 --> 00:01:38.795
www.talkpython
13
00:01:39.255 --> 00:01:39.915
to me.com,
14
00:01:40.295 --> 00:01:51.550
and we'll have the full URL in the show notes. It's a great show, and, I just listened to episode 1 last night and this morning. He he talked about, and had an interview with Man Behind Eve,
15
00:01:51.954 --> 00:01:52.935
a really cool,
16
00:01:53.715 --> 00:01:58.774
REST API web service module for Python that just lets you take mongodb
17
00:01:59.075 --> 00:02:00.054
or other database
18
00:02:00.619 --> 00:02:13.725
schema and make it into a a restful API very easily. I look forward to playing with it myself, and, we're just happy to have someone else in the in the game here. I think more is better in this undertaking.
19
00:02:14.185 --> 00:02:14.905
And so,
20
00:02:15.385 --> 00:02:18.125
please go give him a listen. You you won't regret it.
21
00:02:19.070 --> 00:02:31.325
Alright. And with that, I would like to introduce our guest, Thomas Hatch. Thank you for joining us. And would you please, introduce yourself and explain a little bit about your background to our audience to anyone who may not have heard of UC yet?
22
00:02:32.745 --> 00:02:34.665
Sure. And thanks for having me.
23
00:02:35.064 --> 00:02:37.560
Yeah. My name is Thomas Hatch, and,
24
00:02:38.739 --> 00:02:43.799
I'm the original author and founder of the SaltStack Company and, author of Salt.
25
00:02:44.345 --> 00:02:47.724
Yeah. I started working on Salt back in, February of 2011.
26
00:02:48.985 --> 00:02:49.485
And,
27
00:02:49.785 --> 00:02:52.205
yeah, I started doing it full time beginning in 2012.
28
00:02:53.510 --> 00:02:58.970
Yeah. Before that, I, did systems administration in the system software development. So,
29
00:02:59.270 --> 00:03:02.090
yeah, I've I've deployed many cloud in my day.
30
00:03:04.695 --> 00:03:06.635
So how did you get introduced to Python?
31
00:03:07.655 --> 00:03:08.155
Oh,
32
00:03:08.695 --> 00:03:09.595
I honestly,
33
00:03:09.975 --> 00:03:11.195
I don't really remember.
34
00:03:13.080 --> 00:03:15.020
I mean, I I go back to
35
00:03:15.800 --> 00:03:20.700
to studying computer science in school where I was taught Java and I haven't used Java since then.
36
00:03:21.805 --> 00:03:23.585
And, back in school,
37
00:03:24.045 --> 00:03:28.065
there were there were a lot of people excited about Python, a lot of people excited about Ruby,
38
00:03:29.569 --> 00:03:32.150
and and I was very interested in learning languages.
39
00:03:33.330 --> 00:03:33.830
And
40
00:03:34.209 --> 00:03:39.305
so, I mean, I spent time with with some esoteric. I mean, even went through and learned OCaml.
41
00:03:40.325 --> 00:03:42.165
Spent a lot of time with Ruby, spent,
42
00:03:42.645 --> 00:03:44.825
spent a lot of time in C and etcetera.
43
00:03:45.820 --> 00:03:46.320
And,
44
00:03:46.860 --> 00:03:51.920
after working with Python, I just I just found it a lot more natural of a language to work with, and,
45
00:03:53.020 --> 00:03:58.965
we yeah. I just enjoyed working with Python more. So, I mean, from from an origin perspective, it's more of,
46
00:03:59.665 --> 00:04:02.885
yeah, my my primary argument was generally just preference.
47
00:04:03.980 --> 00:04:05.280
It's it's really interesting,
48
00:04:05.980 --> 00:04:13.045
how often OCaml crops up. It's 1 of those languages that even though it's not, like, listed among mainstream
49
00:04:13.665 --> 00:04:15.605
programming languages, per se,
50
00:04:16.225 --> 00:04:18.005
the thread of its, use
51
00:04:18.440 --> 00:04:22.380
winds its way through all kinds of different people and places, and,
52
00:04:22.919 --> 00:04:27.825
it it's seems like a really neat language. I I I have yet to actually take the time to learn it, but,
53
00:04:28.625 --> 00:04:34.245
seems like there's gotta be something there for so many people to have used it and and and cited it as an influence.
54
00:04:35.580 --> 00:04:38.400
I I definitely think of OCaml as an influencer,
55
00:04:39.180 --> 00:04:44.275
and I then I'd strongly recommend people to to learn it, not necessarily
56
00:04:44.655 --> 00:04:45.475
to use it,
57
00:04:48.014 --> 00:04:49.794
but but more so to
Load full transcript
understand,
58
00:04:51.229 --> 00:04:53.169
the flexibility of the functional paradigm
59
00:04:53.789 --> 00:04:55.729
and to understand how that
60
00:04:56.909 --> 00:05:00.815
how how they put object oriented programming directly inside of
61
00:05:01.295 --> 00:05:03.635
a functional paradigm. It's a really fascinating,
62
00:05:04.415 --> 00:05:05.635
fascinating language.
63
00:05:07.055 --> 00:05:09.395
So what made you choose Python for
64
00:05:09.790 --> 00:05:14.130
writing SaltStack? And was it just a matter of preference, or were there particular architectural
65
00:05:14.590 --> 00:05:23.055
capacities that it had that made you wanna choose it? And if you were to start from scratch all over again, would you use Python again or would you choose a different language?
66
00:05:24.235 --> 00:05:29.690
OCaml's already kind of brought been brought up, so I can't crack a joke and say, Oh, I would use OCaml.
67
00:05:32.470 --> 00:05:35.370
No, I would definitely use Python again and I
68
00:05:35.750 --> 00:05:37.895
think that the choice of using Python
69
00:05:39.315 --> 00:05:42.135
was a good 1 and I look back and
70
00:05:42.595 --> 00:05:46.900
there's there's a lot of things that we've been able to do in Salt because we chose Python.
71
00:05:47.699 --> 00:05:48.680
1 of the main
72
00:05:49.139 --> 00:05:52.440
tenants of salt is its is its plug in system,
73
00:05:53.300 --> 00:05:56.360
and that plug in system is something that
74
00:05:56.805 --> 00:05:59.145
was very easy to write, very easy to make,
75
00:06:00.565 --> 00:06:02.985
make powerful in using Python.
76
00:06:03.660 --> 00:06:07.980
And, because of the way that you can introspect the language, the way that,
77
00:06:08.300 --> 00:06:10.800
you can you can really bend it to your will,
78
00:06:11.995 --> 00:06:18.095
and the very dynamic nature of being able to load things on the fly in a in a reasonable way.
79
00:06:18.850 --> 00:06:25.750
And so, I mean, that's been that's been a big boon. And then some of the other aspects of Python that have been really beneficial has been,
80
00:06:26.655 --> 00:06:27.794
a lot of the concurrency,
81
00:06:29.615 --> 00:06:35.875
libraries and systems which have more recently come into play. And that's that's 1 of those exciting things where we've been able to
82
00:06:36.320 --> 00:06:40.900
begin implementing more and more of that concurrency aspect inside of Salt to make it
83
00:06:41.360 --> 00:06:43.380
even faster and even more efficient.
84
00:06:43.995 --> 00:06:50.255
Yeah. I'll definitely say that having the plug in capabilities has made my life easier on a few occasions, being able
85
00:06:50.794 --> 00:06:55.340
to write your own little module that does exactly what you want and plug it into the overall
86
00:06:55.720 --> 00:06:59.980
execution paradigm without having to dig deep into any of the internals
87
00:07:00.565 --> 00:07:03.065
Definitely makes for a really architecturally
88
00:07:03.365 --> 00:07:03.865
sound
89
00:07:04.565 --> 00:07:05.065
capability.
90
00:07:05.685 --> 00:07:10.105
Thank you. Yep. That that was definitely a goal, to make those plug ins as easy as possible.
91
00:07:11.370 --> 00:07:14.910
What are some of the challenges you faced maintaining a large and complex,
92
00:07:15.290 --> 00:07:16.830
Python code base like SaltStack?
93
00:07:17.130 --> 00:07:19.470
Does Python make anything easier or harder?
94
00:07:21.175 --> 00:07:21.675
That's,
95
00:07:22.695 --> 00:07:28.555
there's there's definitely pitfalls in Python with large code bases, and there's a lot that we've done architecturally
96
00:07:29.670 --> 00:07:34.010
to try and keep that to so that it's less of a complex problem.
97
00:07:34.550 --> 00:07:37.770
So 1 of the 1 of the main things that we've done to alleviate,
98
00:07:38.390 --> 00:07:41.284
just having an overly complex code base in general,
99
00:07:42.224 --> 00:07:49.870
is salts loader and plug in system. And so salt itself, the salt code base is somewhere in the realm of 90% plug ins.
100
00:07:50.570 --> 00:07:55.630
And by somewhere in the realm, I haven't actually done the math you know, I haven't done the calculation on it recently.
101
00:07:56.395 --> 00:07:57.195
And Salt,
102
00:07:57.675 --> 00:08:00.255
has 21 plug in systems right now.
103
00:08:01.275 --> 00:08:01.775
And,
104
00:08:02.475 --> 00:08:04.770
the fact that we can have these completely
105
00:08:05.389 --> 00:08:05.889
isolated,
106
00:08:06.590 --> 00:08:07.650
plug in subsystems
107
00:08:08.750 --> 00:08:11.810
inside of Solve and having the the code isolation
108
00:08:12.755 --> 00:08:15.575
is has been 1 of the biggest benefits for,
109
00:08:16.435 --> 00:08:17.575
being able to manage,
110
00:08:18.275 --> 00:08:20.055
such a large code base because,
111
00:08:21.000 --> 00:08:21.500
functionally,
112
00:08:22.280 --> 00:08:23.740
the entire capability
113
00:08:24.280 --> 00:08:24.780
of,
114
00:08:25.720 --> 00:08:27.340
every individual component
115
00:08:27.640 --> 00:08:30.764
is reasonably isolated into its own scope,
116
00:08:31.065 --> 00:08:35.325
which makes it really easy to be able to do things like completely rewrite
117
00:08:36.110 --> 00:08:41.089
how, say, we manage a certain container type. I mean, we just completely overhaul
118
00:08:41.709 --> 00:08:43.329
all of our LXC container
119
00:08:43.785 --> 00:08:45.805
systems, and it only meant
120
00:08:46.425 --> 00:08:48.605
effectively editing a couple of files.
121
00:08:49.145 --> 00:08:50.845
And so that's been a huge benefit.
122
00:08:52.459 --> 00:08:56.320
That's great. So something that just occurred to me sort of
123
00:08:57.339 --> 00:09:01.440
first of all, I'm curious what you when you say plug in, separate plug in systems,
124
00:09:01.855 --> 00:09:06.915
I have a funny feeling that there's some meaning behind those words that for those of us who are less,
125
00:09:07.935 --> 00:09:13.690
salt savvy, could you
could you explain what what you meant by that as opposed to just straight plug ins?
126
00:09:15.110 --> 00:09:15.610
Yeah.
127
00:09:15.910 --> 00:09:16.410
So
128
00:09:18.214 --> 00:09:21.355
a lot of people look at SALT and they see SALT as
129
00:09:22.055 --> 00:09:29.110
a configuration management system. I mean, we generally get lumped in that category. I mean, not generally, almost always.
130
00:09:29.970 --> 00:09:32.550
And the reality is that salt is,
131
00:09:33.730 --> 00:09:36.470
is just is more of a generic management system.
132
00:09:36.865 --> 00:09:37.605
And so
133
00:09:37.905 --> 00:09:53.029
we have many, many different layers of salt which are pluggable. And so when we look at it, you were mentioning before how easy it is to write some functions and plop it in. And so what most people see as our as the primary plug in system is the execution modules.
134
00:09:53.410 --> 00:09:59.255
And that's just running a single salt command and it goes out and fires off that chunk of Python code,
135
00:09:59.715 --> 00:10:01.575
but then the config management system
136
00:10:02.035 --> 00:10:07.139
is all in a different plugin layer called states and those states call
137
00:10:07.519 --> 00:10:12.820
call down to those execution modules so those 2 plugin systems work together.
138
00:10:14.205 --> 00:10:20.385
And so that's how we get config management is that we take, oh, yeah. We've got command and control, really simple remote execution,
139
00:10:20.990 --> 00:10:22.370
and then we're able to put
140
00:10:22.750 --> 00:10:27.170
and layer a new system on top of it which is configuration management.
141
00:10:27.709 --> 00:10:28.449
But then,
142
00:10:28.750 --> 00:10:33.015
like, the file server back end system installed is a plug in system,
143
00:10:33.395 --> 00:10:38.215
and that's, the component that allows the Saltmaster to directly hook into
144
00:10:38.730 --> 00:10:41.550
a Git repository so that as soon as you commit
145
00:10:41.930 --> 00:10:46.350
your, config management components or your your own plugins
146
00:10:46.805 --> 00:10:49.945
into Git. They're instantly available to solve.
147
00:10:50.325 --> 00:10:52.425
And so since that's a plugin system,
148
00:10:52.885 --> 00:10:55.680
we've got a plugin for Git, a plug in for Mercurial,
149
00:10:56.140 --> 00:11:01.120
SVN, or Azure FS, and Amazon's s 3, etcetera, etcetera.
150
00:11:01.915 --> 00:11:03.775
And similarly, we've got plugins,
151
00:11:04.235 --> 00:11:05.855
a plugin system for authentication.
152
00:11:06.555 --> 00:11:10.095
We've got we just introduced the new beacon system, which is really cool
153
00:11:10.740 --> 00:11:13.640
because SALT is an entirely event based system.
154
00:11:14.340 --> 00:11:21.515
And so the beacons allows you to watch any arbitrary thing that's going on in your environment and then fire events
155
00:11:22.135 --> 00:11:28.715
so that you can fire an event when specific files are changed, deleted, or created. You could fire events when someone logs in
156
00:11:29.190 --> 00:11:32.890
and then that goes up into the reactor system which is another plug in system.
157
00:11:33.270 --> 00:11:44.315
And so really we Salt is really this combination of all of these plug in systems and realizing that you can build virtually any application that you want to distribute it across an infrastructure
158
00:11:45.255 --> 00:11:46.315
using Salt.
159
00:11:47.540 --> 00:11:54.845
Sorry. That probably just made made your question to please clarify this into, well, that's confusing and there's lots of bits I didn't know about.
160
00:11:55.884 --> 00:12:02.464
Actually, no. I I think I think you did an excellent job because as I said, as I kinda hinted at with my ChefConf reference earlier,
161
00:12:02.820 --> 00:12:10.680
I I work with chef day in day out in my day job. And it struck me as you were explaining it that this must make
162
00:12:12.135 --> 00:12:12.635
adding
163
00:12:13.095 --> 00:12:13.915
not just
164
00:12:14.855 --> 00:12:17.115
new wrinkles, but whole new concepts
165
00:12:17.815 --> 00:12:21.595
easier than a more declarative DSL sort of system because
166
00:12:22.279 --> 00:12:23.660
everything is much more
167
00:12:24.200 --> 00:12:26.860
abstract and modular in its space. Is that right?
168
00:12:27.640 --> 00:12:30.540
Very, very much so. Yeah. Because the goal is
169
00:12:30.954 --> 00:12:35.295
is a lot more than setting up and maintaining systems. The goal is
170
00:12:35.675 --> 00:12:36.175
is
171
00:12:36.555 --> 00:12:40.654
keeping track of those systems and managing them in a very holistic way.
172
00:12:42.380 --> 00:12:52.535
Yeah. I have to say that the beacon system definitely sounds very intriguing, and I can't wait to have an opportunity to try that out because I've played a little bit with the reactor system, particularly for managing,
173
00:12:53.395 --> 00:13:00.200
doing code deployments from GitHub webhooks. But the beacon system sounds like it's just add a lot more
174
00:13:00.580 --> 00:13:07.080
capability and adaptability to your system. You know, as you mentioned, being able to fire an event when a file gets changed,
175
00:13:07.705 --> 00:13:12.205
there's just no end to the number of different ideas or concepts you could do with that.
176
00:13:12.825 --> 00:13:17.959
Yeah. I should say that the excitement around beacons, we we announced them at Saltconf
177
00:13:18.500 --> 00:13:19.480
which was,
178
00:13:20.580 --> 00:13:22.600
yeah, just just 1 month ago.
179
00:13:23.459 --> 00:13:23.959
And
180
00:13:24.315 --> 00:13:30.335
the, yeah, the excitement was overwhelming. I mean, that was the only thing everybody was talking about it seemed like for
181
00:13:30.795 --> 00:13:37.300
for all of Zolgov that they were saying, oh, I can create all sorts of dynamic reactions now based on anything that happens.
182
00:13:38.400 --> 00:13:47.865
And, yeah. I mean, we've got companies. We just added
a beacon that every time, So if somebody logs into a minion, every command that they execute on the shell gets fired as an event
183
00:13:48.565 --> 00:13:51.300
so that then they can have an event filter that just
184
00:13:51.620 --> 00:13:53.480
shows them or and tracks
185
00:13:54.260 --> 00:13:59.399
every command executed on every system by that user so that they get this centralized
186
00:14:00.465 --> 00:14:03.285
log of all activity that's happened in their infrastructure.
187
00:14:03.905 --> 00:14:17.700
And so, I mean, just all sorts of things like that that people have been really excited about. It's amazing. I bet that would make PCI or SOX compliance a lot a lot simply a lot simpler to manage having the audit trail of everybody who's ever been in any of the systems.
188
00:14:18.865 --> 00:14:27.730
Yeah. And that's and that's 1 of the big motivations and we've had a bunch of customers come back and ask us and ask us for it which is why, again, we're very excited to put it in. Great.
189
00:14:28.610 --> 00:14:30.630
That follows into our next question of
190
00:14:31.089 --> 00:14:32.709
how do you balance the
191
00:14:33.089 --> 00:14:37.505
desires and needs of the open source community around SaltStack with
192
00:14:37.985 --> 00:14:40.565
the desires and needs of the company behind it.
193
00:14:40.945 --> 00:14:47.700
But do those 2 communities ever come in conflict or has it generally been a synergistic effect so far?
194
00:14:48.959 --> 00:14:53.060
What, I mean, what what you're asking is an incredibly tricky balance
195
00:14:53.839 --> 00:14:54.339
and,
196
00:14:55.275 --> 00:14:59.535
and a and a very tricky balance from both ends. And my goal with SaltStack
197
00:15:00.555 --> 00:15:02.255
has been to create a company
198
00:15:02.715 --> 00:15:06.610
that is that fuels the community and is fueled by the community.
199
00:15:08.509 --> 00:15:09.009
And,
200
00:15:09.470 --> 00:15:13.095
I I I talk about this a little bit more in my my keynote
201
00:15:13.475 --> 00:15:14.695
for Solkoff that,
202
00:15:15.715 --> 00:15:19.415
that we should have up on the web here in the next in the next few days.
203
00:15:20.160 --> 00:15:21.060
But the
204
00:15:21.440 --> 00:15:23.940
but the main goal is that we as a company
205
00:15:24.399 --> 00:15:25.300
are able to
206
00:15:25.680 --> 00:15:26.579
gain insight,
207
00:15:27.415 --> 00:15:31.355
and learn from our community and learn how to continue to develop products
208
00:15:32.055 --> 00:15:33.595
to serve the needs of
209
00:15:33.950 --> 00:15:39.570
of others just in general. And we've done a very good job, I believe, of keeping that synergistic.
210
00:15:40.190 --> 00:15:43.785
And we've done that by making sure that we're not open core.
211
00:15:44.485 --> 00:15:48.505
The plug in system helps a great deal because we are able to,
212
00:15:49.600 --> 00:15:55.140
I mean, there's there's certainly situations where we have proprietary plug ins that we only ship to enterprise customers.
213
00:15:55.920 --> 00:16:01.545
But they're plug ins and they're plug ins that only really make sense to people who are already
214
00:16:01.925 --> 00:16:05.225
buying the, the large system that we're plugging into.
215
00:16:06.165 --> 00:16:06.665
And
216
00:16:08.570 --> 00:16:12.190
the concepts and ideas and innovation that comes out of the community
217
00:16:12.889 --> 00:16:23.255
becomes the fire hose for us developing new features and finding out what our customers really want and what our customers that aren't our customers yet really want.
218
00:16:23.795 --> 00:16:28.890
And it it in a very huge way that synergy has been what drives the business
219
00:16:29.510 --> 00:16:32.890
instead of more of those classical open source business models,
220
00:16:33.510 --> 00:16:34.010
of
221
00:16:34.425 --> 00:16:35.644
going open core
222
00:16:36.024 --> 00:16:38.764
or, trying to rein in what's happening
223
00:16:39.225 --> 00:16:41.005
in the community because the community
224
00:16:41.770 --> 00:16:43.630
can be such a wild wild west.
225
00:16:44.330 --> 00:16:45.470
I mean, we
226
00:16:46.730 --> 00:16:50.355
we will process sometimes over 200 poll requests in a week.
227
00:16:51.394 --> 00:16:56.135
We're we process more inbound code than anybody else in,
228
00:16:56.755 --> 00:16:59.415
the configuration management communities easily.
229
00:17:00.260 --> 00:17:00.760
And,
230
00:17:01.460 --> 00:17:03.000
yeah, it's it's an incredibly,
231
00:17:04.260 --> 00:17:07.240
active and scary thing to keep on top of.
232
00:17:08.645 --> 00:17:12.665
But it all fuels the company and the company's interests fuel the community.
233
00:17:13.525 --> 00:17:18.800
So so for instance, going back to beacons, beacons were developed to deliver specific,
234
00:17:20.300 --> 00:17:20.800
specific
235
00:17:21.100 --> 00:17:23.935
utilities that customers were asking for.
236
00:17:24.495 --> 00:17:29.155
And we were able to build plug ins that are beacons for those customers
237
00:17:29.695 --> 00:17:31.635
that are specific to their use cases.
238
00:17:32.290 --> 00:17:35.190
But we were able to then take what that customer wanted
239
00:17:35.570 --> 00:17:41.535
and put that fundamental system in the open, which then drives us to create more things.
240
00:17:42.495 --> 00:17:49.235
That's that's awesome. I and and just to speak really briefly on that note, from the Chef community side, I think everybody
241
00:17:49.690 --> 00:17:52.269
in this space is struggling with this a little bit.
242
00:17:52.730 --> 00:17:58.429
And, on the Chef side, I know that they they 1 of the things they've been doing recently is starting up
243
00:17:58.875 --> 00:18:05.695
an RFC process to sort of try to structure some of that community input because the chef community is has
244
00:18:06.160 --> 00:18:11.040
experienced exponential growth, which as we all know can be both a good thing and a bad thing. It's,
245
00:18:11.760 --> 00:18:13.860
so thank you for for filling us in.
246
00:18:15.065 --> 00:18:19.485
Yeah. I would I'll definitely agree that the open core model can be very contentious
247
00:18:19.865 --> 00:18:20.765
a lot of times.
248
00:18:21.625 --> 00:18:25.990
It can be beneficial to the project and the company because it does provide a way to
249
00:18:26.610 --> 00:18:35.075
pay the developers who are working on it and drive drive it forward. But when it can be avoided, it's definitely preferable because it definitely bumped up against some circumstances where
250
00:18:35.375 --> 00:18:36.434
there was some functionality
251
00:18:37.054 --> 00:18:41.315
that was in the, you know, proprietary portion of the code base that
252
00:18:41.620 --> 00:18:42.520
wasn't quite,
253
00:18:43.140 --> 00:18:51.455
compelling enough to make me wanna actually jump for the enterprise offering, but just frustrating enough that it turned me away from wanting to the open source portion of the project.
254
00:18:51.835 --> 00:18:52.655
So definitely,
255
00:18:53.515 --> 00:19:00.590
definitely kudos to you guys for being able to avoid the open core model and still be so widely successful as you are.
256
00:19:02.090 --> 00:19:07.950
I I appreciate it. And yeah. And it is tricky. The the 1 of the big things that we've discovered is that
257
00:19:08.475 --> 00:19:12.735
when we go in to I mean, we go into a big organization to sell
258
00:19:13.115 --> 00:19:18.230
and some of the benefits of Salt is that it scales well, it works really well in very complex environments
259
00:19:19.010 --> 00:19:22.470
and those companies are more apt to to spend money
260
00:19:23.170 --> 00:19:23.490
on,
261
00:19:24.215 --> 00:19:25.355
on things like SaltStack,
262
00:19:26.215 --> 00:19:31.835
but then the but then the flip side is that much of who we sell to are the groups peripheral
263
00:19:32.890 --> 00:19:33.390
to,
264
00:19:33.770 --> 00:19:36.270
the people who are contributing contributing us
265
00:19:36.730 --> 00:19:41.550
code. So we go into the company and we're able to say to the people who are giving us code,
266
00:19:41.895 --> 00:19:46.715
who are the people around you who would benefit by visibility into Solv?
267
00:19:47.095 --> 00:19:52.590
And then we can sell those people proprietary software that gives them the visibility into what's going on.
268
00:19:53.290 --> 00:19:56.830
And those sorts of approaches have been very, very,
269
00:19:57.290 --> 00:19:58.990
lucrative for us. It's been
270
00:19:59.315 --> 00:20:02.535
a very interesting approach to be able to say that
271
00:20:02.835 --> 00:20:08.855
instead of trying to bleed money, to to get blood out of a turnip by trying to bleed money out of your community,
272
00:20:09.300 --> 00:20:15.800
we're able to go out and ask the community, who is it that's around you who wants to give us money and we'll go ask them.
273
00:20:16.534 --> 00:20:27.070
Yeah. That's a that's a great model and definitely sounds sounds like a very intelligent way to do business with making friends everywhere you go and avoiding making any enemies. So excellent.
274
00:20:27.450 --> 00:20:28.670
So far so good.
275
00:20:30.010 --> 00:20:32.350
We'll see if we're still in business in a few years.
276
00:20:34.535 --> 00:20:40.715
Yep. I I don't see you guys going away anytime soon. I mean, I I hear a lot about salt, and and I think you guys are experiencing,
277
00:20:41.415 --> 00:20:46.450
you know, maybe not quite meteoric adoption, but but but certainly, I think you're in good shape.
278
00:20:47.470 --> 00:20:51.409
So if you'll indulge me in in, or allow me to indulge in generalities,
279
00:20:52.075 --> 00:20:55.375
developers tend to gravitate towards chef, sysadmins,
280
00:20:55.835 --> 00:20:58.414
and ops folks tend to gravitate towards puppet.
281
00:20:58.929 --> 00:21:01.910
Who might find SaltStack a superior choice and why?
282
00:21:04.289 --> 00:21:04.789
So,
283
00:21:05.490 --> 00:21:05.990
traditionally,
284
00:21:06.865 --> 00:21:08.304
sysadmins have been,
285
00:21:08.705 --> 00:21:10.085
more intrigued by SaltStack.
286
00:21:10.784 --> 00:21:13.044
And a lot of the reasons for that is because
287
00:21:13.505 --> 00:21:17.210
Salt does a really good job of solving system administrative problems.
288
00:21:17.909 --> 00:21:20.330
Salt does a really good job of solving problems
289
00:21:21.029 --> 00:21:25.655
that the, that the developer crowd doesn't necessarily see right off the bat.
290
00:21:26.915 --> 00:21:32.135
1 thing that's very 1 thing that's very common that we see is that we'll go that we will see infrastructures
291
00:21:32.595 --> 00:21:33.335
that were
292
00:21:34.240 --> 00:21:35.380
built by developers
293
00:21:35.760 --> 00:21:38.580
and that we see a very large adoption
294
00:21:39.200 --> 00:21:44.904
once those infrastructures get too big to be maintained by the original developers who built them.
295
00:21:45.284 --> 00:21:45.784
And,
296
00:21:46.645 --> 00:21:51.225
and so a lot of it has to do with scale, a lot of it has to do with the fact that
297
00:21:52.240 --> 00:21:55.620
consult just scales up really, really nicely and doesn't need
298
00:21:56.320 --> 00:21:56.820
modification,
299
00:21:58.240 --> 00:22:05.235
outside of, you know, tweaking some configuration parameters to be able to handle a lot of, a lot of scale and to handle really complex
300
00:22:06.095 --> 00:22:07.235
infrastructure problems.
301
00:22:07.670 --> 00:22:09.930
With that said, we definitely still see,
302
00:22:10.470 --> 00:22:12.250
a fair amount of developer adoption.
303
00:22:12.790 --> 00:22:19.025
And there's a lot that we've been doing recently and a lot that we're working on right now to try and increase that developer adoption.
304
00:22:19.565 --> 00:22:20.065
Because,
305
00:22:20.605 --> 00:22:25.105
most most of our documentation right now is very focused towards system administrators.
306
00:22:25.405 --> 00:22:26.225
It's very
307
00:22:27.080 --> 00:22:27.580
encyclopedic
308
00:22:28.200 --> 00:22:28.940
in nature.
309
00:22:29.720 --> 00:22:32.600
And so we're getting very close. We've got a whole new,
310
00:22:32.920 --> 00:22:34.140
introductory documentation
311
00:22:34.555 --> 00:22:40.495
system that was developed by someone other than me because I'm not good at developing that kind of documentation apparently
312
00:22:41.195 --> 00:22:43.935
that we're gonna be that we're gonna be introducing very soon.
313
00:22:44.289 --> 00:22:46.870
We put a huge amount of effort into Salt SSH
314
00:22:47.730 --> 00:22:49.750
to to make that whole,
315
00:22:50.610 --> 00:22:52.390
deployment of code and
316
00:22:52.955 --> 00:22:54.415
really seamless, masterless,
317
00:22:55.275 --> 00:22:55.775
management,
318
00:22:56.715 --> 00:22:57.775
really, really slick.
319
00:22:58.155 --> 00:23:01.775
And we're very, very proud of Salt SSH. It is incredibly fast
320
00:23:02.430 --> 00:23:03.570
and gives you
321
00:23:03.870 --> 00:23:05.330
virtually all of the functionality
322
00:23:05.790 --> 00:23:08.130
of remote execution and config management
323
00:23:08.990 --> 00:23:10.850
inside of Salt. I mean, if
324
00:23:11.434 --> 00:23:14.575
with, with this next release that we're finalizing right now,
325
00:23:15.274 --> 00:23:16.735
we're on our second RC,
326
00:23:18.315 --> 00:23:21.240
the salt SSH is to the point where
327
00:23:21.540 --> 00:23:27.480
it can do everything the salt can do without having to without having an agent out there.
328
00:23:28.875 --> 00:23:32.095
And so these systems, we're very very excited about
329
00:23:32.715 --> 00:23:35.534
as we go after that developer market more.
330
00:23:36.510 --> 00:23:37.970
So the the Salt SSH
331
00:23:38.750 --> 00:23:43.650
aspect sounds really neat. Is that perhaps an answer without mentioning names
332
00:23:44.155 --> 00:23:49.775
to some other configuration management systems that are gaining ground because of super easy adoption?
333
00:23:50.155 --> 00:23:53.375
You know, like, because they people can start out with just simple orchestration
334
00:23:54.299 --> 00:23:55.679
and add very simple
335
00:23:56.140 --> 00:23:56.640
configuration
336
00:23:57.020 --> 00:24:01.120
in. I'm thinking of the thing that could be used in a blacksmith shop.
337
00:24:05.375 --> 00:24:09.155
We learned we we've learned a lot from our competitors
338
00:24:10.980 --> 00:24:11.380
and,
339
00:24:11.780 --> 00:24:13.800
definitely watch what they are doing.
340
00:24:14.420 --> 00:24:19.895
And I should say that I am I'm very grateful to them from what we've been able to learn.
341
00:24:20.434 --> 00:24:20.835
And,
342
00:24:21.315 --> 00:24:24.135
so, yes, there is definitely some answer there.
343
00:24:24.515 --> 00:24:29.269
And so all this to say historically is, I mean, it's a it's a really interesting thing because
344
00:24:29.649 --> 00:24:35.190
originally, we wrote it to extract the transport system out and just kind of clean up the code
345
00:24:35.895 --> 00:24:40.955
and, very much so as a challenge to see, hey, could we actually do this?
346
00:24:41.575 --> 00:24:45.640
And then we kind of we kind of stepped away from it for maybe 6 months or so
347
00:24:46.200 --> 00:24:52.380
and said, hey. We accomplished this. We've got a lot of other big things to deal with to handle our big infrastructure customers
348
00:24:53.315 --> 00:24:55.174
and our big infrastructure users.
349
00:24:55.635 --> 00:24:56.135
And,
350
00:24:57.075 --> 00:25:02.455
we more recently came back because we saw more and more demand around wanting Salt SSH.
351
00:25:03.270 --> 00:25:04.010
And so,
352
00:25:04.870 --> 00:25:09.050
most most of our recent work has definitely been an answer to our competitors.
353
00:25:10.070 --> 00:25:15.595
And and we really look at that and hope that, getting out, better introductory documentation,
354
00:25:16.535 --> 00:25:22.510
helping people understand that from a high level, we still definitely believe that Salt is the easiest to use
355
00:25:23.050 --> 00:25:25.310
configuration management system out there.
356
00:25:25.635 --> 00:25:29.095
And that unlike a lot of other systems out there,
357
00:25:29.475 --> 00:25:32.935
we started by solving the hard problems at scale
358
00:25:33.669 --> 00:25:41.210
and that we wanna be able to to deliver something that is easy to get started with, easy to roll out, all those things that you're saying,
359
00:25:41.825 --> 00:25:47.284
but that will grow with the person who's deploying it because we've seen so
360
00:25:47.745 --> 00:25:48.485
so commonly
361
00:25:49.370 --> 00:25:50.190
these infrastructures
362
00:25:50.650 --> 00:25:58.830
get up to a few 100 servers and then they come over and they say, oh, we need to scale now and these systems are so slow and what's taking us
363
00:25:59.355 --> 00:26:03.215
hours to do takes us minutes and seconds to do a solve.
364
00:26:04.475 --> 00:26:07.455
That's that's awesome. And I think the marketplace has shown,
365
00:26:07.800 --> 00:26:09.980
has spoken very clearly that
366
00:26:10.280 --> 00:26:15.315
a really easy ramp up and adoption curve is super important and and that
367
00:26:16.115 --> 00:26:18.695
in a way, it's kind of less important that
368
00:26:18.995 --> 00:26:23.414
the best configuration management system win, but that the easiest win,
369
00:26:23.960 --> 00:26:35.155
at least as far as the market is concerned. So I know Chef's been doing it a lot in that sphere as well. I'm really glad to hear you folks are are recognizing the importance of that and, and tooling appropriately.
370
00:26:36.815 --> 00:26:43.690
Yeah. Yeah. And I, yeah. And we've we've really gotta get out and market more of what Salt SSH can do now.
371
00:26:44.389 --> 00:26:44.889
Alright.
372
00:26:45.429 --> 00:26:47.289
So 1 thing that Salt
373
00:26:47.750 --> 00:26:52.684
has that's both a benefit and sometimes potentially a detriment is the fact that it
374
00:26:53.065 --> 00:26:56.205
doesn't really impose any particular rigid structure
375
00:26:56.585 --> 00:26:59.990
on how you make use of it. So I'm just wondering
376
00:27:00.690 --> 00:27:02.309
what some of the complications
377
00:27:02.610 --> 00:27:08.070
you've seen arise out of that of, you know, not having a particular prescribed approach to
378
00:27:08.495 --> 00:27:09.055
using it,
379
00:27:09.455 --> 00:27:14.355
and also, you know, some of the major benefits that you've seen as a result of that as well?
380
00:27:16.230 --> 00:27:24.409
So 1 of the 1 of the things that I think is interesting about Salt is that I tried to make it so that the config management system would be easy to learn,
381
00:27:25.174 --> 00:27:31.514
easy to transfer from person to person, tried to make it so that the the systems are really easy to interface with.
382
00:27:32.375 --> 00:27:32.875
But
383
00:27:33.470 --> 00:27:34.690
as salt is grown
384
00:27:35.070 --> 00:27:37.490
exactly what you're saying is what's happened is that
385
00:27:37.870 --> 00:27:44.605
is the salt itself is fundamentally built to be flexible enough to solve any problem that you can throw at it.
386
00:27:44.985 --> 00:27:49.245
And the problem that we're into is that is that that could be very overwhelming for people
387
00:27:49.890 --> 00:27:53.270
that we that we basically say, hey. Have a ton of rope.
388
00:27:54.450 --> 00:27:57.110
You could build you could build whatever you wanna build.
389
00:27:58.195 --> 00:28:00.934
And I mean, the benefit to that is
390
00:28:01.394 --> 00:28:09.940
very, very straightforward when we look at some of the things that people have built. I mean I mean, SALT is being used literally to manage cruise ships.
391
00:28:10.879 --> 00:28:13.139
I mean, we talk about, like, Internet of things.
392
00:28:13.565 --> 00:28:19.024
SALT is used to manage cruise ships. It's used to manage slot machines. It's used to manage
393
00:28:20.205 --> 00:28:24.769
and deploy code on weather stations in South Africa.
394
00:28:26.029 --> 00:28:26.529
And,
395
00:28:27.149 --> 00:28:29.330
that loose coupling is what enables
396
00:28:29.789 --> 00:28:31.730
that level of integration,
397
00:28:32.645 --> 00:28:37.465
and that loose coupling is what enables us to, you know, do whatever needs to be done.
398
00:28:38.005 --> 00:28:45.960
And it's and and it horrifies people when they come to me and they say, well, Tom, what's the, you know, what's the right way to use salt? And I say,
399
00:28:46.260 --> 00:28:49.720
the right way to use salt is to use it in a way that solves your problems.
400
00:28:51.315 --> 00:28:52.054
And, yeah,
401
00:28:52.915 --> 00:28:54.695
it's it's a very different paradigm
402
00:28:55.955 --> 00:29:02.250
because a lot of people wanna be handed something that says, here's your rule book so that you don't get into trouble.
403
00:29:03.510 --> 00:29:08.809
And, we've we've worked really hard to structure salt so that it's it's harder to get into trouble.
404
00:29:09.655 --> 00:29:14.235
But it does it does lend a bit of a challenge when it comes especially to the configuration
405
00:29:14.615 --> 00:29:16.075
management end of salt
406
00:29:16.730 --> 00:29:17.230
that,
407
00:29:17.690 --> 00:29:19.870
that people want that structure in place.
408
00:29:20.250 --> 00:29:22.110
And as such, we have developed,
409
00:29:22.490 --> 00:29:23.310
best practices
410
00:29:23.804 --> 00:29:26.545
guides around how to build the configuration management
411
00:29:28.205 --> 00:29:31.505
in a way that is more maintainable and is more transferable.
412
00:29:32.590 --> 00:29:35.970
And putting a lot of that emphasis on, you know, making really generic
413
00:29:36.590 --> 00:29:37.890
salt states and
414
00:29:38.190 --> 00:29:39.730
using pillar to,
415
00:29:40.395 --> 00:29:41.935
to steer what's happening,
416
00:29:42.715 --> 00:29:44.895
which is really the core idea of pillar.
417
00:29:45.515 --> 00:29:47.535
But it but it definitely has been a challenge.
418
00:29:48.300 --> 00:29:52.480
And people are more apt to use a tool out of the box, I will say,
419
00:29:53.100 --> 00:29:55.120
that gives you those rigid guidelines.
420
00:29:56.140 --> 00:29:56.640
But
421
00:29:57.825 --> 00:30:00.885
I feel confident that we will continue to grow. And
422
00:30:01.425 --> 00:30:05.045
like you were saying, we don't we've never grown at a meteoric pace.
423
00:30:05.520 --> 00:30:08.020
We've grown at a steady and a strong pace.
424
00:30:08.640 --> 00:30:11.460
And I think that that has to do with the fact that
425
00:30:11.920 --> 00:30:15.795
the salt is something which can adapt itself to any scenario.
426
00:30:16.335 --> 00:30:18.675
And we're not out there drumming up the hype.
427
00:30:19.054 --> 00:30:27.410
We're not out there saying, oh, 0, look at the, you know, look at the shiny bits. We're out there saying, we will solve your real problems
428
00:30:29.230 --> 00:30:31.490
and help, you know, and make make those problems
429
00:30:32.385 --> 00:30:33.125
go away
430
00:30:33.985 --> 00:30:39.205
in a real way instead of, you know, trying to sell the snake oil of the moment.
431
00:30:40.740 --> 00:30:45.000
That's that's excellent, and I I'm glad that you folks are are putting some focus into
432
00:30:45.460 --> 00:30:51.095
giving people some some guidelines, because I think, you know, that the other product that we were speaking about, previously,
433
00:30:51.635 --> 00:30:53.975
I think that's sort of 1 of the ways that they've
434
00:30:54.435 --> 00:30:58.549
gained such a tremendous amount of of of adoption of late
435
00:30:58.929 --> 00:31:09.855
is by giving people, like, here, look, you can do this very easily. And it's a very small thing. Right? I mean, the truth is most of what people start with could be achieved very easily with other tools,
436
00:31:10.315 --> 00:31:15.880
but it's like people love that. And if you sort of make it really clear to them, make it very concrete, to
437
00:31:17.071 --> 00:31:17.571
offer
438
00:31:18.762 --> 00:31:19.262
them,
439
00:31:22.143 --> 00:31:22.643
the
440
00:31:24.154 --> 00:31:25.375
to offer them,
441
00:31:26.154 --> 00:31:29.934
the the ability to scale and the ability to build really complex infrastructures,
442
00:31:31.034 --> 00:31:32.015
you know, even
443
00:31:32.395 --> 00:31:33.135
by comparison,
444
00:31:33.770 --> 00:31:36.190
much more so than some other of its competitors,
445
00:31:36.890 --> 00:31:39.630
I I think that's great. I'm glad I'm glad to see that.
446
00:31:40.490 --> 00:31:41.770
Yeah. I will say that,
447
00:31:42.445 --> 00:31:54.330
to your point, Chris, you know, there are certain different tools that you can use for doing number of the various things that SaltStack can do as well, but that's the problem right there is that they are different tools, whereas Salt,
448
00:31:54.630 --> 00:31:58.409
you can use 1 tool to do all of it. That that's been my experience.
449
00:31:59.115 --> 00:32:06.735
At a previous company I was working at, we act had actually just had a similar issue where we were using 1 tool for orchestration and a different tool for configuration management.
450
00:32:07.380 --> 00:32:09.320
Trying to figure out how those 2 interacted
451
00:32:09.620 --> 00:32:10.919
was sometimes problematic,
452
00:32:11.700 --> 00:32:27.740
and so we actually ended up, starting to move to using SaltStack so that we could just consolidate all of those things and just have everything in 1 place so you didn't always have to jump back and forth between 2 different code bases and 2 completely different tools and programming languages and paradigms to try and understand
453
00:32:28.120 --> 00:32:39.585
what actually happens when you issue a certain command. Well and and and it's reassuring to hear what you're saying about it because we're we're in the process of trying to develop exactly what you're what you're describing along the lines of
454
00:32:40.045 --> 00:32:43.420
giving people short videos and tutorials around
455
00:32:43.880 --> 00:32:47.180
here's how you solve small problem x in solve.
456
00:32:47.880 --> 00:32:48.380
And,
457
00:32:48.965 --> 00:32:55.625
also emphasizing those around, here's how you solve a problem that you thought wasn't small but here's how you do it in 2 minutes with solve.
458
00:32:57.630 --> 00:33:09.005
That's that's very that sorry. That's very smart. Right? Because if they if they feel like it's big and they're shown, here's how to make it really easy, then that's gonna be tremendously satisfying for people.
459
00:33:10.184 --> 00:33:14.365
Yeah. I can't I can't tell you how many people have come back and done things like,
460
00:33:14.745 --> 00:33:15.804
like set up
461
00:33:16.510 --> 00:33:17.650
completely automatic
462
00:33:18.350 --> 00:33:25.524
code deployment or canary environments with salt that nobody I mean, you don't even have to touch it. Somebody pushes code
463
00:33:25.985 --> 00:33:29.044
and the canary environment gets deployed for them and
464
00:33:29.904 --> 00:33:34.050
they're done. And people are amazed at the fact that they do, that you could do that,
465
00:33:35.090 --> 00:33:39.030
in less than 10 lines of, I shouldn't, I shouldn't quote it.
466
00:33:40.370 --> 00:33:41.670
It depends on the tool.
467
00:33:43.715 --> 00:33:48.295
But in in minutes, you can set up these really complicated fully autonomic systems.
468
00:33:49.555 --> 00:33:53.095
And so yeah, we're we're definitely gonna be coming out with a lot more,
469
00:33:53.820 --> 00:33:55.280
instruction and documentation
470
00:33:55.580 --> 00:33:58.320
and videos around how to accomplish those things.
471
00:33:59.100 --> 00:33:59.920
Wow. Thomas,
472
00:34:00.220 --> 00:34:01.360
if you wouldn't mind,
473
00:34:01.885 --> 00:34:07.885
especially if it's if it's available on the web, after the fact, it'd be really cool if you could link that that,
474
00:34:08.285 --> 00:34:09.025
10 line
475
00:34:09.349 --> 00:34:10.329
canary environment
476
00:34:10.710 --> 00:34:12.089
deploy or thing
477
00:34:12.470 --> 00:34:18.935
into the show notes or hand it to us or whatever. If it's if it's assuming it's publicly available, because I think that would be a great,
478
00:34:19.495 --> 00:34:23.035
agreed opportunity for people to get a sense of how much salt can do.
479
00:34:24.215 --> 00:34:25.675
No. I'll definitely do that.
480
00:34:26.055 --> 00:34:28.920
Yeah. We we need to get that 1 out there. We set up,
481
00:34:29.480 --> 00:34:33.420
we've set this scenario up a lot. It's actually the core idea came from
482
00:34:33.960 --> 00:34:34.460
Wikipedia.
483
00:34:35.240 --> 00:34:36.059
And so,
484
00:34:37.444 --> 00:34:42.825
yeah, because because Wikipedia, as you probably know, uses Puppet for their configuration management,
485
00:34:43.765 --> 00:34:48.300
but they use, but they use Salt for their orchestration and deployment.
486
00:34:48.760 --> 00:34:50.940
And many of their and much of the configuration
487
00:34:51.240 --> 00:34:54.700
management that they use in newer deployments is pure Salt.
488
00:34:55.575 --> 00:34:58.875
And that they they were incredibly early adopters
489
00:34:59.575 --> 00:35:03.275
and they were the first ones to come back and say, hey, you know, I can
490
00:35:03.810 --> 00:35:09.110
use SALT's peer system to pull this off. And after looking at how they developed it,
491
00:35:09.490 --> 00:35:10.310
we developed,
492
00:35:10.930 --> 00:35:13.295
we developed the event reactor system, which
493
00:35:14.494 --> 00:35:17.315
which you've already mentioned and developed that system
494
00:35:17.775 --> 00:35:24.710
in such a way to make it to make the more complicated scenario that they built out something that was much easier, much more reproducible.
495
00:35:25.250 --> 00:35:29.270
And of course, you could do flipping anything with the event reactor system now.
496
00:35:31.315 --> 00:35:38.375
Very cool. So following on to to that that question, what are some common problems that you've seen people struggle with when using SaltStack?
497
00:35:41.089 --> 00:35:42.790
Getting back to their day job.
498
00:35:45.250 --> 00:35:49.964
Actually, in in all honesty, that is a fairly common problem that we see is that
499
00:35:50.425 --> 00:35:58.204
is that people will find salt and they will go down the rabbit hole of just creating some of the most fantastic things.
500
00:35:58.849 --> 00:36:07.829
And then they kind of poke their head up and go, oh, everyone else is the the people that come and they just beg to work for us and say, I wanna build these fantastic things all day long.
501
00:36:09.915 --> 00:36:14.494
So for instance, 1 of my favorites is that at Hewlett Packard, they developed a
502
00:36:15.355 --> 00:36:16.650
a complete app
503
00:36:16.970 --> 00:36:21.069
container deployment system around Salt. They put it together in 3 weeks.
504
00:36:21.609 --> 00:36:24.670
It is a stable app container deployment system.
505
00:36:25.045 --> 00:36:31.785
They tossed a lightweight GUI on top of it and so people inside people inside of Hewlett Packard for internal
506
00:36:32.380 --> 00:36:33.360
development purposes
507
00:36:33.660 --> 00:36:34.720
are able to
508
00:36:35.500 --> 00:36:36.640
just give
509
00:36:38.060 --> 00:36:42.694
a container definition and it's instantly deployed and it's all salt under the hood
510
00:36:43.395 --> 00:36:45.095
and salt calling out to LXC
511
00:36:45.635 --> 00:36:50.030
and to the extent where their users can use our Docker to LXC conversion
512
00:36:50.410 --> 00:36:50.910
components
513
00:36:51.530 --> 00:36:56.270
and just develop everything in Docker and plop it into Salt and it deploys LXC containers.
514
00:36:57.674 --> 00:37:05.775
And and that I'm trying to I'm I'm actually kind of being a punk and turning your question of what are the problems with salt into a salt's fantastic
515
00:37:08.710 --> 00:37:09.210
answer.
516
00:37:10.549 --> 00:37:21.435
Usually some of the things that people have hiccups with is that they might, you know, tread onto territory that's really, really new and run into some some bugs that we hadn't hit yet,
517
00:37:22.769 --> 00:37:26.069
or more of it is just kind of getting lost in the functionality.
518
00:37:27.170 --> 00:37:32.745
It's it's that people will pick up SALT and say, hey, I'm gonna try out salt for config management.
519
00:37:33.845 --> 00:37:38.105
And they don't they don't realize the salt is more of this total management
520
00:37:38.405 --> 00:37:38.905
system
521
00:37:39.730 --> 00:37:50.635
and, they start worrying too much about components that they don't need to worry about. So, I mean, I guess a lot of my answer there would be that if so if you're using salt
522
00:37:52.695
--> 00:38:00.920
and you're worried going, oh, well, I don't understand how all these different systems work. Even in the config management system, if you're using Salt and you go, oh,
523
00:38:01.380 --> 00:38:04.260
I'm intimidated by prereq and all of these,
524
00:38:04.924 --> 00:38:07.105
declarative components, which looks scary.
525
00:38:07.484 --> 00:38:09.984
Don't worry about it. You don't need to worry about those things.
526
00:38:10.605 --> 00:38:12.224
Just know that they're there.
527
00:38:13.400 --> 00:38:15.660
It's like the old adage, how do you eat an elephant
528
00:38:15.960 --> 00:38:17.579
1 bite at a time. Right?
529
00:38:18.359 --> 00:38:22.540
Right. Right. We we generally compare it to, like, a SWAT team,
530
00:38:23.065 --> 00:38:30.045
you know, or police a police department. You go in and your handgun will take care of the vast majority of situations, but you know
531
00:38:30.829 --> 00:38:36.609
that there's an assault rifle back there or tear gas or whatever you need to solve any problem you might run into.
532
00:38:37.230 --> 00:38:43.705
And that's kind of the benefit of salt that no matter what you run into, we will we we have a solution for you.
533
00:38:44.780 --> 00:38:54.640
That's great. And and with regards to your getting back to their day job problem, well, if if they really wanna do this kind of thing all the time, I mean, there are so many companies hiring for
534
00:38:55.085 --> 00:39:06.819
infrastructure as code or or DevOps or whatever you wanna call it. I don't think they'd have to look very hard if they wanted to change, change disciplines and and do this stuff for a living. Now I don't know I don't know how many are advertising
535
00:39:07.119 --> 00:39:20.345
explicitly for salt stack, but a lot of them are so desperate that if you found someone who said, I know salt and I can make it do wonders and and and, you know, wash your dishes and get your paper, I'm sure a lot of companies would be much more,
536
00:39:21.045 --> 00:39:24.300
open to using it given how desperately they're in need of the help.
537
00:39:25.240 --> 00:39:27.740
I gotta say 1 of my 1 of my favorite
538
00:39:28.200 --> 00:39:31.420
stories, or I should say 1 of my favorite kind of stories is
539
00:39:31.955 --> 00:39:34.375
is to hear about how many people
540
00:39:34.755 --> 00:39:36.695
have been introduced to solve who
541
00:39:36.995 --> 00:39:38.695
had minimal systems knowledge,
542
00:39:39.635 --> 00:39:41.255
minimal programming knowledge,
543
00:39:41.780 --> 00:39:46.280
and we're able to dramatically improve their career over a very short period of time.
544
00:39:46.660 --> 00:39:53.005
I mean, 1 of my favorites was somebody in our community who was working in a in a call center for a hotel chain
545
00:39:53.545 --> 00:39:55.085
that never done system administration
546
00:39:55.465 --> 00:39:55.965
before
547
00:39:56.825 --> 00:40:02.580
and heard about assault through just 1 of his friends said, hey. Salt's cool. Look at it. So we popped into IRC
548
00:40:03.440 --> 00:40:04.980
and studied our documentation
549
00:40:05.440 --> 00:40:07.300
and started helping people in IRC.
550
00:40:07.875 --> 00:40:10.375
8 months later, the guy's making 6 figures
551
00:40:10.835 --> 00:40:11.495
at a
552
00:40:12.515 --> 00:40:14.615
at a major tech company in Seattle
553
00:40:15.260 --> 00:40:16.240
to pull up SALT.
554
00:40:16.780 --> 00:40:22.320
You know, and it's like, oh, well, you just got a a, like a 4 x pay increase, buddy.
555
00:40:24.415 --> 00:40:26.595
But we have a ton of stories like that.
556
00:40:28.335 --> 00:40:32.755
Yeah. And and it's very it's it makes it very rewarding
557
00:40:34.180 --> 00:40:58.080
to be able to feel like you are actually helping people on a on a more personal level instead of just saying, hey, your servers work better. Yeah. I'll definitely say that 1 of the troubles that I've seen a couple times when I've been using solve is running into that analysis paralysis of, okay, the there's this particular problem I'm trying to solve, and now I see, okay, there are these 5 different ways I can use solve to solve it. So which 1 is going to be optimal for my particular
558
00:40:58.434 --> 00:40:58.934
situation.
559
00:40:59.395 --> 00:41:14.099
But sometimes you just kinda have to pick 1 and run with it. And then if it doesn't work, eventually, then you can go back to refactor that, which it will say SALT makes relatively easy because there is generally so little actual coding that you need to do to tie the different components together.
560
00:41:15.434 --> 00:41:18.875
Well and and, yeah, the analysis paralysis, I mean, we will have,
561
00:41:20.875 --> 00:41:22.635
I mean, I'll have all of some of our,
562
00:41:23.194 --> 00:41:23.934
our implementation
563
00:41:24.234 --> 00:41:25.214
and support
564
00:41:26.140 --> 00:41:30.160
people come up to me and say, oh, Tom. I don't know how to solve this problem over here.
565
00:41:30.460 --> 00:41:35.984
And and I, you know, I have no idea what's going on. I'll sit down and talk to him for 2 minutes and say, oh,
566
00:41:36.924 --> 00:41:38.145
don't you know about,
567
00:41:38.684 --> 00:41:40.305
using an external pillar?
568
00:41:41.645 --> 00:41:44.650
And they go, oh, that's an external pillar.
569
00:41:46.390 --> 00:41:53.935
Or yeah. Oh, and I'm like, oh, well, you're gonna write 15 lines of Python code and hook into their existing CMDB and you're done.
570
00:41:54.395 --> 00:41:59.055
And but, yes, we we see it all the time. It's that there's so much there that
571
00:41:59.590 --> 00:42:02.730
either you don't know about or if you do know about it's kind of
572
00:42:03.190 --> 00:42:08.010
this feeling of, I've gotta figure out what these 8 things do before I know which 1 to use.
573
00:42:08.935 --> 00:42:15.835
And it's it's really just a challenge of building a truly flexible system to be able to do that, and and I'm
hoping that
574
00:42:16.170 --> 00:42:20.109
us putting these videos out that are able to say, x y z, give
575
00:42:20.809 --> 00:42:23.630
give people these concrete examples
576
00:42:24.089 --> 00:42:24.589
of
577
00:42:25.225 --> 00:42:27.405
this is this is a good way to use
578
00:42:28.585 --> 00:42:36.050
I'm trying to think of something more esoteric inside of salt, but I've already used up so many of them. Oh, but, like, this is a good way to use returners
579
00:42:36.590 --> 00:42:43.455
for auditing, or this is a good way you know, this is a good use case for building an engine inside of Salt
580
00:42:44.015 --> 00:42:45.775
and using that. And,
581
00:42:46.975 --> 00:42:57.859
hopefully, we can get those we can get those rolling soon. We just we we we just finished up this release, and I imagine you guys, are familiar with how much of a pain it is to to finish up major releases.
582
00:42:58.560 --> 00:42:59.380
Oh, yes.
583
00:42:59.920 --> 00:43:00.420
Oh,
584
00:43:00.865 --> 00:43:03.765
and we just finished the conference. Conferences are murder.
585
00:43:04.065 --> 00:43:04.724
I mean,
586
00:43:05.744 --> 00:43:06.244
they're
587
00:43:07.505 --> 00:43:10.740
conferences are so fantastic, so much fun, but putting on a conference
588
00:43:11.380 --> 00:43:13.400
is just the most painful thing in the world.
589
00:43:14.580 --> 00:43:46.630
Well, I think I'm sure it's it's it's not unlike doing a major release. Right? From the outside, people are like, well, come on already, like, where is it, you know? Shouldn't you have been done 2 weeks ago? But there you are laboring in the trenches because it becomes such a fractal problem of achieving that last, you know, 2 feet to cross the finish line. It's like, oh, we just have these really critical problems we have to solve, and then we can do it. And and, it seems like putting on a conference is is very similar. From the outside, it seems like, so what's the big deal? You rent a venue, you get some speakers, it's easy. But there's this
590
00:43:47.029 --> 00:43:47.529
incredibly
591
00:43:47.829 --> 00:43:52.410
fractal amount of work behind the scenes to arrange all the logistics to make it happen.
592
00:43:53.109 --> 00:43:57.375
Oh, tell me about it. I mean, for our first conference, I had to write,
593
00:43:59.275 --> 00:44:03.135
call what was it? I had to write about a 150 pages of training
594
00:44:03.940 --> 00:44:05.160
manual content,
595
00:44:06.100 --> 00:44:09.080
in, like, a week and a half before that conference happened.
596
00:44:09.860 --> 00:44:13.905
And it's just just insane doing that stuff. So yeah.
597
00:44:18.845 --> 00:44:28.220
So what are some of the most surprising or interesting things that you've seen people do with SaltStack? Things that you just never would have even imagined possible with with, when you first wrote it.
598
00:44:29.535 --> 00:44:30.035
Oh,
599
00:44:33.934 --> 00:44:35.555
there's there's a lot.
600
00:44:37.800 -->
00:44:38.300
We
601
00:44:38.600 --> 00:44:39.660
we get used,
602
00:44:40.840 --> 00:44:42.619
a great deal for,
603
00:44:43.400 --> 00:44:49.135
probably the first 1 that surprised me when I found out about Salt being used to manage medical devices.
604
00:44:50.635 --> 00:44:51.035
That,
605
00:44:51.914 --> 00:44:54.070
that they were using salt on,
606
00:44:55.250 --> 00:44:57.030
on, embedded devices
607
00:44:57.650 --> 00:44:59.910
that were being put throughout a hospital.
608
00:45:00.530 --> 00:45:04.495
I don't even remember what they're monitoring but I mean it was monitoring something
609
00:45:05.515 --> 00:45:06.815
relative to the patients
610
00:45:07.195 --> 00:45:09.535
and then using salt as this data aggregator.
611
00:45:10.540 --> 00:45:15.440
And that was back in, that was back in 2012 when SALT was just a year old.
612
00:45:16.380 --> 00:45:16.880
And,
613
00:45:17.260 --> 00:45:18.560
we look at it now
614
00:45:21.165 --> 00:45:22.305
and, our
615
00:45:22.685 --> 00:45:25.905
current play and a lot of what we're working on for security mitigation
616
00:45:26.820 --> 00:45:27.320
has
617
00:45:28.180 --> 00:45:29.560
kinda surprised me.
618
00:45:30.020 --> 00:45:36.765
I can't tell you how proud I am of all the tweets that come out after heart bleed and shell shock that were people saying hey,
619
00:45:37.225 --> 00:45:41.725
I mitigated shell shock in 4 minutes with salt stack over 10,000
620
00:45:42.185 --> 00:45:42.685
servers.
621
00:45:43.630 --> 00:45:44.130
Wow.
622
00:45:45.790 --> 00:45:49.869
Oh, I love those. And I come back and I say, 4 minutes? What took it so long? I gotta
623
00:45:51.585 --> 00:45:56.805
and they say, oh, don't worry. Salt had actually done its work in a minute and a half, but the other time was testing.
624
00:45:59.590 --> 00:46:04.410
Yep. I definitely saw a number of those tweets come out after those events as well. It's definitely
625
00:46:04.870 --> 00:46:06.250
gratifying to see that.
626
00:46:07.244 --> 00:46:08.464
Yeah. It's very reassuring.
627
00:46:09.244 --> 00:46:09.744
And,
628
00:46:10.605 --> 00:46:15.025
but probably 1 1 that I'm that I'm really proud of most recently was,
629
00:46:16.119 --> 00:46:17.180
was that a nonprofit
630
00:46:17.640 --> 00:46:21.660
set up a bunch of weather monitoring stations using raspberry pies
631
00:46:22.080 --> 00:46:22.580
in,
632
00:46:23.319 --> 00:46:24.539
in South Africa.
633
00:46:25.175 --> 00:46:27.995
And these stations are used to give,
634
00:46:28.695 --> 00:46:30.155
to give early alerts
635
00:46:30.695 --> 00:46:33.595
to to locals who otherwise don't have access
636
00:46:33.900 --> 00:46:35.039
to this kind of information
637
00:46:35.660 --> 00:46:37.180
or don't have access to,
638
00:46:37.900 --> 00:46:39.599
to be scanning for this information.
639
00:46:40.380 --> 00:46:45.825
And so SALT is used to set up all of these weather stations and then the SALT event bus
640
00:46:46.445 --> 00:46:48.625
is used to channel information
641
00:46:49.085 --> 00:46:51.560
back to a central hub about what's going on.
642
00:46:52.600 --> 00:46:54.300
And and that whole
643
00:46:54.680 --> 00:46:55.740
Internet of things
644
00:46:56.040 --> 00:46:56.540
component
645
00:46:57.000 --> 00:46:57.500
is
646
00:46:58.200 --> 00:47:02.935
just something I'm really excited about. That we've got companies that are starting to use SALT
647
00:47:04.995 --> 00:47:07.015
for, for home automation purposes
648
00:47:07.950 --> 00:47:12.210
inside of, yeah, inside of just arbitrary home automation devices.
649
00:47:13.150 --> 00:47:17.490
And they love it. They come back and they say this is great because I've got a home automation device
650
00:47:18.515 --> 00:47:23.015
and everything is going through this standard interface that salt just gives me.
651
00:47:23.635 --> 00:47:26.540
And so, yeah, that that stuff is a lot more esoteric
652
00:47:27.640 --> 00:47:28.140
than,
653
00:47:28.440 --> 00:47:31.980
oh, we manage a big data center, which we do lots of that.
654
00:47:33.454 --> 00:47:42.434
So when you you talk about the Internet of Things in these weather stations and things like that, just for the purposes of those of us who are who are less salt savvy,
655
00:47:42.750 --> 00:47:47.010
would that be something like a minion running on on that Raspberry Pi?
656
00:47:48.190 --> 00:47:50.530
Yeah. Yeah. So so
657
00:47:51.005 --> 00:47:53.345
people will people will put a minion on the Raspberry
658
00:47:54.045 --> 00:47:56.445
Pi and then just have a master running back,
659
00:47:56.925 --> 00:48:01.040
either at an office somewhere or in a central, you know, some central location.
660
00:48:01.980 --> 00:48:04.960
And all of those minions are just reporting back into that master.
661
00:48:05.340 --> 00:48:09.835
And and that's it's actually interesting too the different ways I've seen people do it because
662
00:48:10.295 --> 00:48:15.515
a normal, you know, a classical salt deployment is that you've got this you've got the 0MQ,
663
00:48:16.869 --> 00:48:20.890
maintaining this cons this, TCP connection back to the master.
664
00:48:21.350 --> 00:48:24.890
But we recently introduced rate which is a UDP protocol
665
00:48:25.975 --> 00:48:28.955
and we've got the ability to and we recently
666
00:48:29.255 --> 00:48:35.109
not not too recently, it's maybe a year and a half old, the the scheduler in salt. The recent thing about salt's,
667
00:48:35.970 --> 00:48:38.869
schedulers that we added, we just added tons of,
668
00:48:39.970 --> 00:48:41.670
additions onto its capabilities
669
00:48:42.375 --> 00:48:45.515
so that your scheduling can be incredibly granular now.
670
00:48:46.375 --> 00:48:49.355
But a lot of people will just fire up that minion
671
00:48:49.740 --> 00:48:52.319
and say I don't care about the constant connection
672
00:48:53.099 --> 00:48:59.785
or the TCP connection isn't gonna do the right kind of traversal but I can I can route it with the u with Salt UDP protocol
673
00:49:00.725 --> 00:49:06.585
or I can just set the scheduler to have that minion act as this detached agent
674
00:49:07.250 --> 00:49:10.390
that is either pinging a master on a regular basis
675
00:49:10.690 --> 00:49:13.270
or we just take the master out of the equation altogether
676
00:49:13.809 --> 00:49:16.855
and all of those minions are just using Salt's returner interface
677
00:49:17.415 --> 00:49:19.755
face and the returner interface is Salt's,
678
00:49:20.215 --> 00:49:23.835
plugin interface that allows you to connect to virtually any database?
679
00:49:24.270 --> 00:49:26.610
And so they just use Salt's returner interface
680
00:49:27.230 --> 00:49:31.650
to run commands on a schedule and just have that go to some arbitrary database.
681
00:49:32.945 --> 00:49:33.445
And,
682
00:49:33.745 --> 00:49:35.845
and it's that flexibility, that fundamental
683
00:49:36.145 --> 00:49:36.645
decoupling
684
00:49:37.825 --> 00:49:43.220
that is really what allows SALT to work in so in such disparate environments.
685
00:49:44.960 --> 00:49:49.325
That's very cool. And I and I really do think that that is a distinguishing
686
00:49:49.625 --> 00:49:50.605
feature of salt
687
00:49:50.985 --> 00:49:53.325
versus almost any of the other configuration.
688
00:49:53.945 --> 00:49:58.365
Well, I can't call it configuration management system as you pointed out. That's that's a misnomer.
689
00:49:59.210 --> 00:50:00.270
Well, I guess
690
00:50:00.730 --> 00:50:04.430
that's a really distinguishing feature compared to other configuration
691
00:50:04.809 --> 00:50:07.390
management systems of which Salt is not 1.
692
00:50:07.690 --> 00:50:08.510
On the market,
693
00:50:09.035 --> 00:50:10.015
it it really sort
694
00:50:10.395 --> 00:50:13.855
of, like you say, lend it to be used in in areas,
695
00:50:14.795 --> 00:50:15.615
or environments
696
00:50:15.915 --> 00:50:17.455
where traditional Centimeters
697
00:50:17.755 --> 00:50:18.255
probably
698
00:50:18.940 --> 00:50:22.240
doesn't really can't really offer that much or
699
00:50:22.700 --> 00:50:28.000
bringing it to bear or bringing them to bear rather might be a little bit obtuse or or hard to get around.
700
00:50:28.434 --> 00:50:29.255
Very cool.
701
00:50:30.035 --> 00:50:39.839
Yeah. 1 1 thing that I've seen a few different implementations of that I thought was very interesting was actually using Salt as the monitoring and alerting platform for an infrastructure
702
00:50:40.140 --> 00:50:40.640
where,
703
00:50:41.180 --> 00:50:44.160
they had a scheduler set up to have the minions
704
00:50:44.645 --> 00:51:00.510
send back the, you know, CPU statistics, memory statistics back to a particular returner back end, whether it be a graphite database or a relational database or anything that you can see some on Elasticsearch. And then also using that same capabilities to actually generate alerts from that data,
705
00:51:00.910 -->
00:51:02.210
is definitely pretty cool.
706
00:51:02.925 --> 00:51:07.585
Yeah. Yeah. And that's and that's 1 of the big pushes that we're working on right now because,
707
00:51:08.845 --> 00:51:11.825
because we wanna make sure that we're able to
708
00:51:12.460 --> 00:51:14.480
really satisfy all those needs
709
00:51:15.260 --> 00:51:19.680
and make it much more streamlined to use SALT for your full stack of monitoring.
710
00:51:20.075 --> 00:51:26.895
And really it's why not? I mean, we've already got this execution library of modules that can already do all the monitoring for you.
711
00:51:29.640 --> 00:51:30.140
Great.
712
00:51:30.440 --> 00:51:31.740
Yeah. That that is that is great.
713
00:51:32.200 --> 00:51:39.975
Yeah. 1 of the things that people say about Salt's config management is they say Salt is a config management system in the same way that Google is a search engine.
714
00:51:40.915 --> 00:51:43.095
Or perhaps, emacs is an editor. Right?
715
00:51:46.700 --> 00:51:47.200
So,
716
00:51:49.099 --> 00:51:50.160
just to sort of,
717
00:51:50.780 --> 00:51:53.900
I guess, as an as an homage to 1 of my favorite,
718
00:51:54.220 --> 00:52:00.015
technical podcasts that, and partially inspired me to want to do this 1, we have,
719
00:52:00.495 --> 00:52:01.635
what we call the picks,
720
00:52:02.015 --> 00:52:10.240
that we'd like to do. And we'd like you to pick, you know, a few things. They can be technical or non technical, just things that you like. It can be
721
00:52:10.540 --> 00:52:15.425
software technology. It can be beer or a board game, something in a smartphone
722
00:52:15.805 --> 00:52:21.105
app, you know, whatever it is, just something you you think that's cool and you'd like to tell people about.
723
00:52:22.970 --> 00:52:26.990
Oh, something that I think is cool that I would like to tell people about.
724
00:52:30.475 --> 00:52:31.695
I'm a big fan
725
00:52:32.075 --> 00:52:33.375
of flow based programming.
726
00:52:35.595 --> 00:52:38.910
I think that flow based programming paradigm offers a
727
00:52:39.789 --> 00:52:41.410
completely different approach
728
00:52:42.030 --> 00:52:44.930
to how you think about computing and especially distributed,
729
00:52:45.309 --> 00:52:46.369
distributed systems.
730
00:52:46.785 --> 00:52:49.925
And we've been playing around with a lot trying to figure out a good way
731
00:52:50.545 --> 00:52:55.445
to implement flow based programming inside of salt in such a way that that optimizes things.
732
00:52:56.110 --> 00:53:00.130
So, I mean, that's that's definitely something that I would encourage people to look into.
733
00:53:01.230 --> 00:53:07.154
I'm trying to think of something that's nontechnical but I'm terrible because my entire life has been so incredibly obsessed
734
00:53:07.494 --> 00:53:07.994
with,
735
00:53:09.934 --> 00:53:11.075
with salt recently
736
00:53:11.934 --> 00:53:14.230
that, you know, I I I don't get out much.
737
00:53:14.950 --> 00:53:18.410
That's quite alright. I can definitely relate to that, but
738
00:53:18.869 --> 00:53:20.090
go go for the technical.
739
00:53:21.190 --> 00:53:21.690
Yeah.
740
00:53:23.255 --> 00:53:27.275
Yeah. So can you give us an example of of a flow based programming system?
741
00:53:29.335 --> 00:53:30.315
Yeah. So
742
00:53:31.310 --> 00:53:31.810
Salt,
743
00:53:32.350 --> 00:53:37.730
1 1 thing that's that, that we dug up to support Salt is something called IOflow.
744
00:53:38.655 --> 00:53:42.755
So I used to work in the US intelligence community as a contractor,
745
00:53:43.695 --> 00:53:46.994
and so I can neither confirm nor deny many things.
746
00:53:49.480 --> 00:53:51.900
But I became aware of this flow programming,
747
00:53:52.440 --> 00:53:56.300
platform that they were using to manage robotics called Ioflow.
748
00:53:58.095 --> 00:53:59.795
And, I knew the developer
749
00:54:00.175 --> 00:54:02.595
and, knew the right contact contacts.
750
00:54:03.455 --> 00:54:05.715
And, well, we call it Ioflow. Internally,
751
00:54:06.260 --> 00:54:07.720
it was something else.
752
00:54:08.660 --> 00:54:13.000
And, I was able to to coax it out into the open
753
00:54:13.515 --> 00:54:17.775
once it was renamed and scrubbed, you know. Right. Yep.
754
00:54:18.075 --> 00:54:18.575
And,
755
00:54:18.875 --> 00:54:20.415
and the ioflow project
756
00:54:20.795 --> 00:54:22.015
is an incredibly
757
00:54:22.315 --> 00:54:22.815
powerful
758
00:54:23.640 --> 00:54:24.460
flow programming
759
00:54:24.920 --> 00:54:25.420
system.
760
00:54:26.200 --> 00:54:27.420
It's pure Python
761
00:54:28.680 --> 00:54:29.180
and,
762
00:54:29.799 --> 00:54:36.325
I'm not gonna say that it's easy to learn how it works. It's kinda complicated because, I mean, it was written in the dark for,
763
00:54:37.025 --> 00:54:38.244
like, autonomous
764
00:54:38.944 --> 00:54:40.244
vehicles and submarines.
765
00:54:42.580 --> 00:54:45.480
But when it comes to building autonomous systems,
766
00:54:46.580 --> 00:54:52.065
it's it's incredibly useful. I mean, it takes, again, it takes a while to get your head around. All the documentation
767
00:54:52.765 --> 00:54:54.625
is obtuse and very academic,
768
00:54:55.325 --> 00:54:57.985
but it's just this incredibly cool system.
769
00:54:58.890 --> 00:55:01.870
And the whole idea behind flow programming is that
770
00:55:02.650 --> 00:55:05.790
you you've got this data bus and so
771
00:55:06.315 --> 00:55:11.775
all of the data for your application is on this data bus. You don't make objects with isolated data.
772
00:55:12.555 --> 00:55:16.550
And then you've got these black boxes. Ioflow calls them behaviors
773
00:55:17.330 --> 00:55:20.230
and then those behaviors access the data bus.
774
00:55:20.930 --> 00:55:29.435
And so the behaviors are restricted to only be able to get certain data off of the data bus and so then they can read and write certain data off of the data bus
775
00:55:29.815 -->
00:55:35.220
and then everything is all of these behaviors are just on this schedule checking the bus to say,
776
00:55:35.520 --> 00:55:39.300
did something change? Oh, that thing changed so this behavior should run.
777
00:55:40.244 --> 00:55:46.345
And it's just a fascinating programming paradigm and again I think a very, very, very powerful 1. Nioflo is a
778
00:55:46.724 --> 00:55:50.579
fantastic example of how it works. I'd really like to,
779
00:55:52.720 --> 00:55:55.619
to extend ioflow or build a system like ioflow,
780
00:55:57.134 --> 00:55:58.434
that better abstracted
781
00:55:58.734 --> 00:56:00.835
the concepts of flow based programming.
782
00:56:01.454 --> 00:56:03.394
But, I mean, 1 thing at a time.
783
00:56:04.015 --> 00:56:04.515
Absolutely.
784
00:56:05.060 --> 00:56:08.680
Is Ioflow open source? I see Googling it. I see
785
00:56:09.140 --> 00:56:11.000
a Microsoft Research Publications
786
00:56:11.300 --> 00:56:12.280
paper on it.
787
00:56:13.464 --> 00:56:17.964
Oh, you're probably spelling it wrong. It's I o f l o. There's no w.
788
00:56:18.265 --> 00:56:18.765
Ah.
789
00:56:19.704 --> 00:56:21.325
And it's Apache licensed.
790
00:56:21.990 --> 00:56:24.810
Oh, perfect. Thank you very much. That helps a lot.
791
00:56:25.270 --> 00:56:30.730
There we go. I found it. It's on GitHub. Super cool. Thank you. We'll put that in the show notes. That sounds really neat.
792
00:56:31.494 --> 00:56:33.115
Yeah. Definitely cool stuff.
793
00:56:35.175 --> 00:56:40.474
That's great. Don't feel any pressure. You gave us a really good 1 there. Do you have any other picks you'd like to cite?
794
00:56:42.099 --> 00:56:42.599
Oh,
795
00:56:43.059 --> 00:56:44.279
no. No. I don't know.
796
00:56:44.660 --> 00:56:48.119
Imagine Dragons are awesome, but everybody already knows that.
797
00:56:49.484 --> 00:56:54.705
Hey, man. That works. It's you know, music is 1 of those amazing things that that there there is literally,
798
00:56:55.165 --> 00:57:13.775
you know, there's something for everyone. So I I like Imagine Dragons too, and and who knows? You know, this this podcast reach could reach someone in outer Slavovia who's never heard of the Imagine Dragons. And now they'll be prompted to go on Spotify and give them a listen. So No. You just reached 1 because I've never heard of them. Well, so there you go. There you go.
799
00:57:14.870 --> 00:57:15.370
Oh,
800
00:57:15.830 --> 00:57:21.050
man. They they wail. You gotta check those guys out. Yeah. Well, as soon as we're off this call, go check it out.
801
00:57:21.510 --> 00:57:22.330
Very cool.
802
00:57:22.710 --> 00:57:24.615
So So I guess I'll move on to my picks.
803
00:57:24.994 --> 00:57:27.174
And the first pick that I will pick is
804
00:57:27.555 --> 00:57:35.470
a beer because I like good craft beer. When I was in California, 1 of the things I love about about craft beer is that as I, you know, as I get to travel,
805
00:57:36.090 --> 00:57:43.335
I really enjoy trying the craft beers that are only available in that region because some of it doesn't travel particularly well.
806
00:57:43.715 --> 00:57:45.575
And I had the opportunity to try
807
00:57:45.910 --> 00:57:49.130
a pint of stone Imperial Russian Stout,
808
00:57:49.750 --> 00:57:51.370
and it was really delicious.
809
00:57:52.310 --> 00:57:54.250
I I really love Stone Brewery.
810
00:57:54.735 --> 00:57:56.035
I find that their beers
811
00:57:56.495 --> 00:57:59.955
really sort of like hit the nail on the head with craft beer. Sometimes,
812
00:58:00.495 --> 00:58:09.900
you know, with with things like a stout or or there are few other varieties like this. There's so much complexity there that it's very easy for a brewer that's not particularly expert
813
00:58:10.280 --> 00:58:13.325
to have their beer come out kind of 1 note.
814
00:58:13.785 --> 00:58:21.725
And, this 1 is balanced perfectly. It's delicious malty goodness. It's it's great stuff. If you like dark beer,
815
00:58:22.090 --> 00:58:23.050
or even if you,
816
00:58:23.770 --> 00:58:29.870
think you don't like beer at all, but have only been fed to things like Budweiser, not to say there's anything wrong with Budweiser,
817
00:58:31.395 --> 00:58:34.535
or or very light, hoppy beers, you might give it a shot.
818
00:58:34.914 --> 00:58:39.095
The second pick that I have is actually a blog post
819
00:58:39.670 --> 00:58:40.170
by
820
00:58:40.470 --> 00:58:40.970
Arun
821
00:58:41.270 --> 00:58:41.770
Ravindran.
822
00:58:42.950 --> 00:58:48.250
I'm sure I mangled his name horribly being an insular American who can't pronounce foreign words,
823
00:58:49.315 --> 00:58:52.135
but it's called Python 1 liner games.
824
00:58:52.435 --> 00:58:58.670
I'll put the link in the show notes. And what I find to be really cool about this post, these are not games like,
825
00:58:59.530 --> 00:59:00.750
I don't know, you know,
826
00:59:01.290 --> 00:59:05.310
metal metal gear solid or anything like that. These are like computer games,
827
00:59:05.625 --> 00:59:07.805
like those of us who are old and crusty
828
00:59:08.185 --> 00:59:13.885
used to play in the days when we used to type them in in basic, you know, things like that. Things like,
829
00:59:14.490 --> 00:59:16.270
character generated mazes
830
00:59:16.970 --> 00:59:31.125
and snake games and, like, really just simplistic things. But they're 1 liners, and thus, I think they're very cool. I I'm a big fan of whimsy in programming and I think that, that we need to get it any anyway we can. So I really enjoyed that post.
831
00:59:33.140 --> 00:59:33.640
And
832
00:59:34.260 --> 00:59:41.935
the third thing that I wanna pick is I wanna pick the Boston Python meet up. I went for the first time a couple of weeks ago,
833
00:59:42.395 --> 00:59:57.840
and I really really enjoyed it. It was the the the quality of the of the content being presented was top notch, and I met some really cool people. And in general, I mean, if if
you're not involved in meetups near you, and chances are there is 1 near you, unless you also live in out of suburbia.
834
00:59:58.555 --> 01:00:05.055
It's it's definitely worth taking the time to drop by and say hello. You you you chances are you won't regret it.
835
01:00:05.915 --> 01:00:07.690
That's it for me. Great.
836
01:00:08.170 --> 01:00:12.990
So for my first pick, I'm going to pick a, somewhat self serving 1 that's,
837
01:00:13.690 --> 01:00:15.470
rather topical. So I actually
838
01:00:15.985 --> 01:00:20.965
recently wrote a couple of blog posts about my experience in using SaltStack to
839
01:00:21.265 --> 01:00:22.885
move a friend and
840
01:00:23.585 --> 01:00:24.085
client
841
01:00:24.420 --> 01:00:26.200
from Heroku onto AWS.
842
01:00:26.660 --> 01:00:29.480
So I'll put links to those 2 posts in the show notes.
843
01:00:30.180 --> 01:00:33.059
For my next pick, I'd like to choose a
844
01:00:33.795 --> 01:00:35.175
there's a tool called CaveQ
845
01:00:36.195 --> 01:00:45.480
that is a clipboard manager that I use on the KDE desktop on Linux. I believe it's cross platform to at least OSX and, I believe, Windows,
846
01:00:46.100 --> 01:00:52.714
but it is an amazing clipboard manager. It lets you maintain clipboard history. You can edit it. You can
847
01:00:53.095 --> 01:00:54.954
categorize it into separate tabs.
848
01:00:55.255 --> 01:00:58.315
So, for instance, I use EMAX as my main editor.
849
01:00:58.670 --> 01:01:07.890
And whenever you highlight a line in emacs or, you know, copy it into an emacs buffer, it also shows up in your clipboard. So it was just spamming my main clipboard
850
01:01:09.395 --> 01:01:19.420
and just pushing everything relevant back off of the, list. So I I was able to set up a filter so that anything coming from my emacs program went into its own tab, so it was still accessible and searchable,
851
01:01:20.039 --> 01:01:20.940
but it wasn't,
852
01:01:21.240 --> 01:01:23.019
it it wasn't polluting my main
853
01:01:23.799 --> 01:01:27.365
clipboard history. So it's a phenomenal phenomenal system,
854
01:01:27.984 --> 01:01:29.445
definitely worth checking out.
855
01:01:29.825 --> 01:01:32.885
And I'll also choose the Pelican static site generator.
856
01:01:33.270 --> 01:01:34.570
That's actually what I use
857
01:01:35.270 --> 01:01:48.025
to write and run my blog. It's a Python based static site generator, has a really good plug in system, has a really good repository of themes that make it really easy to get up and running with a decent looking website,
858
01:01:48.570 --> 01:01:53.390
has a lot of different capabilities. You can use it for a regular generating regular websites.
859
01:01:53.770 --> 01:01:55.869
It's primarily used for blogging, but
860
01:01:56.245 --> 01:01:56.745
phenomenal,
861
01:01:57.285 --> 01:01:59.865
very popular project. Definitely worth checking out.
862
01:02:00.485 --> 01:02:03.945
And last 1 I'll pick today is a website called Noisli,
863
01:02:04.245 --> 01:02:05.910
n o I s l I,
864
01:02:06.789 --> 01:02:07.690
and it is
865
01:02:08.069 --> 01:02:09.369
a white noise generator.
866
01:02:09.670 --> 01:02:12.490
So you go there, and there are a number of different
867
01:02:13.245 --> 01:02:25.080
sounds that you can choose, and you can adjust the volume. So for instance, you could say, I wanna have a little bit of wind, a little bit of crackling fire, and maybe a thunderstorm in the background. You could just mix and match from all those different sounds
868
01:02:25.700 --> 01:02:27.080
to make a really pleasant,
869
01:02:27.460 --> 01:02:30.315
ambient sound for you to listen to when you're really trying to focus.
870
01:02:30.875 --> 01:02:36.015
I found sometimes when I was listening to music while I program, you know, it could be great to be motivating, but sometimes
871
01:02:36.315 --> 01:02:40.930
they can just be a little bit too distracting, and I found Noisli to be perfect for those situations.
872
01:02:42.350 --> 01:02:43.090
Very cool.
873
01:02:43.550 --> 01:02:45.250
That is all I have for PIX.
874
01:02:46.270 --> 01:02:47.285
That's that's awesome.
875
01:02:47.924 --> 01:02:55.305
The the noisily thing sounds really neat. I mean, there there are certainly I I have a couple of old CDs that I've been using for, like, 20 years,
876
01:02:55.850 --> 01:03:04.430
called environments. And there's there's a couple in particular, like the ocean waves and and rain. And I I have yet to find any kind of digital
877
01:03:05.015 --> 01:03:07.195
thing that comes as close to,
878
01:03:08.375 --> 01:03:12.935
filling that niche for me as these recordings. I'll have to give Noisli a try and see if it,
879
01:03:13.690 --> 01:03:15.230
see if it passes muster.
880
01:03:16.010 --> 01:03:16.510
So
881
01:03:17.210 --> 01:03:19.070
that does it for this show.
882
01:03:19.690 --> 01:03:26.165
Thomas, is there anything that you'd like to plug or any appearances that you're gonna be having anytime soon
883
01:03:26.545 --> 01:03:29.605
that you'd like to let our listeners know about?
884
01:03:30.880 --> 01:03:31.859
Well, I mean,
885
01:03:32.400 --> 01:03:37.299
there I I would like to you you invited me to plug something, so I will.
886
01:03:40.465 --> 01:03:42.165
And you were talking about PIX.
887
01:03:42.785 --> 01:03:45.845
Another project that I put together is something called libnagle,
888
01:03:47.510 --> 01:03:48.550
which is a,
889
01:03:48.950 --> 01:03:49.609
which is,
890
01:03:50.230 --> 01:03:53.130
Python bindings to the libsodium library.
891
01:03:53.914 --> 01:03:56.494
And they've been abstracted in such a way to make cryptography
892
01:03:57.115 --> 01:03:59.295
incredibly safe and easy and
893
01:04:00.234 --> 01:04:01.775
incredibly easy to use.
894
01:04:02.450 --> 01:04:02.690
So,
895
01:04:03.250 --> 01:04:04.630
you know, if you ever need
896
01:04:05.410 --> 01:04:08.230
super strong cryptography, take a look at libnacl.
897
01:04:09.970 --> 01:04:10.790
Yeah, libnacl.
898
01:04:12.675 --> 01:04:13.155
But,
899
01:04:13.475 --> 01:04:17.015
but, yeah, we've got, I mean, we're gonna be we're gonna be a PyCon.
900
01:04:18.355 --> 01:04:19.495
We're over at
901
01:04:20.420 --> 01:04:23.240
the, what is it, the Microsoft Build Conference.
902
01:04:24.740 --> 01:04:26.600
Yeah. Salt's all over the place.
903
01:04:29.025 --> 01:04:36.645
So, yeah, keep an eye open on what we're doing. Okay. And for anybody who'd like to follow you in the SALT project, where can they find you?
904
01:04:37.599 --> 01:04:38.900
Well, I am thatch45
905
01:04:39.520 --> 01:04:40.180
on GitHub.
906
01:04:40.560 --> 01:04:41.540
I am thatch45
907
01:04:43.440 --> 01:04:43.940
on
908
01:04:46.065 --> 01:04:50.884
Twitter. I don't I don't tweet very much. I keep trying to tweet more but I'm a bad tweeter.
909
01:04:54.720 --> 01:05:00.820
But, yeah, definitely follow the Salt Project which is at GitHub, Salt Stack, Salt Stack slash Salt
910
01:05:01.335 --> 01:05:04.234
and we've got a bunch of other really cool projects in there.
911
01:05:05.095 --> 01:05:05.595
And,
912
01:05:06.135 --> 01:05:10.474
yeah, join the community. We're we love we love merging code. We,
913
01:05:11.310 --> 01:05:15.810
and we work really hard to have a nurturing and a very positive community that helps people
914
01:05:16.190 --> 01:05:17.250
learn how to improve
915
01:05:17.710 --> 01:05:20.115
which has worked out really well for us. So,
916
01:05:20.494 --> 01:05:21.234
yeah, definitely
917
01:05:21.775 --> 01:05:22.674
look us up.
918
01:05:23.375 --> 01:05:28.115
That's great. I I just have to ask, sir, what, what's the 45 in THATCH 45?
919
01:05:31.770 --> 01:05:32.270
So
920
01:05:33.450 --> 01:05:35.230
there's there's a bit of a story.
921
01:05:37.954 --> 01:05:41.815
45 is my lucky number because when I was 10,
922
01:05:43.395 --> 01:05:46.695
I was playing Legend of Zelda on the 8 bit Nintendo,
923
01:05:47.860 --> 01:05:54.520
and I closed my eyes and named my Zelda character. And he ended up and Link ended up being named 45.
924
01:05:55.060 --> 01:05:55.960
Oh, that's awesome.
925
01:05:56.315 --> 01:05:59.295
And it was the best game of Zelda that I'd ever played.
926
01:05:59.835 --> 01:06:02.895
I got I got through, like, the 5th labyrinth without dying.
927
01:06:03.730 --> 01:06:05.590
And so I just always used 45.
928
01:06:07.330 --> 01:06:09.830
That's awesome. Thank you. I'm very glad I asked.
929
01:06:12.725 --> 01:06:22.185
Well, thank you very much for listening. Thomas, thank you for joining us, and we are looking forward to bringing you another great episode as soon as possible.