text stringlengths 9 408 |
|---|
• Upgrading Ansible to version 3 requires careful consideration due to changes in how modules and plugins are managed. |
• The introduction of collections, which break down large codebases into smaller, maintainable components. |
• Challenges in making collections work together seamlessly, resulting in potential "growing pains" for users. |
• Benefits of the new system include flexibility and the ability to install only necessary modules. |
• Recommended resources for learning about Ansible 3 changes include the official documentation, release notes, and a guide for upgrading. |
• The speaker's book on Ansible has been updated to reflect the changes in version 3. |
• The Compute Module 4 has a standard PCI Express slot on its I/O board. |
• This allows for building custom boards with different form factors and features, such as M.2 slots for storage and LTE modems. |
• Broadcom contacted the speaker after seeing their work and offered to send them a hardware RAID controller card to test. |
• The speaker successfully implemented a live stream with 16 hard drives plugged into the Pi using the card. |
• Performance was limited by the X1 PCI Express lane, which only supports up to 5 gigabits per second (3.2 gigabits in real-world tests). |
• The Compute Module may be an indication of where future Raspberry Pi boards are headed, potentially including the Pi 5. |
• The advantages of using the Compute Module include leveraging the existing Raspberry Pi ecosystem and community. |
• Limitations of Raspberry Pi's network throughput |
• Desired improvements in future Pi models (PCI bandwidth and CPU speed) |
• Comparison to Apple M series performance |
• Self-hosting projects, including pydramble.com and potential use of Starlink for hosting services |
• ISP uptime and reliability concerns |
• Testing Starlink for redundancy and link aggregation |
• Host is using various devices for different tasks, including Raspberry Pi, x86 server, and Mac Mini. |
• The host's Mac Mini is outdated but still serves as primary network storage device. |
• The host has a significant amount of data on their LAN, with 24 terabytes online and approximately 60 in-house. |
• A "Petabyte Pi" project is discussed, where the goal is to build a Raspberry Pi controlling a petabyte of storage. |
• The conversation also touches on hardware requirements for such a project and potential uses for a large storage device. |
• Jeff's guest appearance on the show |
• Upcoming content mentioned but not revealed to the host |
• Promotion of Cloud Guru and links to their social media channels |
• SelfHosted members benefits and limited ad feed |
• Contact information for the show, including Twitter handles and website URL. |
[0.00 --> 4.96] Coming up on today's show, we have Jeff Geerling. You may know him as Geerling Guy in Ansible Galaxy. |
[5.42 --> 8.62] He's also on a bunch of work recently with the Raspberry Pi. |
[9.48 --> 16.28] Chris loses his mind a little bit when Jeff tells him how he hooked up 16, yes, 16 drives to a Raspberry Pi. |
[16.70 --> 17.22] I'm Alex. |
[17.64 --> 19.82] I'm Chris, and this is Self-Hosted 41. |
[21.06 --> 25.40] Alex, we have a lot to talk about today, and we also have a special guest. |
[25.40 --> 33.12] We do indeed, yes. We have Geerling Guy, Jeff Geerling, the Raspberry Pi Ansible maestro, all the sorts of superlatives. |
[33.74 --> 37.52] My new YouTube habit. I love what he's putting out. |
[37.58 --> 38.78] Yeah, I thought you might like him. |
[40.04 --> 43.92] Yeah, I do. I want to say thanks to a Cloud Guru for sponsoring this episode. |
[44.06 --> 47.28] They are the leader in learning for the cloud, Linux, and other modern tech skills. |
[47.38 --> 49.52] Get hundreds of courses, thousands of hands-on labs. |
[49.94 --> 53.66] Get certified, get hired, get learning at cloudguru.com. |
[53.66 --> 58.54] So the interview really will be the bulk of the show today, because there's so many great things we get into. |
[58.96 --> 64.72] But before we start, I kind of wanted to chat with you about Nabucasa buying ESP Home. |
[65.24 --> 65.94] How do you feel about it? |
[65.98 --> 70.18] I mean, when I first heard the news, I was like, oh, I wasn't quite sure how to feel. |
[70.18 --> 79.32] And then some more details trickled out about how the original creator, Otto, was, you know, basically burning out. |
[79.32 --> 84.56] And I think overall, it's a great way to save an open source project. |
[84.56 --> 91.56] That is one of my personal favorite ways to configure, you know, ESP boards. |
[92.24 --> 94.88] It's a clear value for the Home Assistant community. |
[95.60 --> 97.34] And this was, you're right. |
[97.42 --> 100.62] I had my first read of this was sort of like, I'm not so sure. |
[100.62 --> 103.10] Because they're a small team with a lot to do. |
[103.42 --> 110.28] But when you read between the lines, it seems pretty clear that Otto was about to hit the nope out button. |
[110.88 --> 115.46] And the project would have been left without its leader and lead developer. |
[116.10 --> 119.26] This is kind of nice because this gives the project room to grow. |
[119.44 --> 121.12] It'll bring in some new contributors. |
[121.80 --> 123.16] Otto is taken care of. |
[123.46 --> 126.90] He's able to participate if he likes, but, you know, he's going to focus on life for a bit. |
[126.94 --> 128.26] He's shutting down the Patreon account. |
[128.26 --> 131.24] He doesn't have to worry about the management side of things. |
[131.88 --> 134.72] And it continues to be a free software project. |
[135.48 --> 141.68] And if anything, I would expect it will be even tighter integrated into Home Assistant now. |
[141.94 --> 142.98] We're seeing some of that already. |
[143.48 --> 152.16] Frank, one of the main developers for Home Assistant, has already made some significant improvements to the VS Code plugins for how that interfaces with ESP Home. |
[152.56 --> 155.44] So there's some autocomplete stuff coming and things like that. |
[155.44 --> 159.46] But let's just back up a little bit and explain what ESP Home is. |
[160.10 --> 168.16] So the way I got started with it was I was programming these ESP8266 single board computers, if you like. |
[168.24 --> 171.80] They're kind of in the same space as an Arduino, more than a Raspberry Pi. |
[172.06 --> 173.34] So they don't run a full OS. |
[173.42 --> 175.56] They actually run a precompiled firmware. |
[175.56 --> 186.20] And that used to require writing an Arduino sketch and uploading it to the board and, you know, all the stuff that comes with the Arduino IDE and universe and that kind of thing. |
[186.74 --> 194.48] And what ESP Home does, and it is pure magic in my opinion, is you define the firmware as a YAML file. |
[194.48 --> 205.24] You add a couple of modules here with a couple of lines to, you know, enable Wi-Fi and then another couple of lines to enable logging and then another couple of lines to enable the Home Assistant API, for example. |
[205.96 --> 217.28] And then you flash that binary that is generated from the YAML file onto the ESP8266 without having to write a single line of C code or whatever the Arduino equivalent would be. |
[217.28 --> 219.90] And it just makes it so approachable. |
[220.36 --> 223.84] Yeah, and there's so many devices that run off this type of firmware out there. |
[224.40 --> 230.04] And you can really see long term the value that Home Assistant, if Home Assistant can make this even simpler. |
[230.84 --> 238.88] Imagine a future, if you would, Alex, where Home Assistant could even auto detect devices and guide the user through generating the firmwares. |
[239.18 --> 244.08] And maybe even has a way to deploy it with some DNS magic or something, depending on the device. |
[244.08 --> 249.62] But they could really make this a whole inclusive package at some point. |
[250.14 --> 250.66] Absolutely, they could. |
[250.76 --> 260.44] Because with this acquisition, Nabu Kasa now owns the copyright to Otto's Code and therefore the ESPHome organization on GitHub and Docker as well. |
[260.74 --> 263.68] Yeah, and ESPHome.io is a great resource. |
[263.84 --> 266.64] So if you want to learn a little bit more, go check out ESPHome.io. |
[266.74 --> 268.82] And of course, we'll have a link in the notes. |
[269.36 --> 271.80] Which, as always, you can find at selfhosted.show. |
[271.80 --> 275.74] Linode.com slash SSH. |
[275.86 --> 281.16] Linode.com slash SSH gives you a $100 60-day credit towards a new account at Linode. |
[281.36 --> 283.18] And of course, it supports the show. |
[284.04 --> 285.78] Linode is our cloud hosting provider. |
[285.98 --> 289.42] Anything we want to try out or anything we put in production, we put it up on Linode. |
[289.58 --> 290.84] We get emails into the show. |
[290.92 --> 292.40] We try stuff out on Linode. |
[292.54 --> 294.18] It's really quick to get going. |
[294.30 --> 296.20] But also, it's because it's fast. |
[296.38 --> 298.74] We know it's just going to get done really quick. |
[298.74 --> 302.20] And sometimes you just want to prototype something as fast as possible. |
[302.42 --> 307.16] Now, we host all of our major infrastructure for Jupyter Broadcasting 3.0 on Linode, of course. |
[307.82 --> 312.52] But even the stuff that never makes it public, that never is listener-facing, we run on Linode as well. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.