text stringlengths 9 408 |
|---|
[312.58 --> 313.32] They're super fast. |
[313.40 --> 324.42] They have native SSD storage, 40 gigabit network, totally easy to use cloud manager, really simple to take snapshots and get an idea of the last time your computer, or I should say Linode, was backed up. |
[324.42 --> 331.20] You can really simplify your infrastructure while also reaping the benefits of great performance at a great price. |
[331.66 --> 336.14] Linode costs 30% to 50% less than AWS or Google Cloud or Azure. |
[336.66 --> 341.22] And it really works well if you want to just blend a little bit of on-premises and cloud as well. |
[341.34 --> 342.56] That's how I use it for NextCloud. |
[342.92 --> 345.72] I have a cloud component to my NextCloud setup on Linode. |
[346.08 --> 351.14] And then the big bulk of the storage, like the archival stuff, it's all here locally on my LAN. |
[351.26 --> 352.58] It works fantastic that way. |
[352.58 --> 356.46] And with 11 data centers worldwide, you're going to find just the right spot to deploy. |
[356.68 --> 364.78] And you'll rest easy knowing that Linode's rocking fast and has great monitoring tools that can alert you to problems before you even notice them. |
[365.04 --> 369.02] Of course, these things are really important, but performance matters as well. |
[369.10 --> 370.58] And Linode has you covered there too. |
[371.02 --> 376.40] Cloud Spectator recently did a study of the different cloud providers, like all of them. |
[377.02 --> 379.46] Dio, Amazon, Google. |
[379.46 --> 383.78] Google looked at Azure, all of them, put them in there, and saw who was the fastest. |
[384.28 --> 392.50] And one of the things that really makes Linode stand out is their dedicated CPU rigs have AMD EPYC processors that are just cranking faster than the other providers. |
[392.50 --> 398.56] And Linode's disk storage is super fast, so you can feed those processors faster than the other providers. |
[398.56 --> 411.02] And what Cloud Spectator survey shows is that not only does Linode have the best CPU and disk performance, but it has the best continuous performance as well, which really matters when you have large jobs that need processing or you're getting a lot of traffic. |
[411.18 --> 412.56] You need that sustained performance. |
[413.46 --> 417.16] I mean, Linode started in 2003 as one of the first companies in cloud computing. |
[417.16 --> 419.08] So they really know what they're doing. |
[419.28 --> 424.76] They're independently owned and founded on a love for Linux open source technologies and the community that surrounds them. |
[425.06 --> 426.94] So just go try what I'm talking about. |
[427.12 --> 428.86] I've told you about the object storage before. |
[428.98 --> 430.66] I've told you about the cloud firewall before. |
[430.74 --> 432.34] There's a lot to check out with Linode. |
[432.48 --> 435.20] And what they've chosen to do, they do really well. |
[435.50 --> 436.72] So go spend that $100. |
[437.44 --> 439.32] Linode.com slash SSH. |
[439.46 --> 442.04] Go see what I've been talking about and support the show. |
[442.38 --> 444.38] Linode.com slash SSH. |
[444.38 --> 452.00] Well, I'm delighted to welcome to the show somebody whose work I've been following for many years as an Ansible user. |
[452.26 --> 454.12] We have Jeff Geerling on the show today. |
[454.22 --> 454.72] Welcome, Jeff. |
[455.18 --> 456.24] Thanks for having me. |
[456.60 --> 457.50] Thank you for being here. |
[457.86 --> 462.18] And more recently, of course, a YouTube extraordinaire content creator. |
[462.62 --> 464.04] Yeah, that's how I came to know you. |
[464.38 --> 464.66] Yeah. |
[465.14 --> 468.32] So you've been doing a lot of videos lately on the Raspberry Pi 4 compute module. |
[468.42 --> 469.90] I thought we'd talk to you a little bit about that. |
[469.90 --> 478.42] But before we get to that side of the discussion, I wanted to sort of talk to you a little bit about what I knew you for first, which was Ansible. |
[478.64 --> 483.54] So you have a really rather excellent 101 getting started course. |
[483.54 --> 494.10] Before Jeff Geerling existed and created this, you know, de facto guide for people getting started with Ansible, how did you get involved with the project? |
[494.10 --> 500.10] I started off by having a few servers, then many servers, and then dozens of servers. |
[500.36 --> 506.32] And once I went from many to dozens, I realized I had to switch to some sort of configuration management system. |
[507.12 --> 509.66] And at the time, Ansible was pretty much brand new. |
[510.14 --> 516.76] That was 2012, 2013, when I was making that transition from shell scripts and runbooks to something more formal. |
[516.76 --> 519.62] So I tried out Chef, but I'm not a Ruby developer. |
[520.32 --> 522.18] And I didn't really like it. |
[522.38 --> 529.74] It felt too much like programming to me and learning Ruby when, you know, I did PHP and Node.js and things like that. |
[530.14 --> 533.20] So I got into Ansible at that time. |
[533.52 --> 538.34] And at the time, it was so simple that you could pick everything up in a day. |
[538.36 --> 542.48] And it was focused really on just Linux administration, not all the other things that it does today. |
[542.48 --> 547.82] Um, but the documentation was great, but there wasn't a ton of examples out there. |
[547.98 --> 551.36] So I just started blogging about my experiences. |
[551.36 --> 554.00] And then I realized that there wasn't a book for it. |
[554.10 --> 561.80] So I put my blog post together into like a 50 page sampler thing and stuck it onto LeanPub, |
[561.90 --> 566.20] which was also pretty new at the time, and started self-publishing this little ebook. |
[566.20 --> 572.78] And my goal was to maybe sell 100 copies or 200 copies and, you know, help some people learn Ansible. |
[573.10 --> 577.96] And lo and behold, a couple of years later, since it was one of the first books on Ansible, |
[578.08 --> 580.28] it became one of the most purchased books. |
[580.50 --> 584.20] And to this point, I don't remember how many tens of thousands of books I've sold, |
[584.34 --> 587.46] but lots of thousands of books have been sold. |
[588.10 --> 594.90] It was the number one bestseller for infrastructure automation for a number of periods on Amazon. |
[594.90 --> 600.82] And has been in the top five, top 10 books on LeanPub for years now, too. |
[601.18 --> 601.54] Congratulations. |
[602.30 --> 602.86] Yeah, thanks. |
[603.06 --> 603.88] I don't doubt it. |
[604.10 --> 609.62] You know, every time you search for anything related to a specific role or something like |
[609.62 --> 613.86] that for Ansible, you're looking, there's a Jeff Geerling role in there in Ansible Galaxy. |
[614.28 --> 618.54] So some of our listeners will be familiar with Ansible, but some won't. |
[618.64 --> 622.12] So what's your quick kind of elevator pitch of what Ansible is and does? |
[622.12 --> 627.36] There's an XKCD about whether or not you should automate something. |
[628.06 --> 631.14] And I think that that's a good illustration of what Ansible is. |
[631.26 --> 635.68] Once you reach the point where you're doing something, maybe to a group of computers or |
[635.68 --> 640.34] to network switches or to servers, or even I use it to manage my own computer. |
[640.46 --> 645.40] If you're doing a repetitive task that can be automated, Ansible can automate that. |
[645.60 --> 647.94] Almost anything in the world that has to do with technology. |
[647.94 --> 650.82] So that's what it does. |
[650.94 --> 652.02] And it's very simple. |
[652.22 --> 657.54] That's the big selling point for it compared to other tools is it uses YAML configuration, |
[657.92 --> 660.66] which is very approachable, very easy to learn. |
[661.10 --> 666.74] And that's why I liked it over the other solutions at the time, Chef and Puppet that I was looking at. |
[666.74 --> 674.54] People back in 2012, 13 time were just moaning about how YAML was so complicated with its white space. |
[674.60 --> 681.24] And I never quite understood the hate, to be honest with you, because JSON, people say, |
[681.42 --> 682.66] oh, I'd much rather write JSON. |
[682.82 --> 683.80] I'm like, are you mad? |
[685.12 --> 686.52] YAML is way easier to work with. |
[686.52 --> 695.92] Yeah, I think a lot of people maybe don't, they aren't used to having like a code editor do formatting for them and things like that. |
[696.00 --> 701.66] It's much more common nowadays, especially in the infrastructure space than it was 10 years ago. |
[701.90 --> 703.44] And I think that's the biggest difference. |
[703.58 --> 709.52] Nowadays, YAML, people complain about it mostly because they see people do things that you shouldn't do in YAML. |
[709.52 --> 712.98] But back then it was more the syntax and the formatting. |
[713.16 --> 717.56] They're like, I could put in anything in JSON or God forbid, XML. |
[718.56 --> 720.52] But, you know, YAML is going to complain about it. |
[720.64 --> 725.38] And I think nowadays we're past the formatting stage and we're into the, you know, |
[725.46 --> 730.64] what could be a next generation format for configuration that's even better than YAML because it does have shortcomings. |
[730.82 --> 739.30] But it's, in my opinion, it's a thousand times better than JSON, XML and SOAP and all the other protocols we used to have to know to be able to configure things. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.