Rebuilding my homelab: Suffering as a service • Hacker News Board

Re: Rebuilding my homelab: Suffering as a service

#21

Post by miyuru » Sat, May 18, 2024, 2:02 PM UTC

xena wrote: post #15

chadsix wrote: post #10

This was a tremendous write-up. I appreciate the detail including your ingressd setup. I agree, though, that this is a pain. It's for this reason that we made Cloud Seeder [1] so you can have hands-free setup of your homelab and IPv6rs for painless ingress [2] [1] https://github.com/ipv6rslimited/cloudseeder [2] https://ipv6.rs

I'd set up IPv6 on there, but the problem is that I use Flannel (which is IPv4 only) and my 8 gigabit fiber ISP only gives me IPv4 connectivity. I'll look into more details, but I've slightly given up on IPv6 for now. Maybe I'll set up Calico or something, but IPv6 seems to have been made artificially difficult by everything in the stack. I hate it.

Can you add AAAA records to cdn.xeiaso.net as well.

It seems to have the same IPv4 from fly.io as the main domain, but you forgot to add it to the CDN subdomain.

Re: Rebuilding my homelab: Suffering as a service

#22

Post by xena » Sat, May 18, 2024, 2:04 PM UTC

miyuru wrote: post #21

xena wrote: post #15

Earlier quoted context omitted.

I'd set up IPv6 on there, but the problem is that I use Flannel (which is IPv4 only) and my 8 gigabit fiber ISP only gives me IPv4 connectivity. I'll look into more details, but I've slightly given up on IPv6 for now. Maybe I'll set up Calico or something, but IPv6 seems to have been made artificially difficult by everything in the stack. I hate it.

Can you add AAAA records to cdn.xeiaso.net as well. It seems to have the same IPv4 from fly.io as the main domain, but you forgot to add it to the CDN subdomain.

Uhhhh, I thought I did that! I'm gonna go fix that, sorry!

Re: Rebuilding my homelab: Suffering as a service

#23

Post by moritonal » Sat, May 18, 2024, 2:05 PM UTC

Good place to tell people about CKD8S. It acts as an IaC translating TS to K3 Yalm greatly simplifying working in K8. Developers shouldn't be writing YAML.

Re: Rebuilding my homelab: Suffering as a service

#24

Post by jjbinx007 » Sat, May 18, 2024, 2:06 PM UTC

shrubble wrote: post #13

PaulHoule wrote: post #2

No. Real suffering in the homelab is getting N 20 year old servers and swapping parts between them to get N-M servers that work. I feel like the project will be successful if I get all the drives wiped and I am within site of that although I discovered the wiping was going to be a process of triage: some drives did not spin up, one drive took 14 hours to wipe whereas a normal drive would take about 30 minutes. My col…

That is retrocomputing, not homelabbing. Look into the sub-$200 Intel N100 based systems with 16GB RAM.

I recently bought 2 of these and they are EXCELLENT! I can leave them running 24/7 without worrying about how much electricity they're using. The performance, flexibility and reliability far exceeds the Raspberry Pis that are confined the to cupboard and they're probably a fair bit faster than my old desktop PCs that I rarely switch on any more.

I've gone uber-minimalist and only have NVME drives attached via USB-3. One's connected via ethernet, the other has a wifi connection. Personally I don't need any more and I've retired my old servers for now.

Re: Rebuilding my homelab: Suffering as a service

#25

Post by walterbell » Sat, May 18, 2024, 2:07 PM UTC

> I ran a poll on Mastodon to see what people wanted me to do. The results were overwhelmingly in favor of Rocky Linux. As an online "content creator", who am I to not give the people what they want?

Truman would be proud!

> the NAS. It has all of our media and backups on it. It runs Plex and a few other services, mostly managed by docker compose.

Does the NAS run NixOS?

Re: Rebuilding my homelab: Suffering as a service

#26

Post by chadsix » Sat, May 18, 2024, 2:09 PM UTC

xena wrote: post #18

chadsix wrote: post #17

Earlier quoted context omitted.

> 8 gigabit fiber ISP only gives me IPv4 connectivity. Just like my ISP (but not 8 gbit!). Luckily, IPv6rs actually tunnels through IPv4 (or 6) and provides an IPv6 address. You don't need one to start! I don't know the ins and outs for flannel, but maybe you could setup IPv4 internally and use IPv6 (and an IPv4 Reverse Proxy) for the public internet? I agree, though, IPv6 on its own can be hard but thanks to WireGua…

Can you email me at hackernews@xeserv.us? I'd like to hear more.

I'm on it! Looking forward to the dialogue!

Re: Rebuilding my homelab: Suffering as a service

#27

Post by sgarland » Sat, May 18, 2024, 2:10 PM UTC

> What's not fine is how you prevent Ansible from running the same command over and over. You need to make a folder full of empty semaphore files that get touched when the command runs...

> One of my patrons pointed out that I need to use Ansible conditionals in order to prevent these same commands from running over and over.

Yes-ish. As I'm pretty sure OP figured out due to the pre-made roles comment, there exists a `community.general.dnf_config_manager` module that would handle this specific issue. As a general rule in Ansible, as ansible-lint [0] will tell you, is if you're using `ansible.builtin.{command, shell}`, there's a decent chance you're Doing It Wrong (TM).

The biggest problem I have with Ansible (and I say this as someone who uses it extensively with Packer to build VM templates for Proxmox in my homelab) is that, like its underlying Python, there are a dozen ways to do anything. For example, if you wanted to perform a set of tasks depending on arbitrary conditions, you could:

0. Use `when` and rely on things like named host groups

1. Use `when` and rely on manually handling state throughout plays

2. Use handlers

3. Break down the tasks into logically-scoped roles, and manually call roles

4. Do #3, but rely on Ansible's role dependencies instead

5. Use semaphore files / `creates` as OP did

6. Probably something else

[0]: https://github.com/ansible/ansible-lint

Re: Rebuilding my homelab: Suffering as a service

#28

Post by xena » Sat, May 18, 2024, 2:11 PM UTC

xena wrote: post #22

miyuru wrote: post #21

Earlier quoted context omitted.

Can you add AAAA records to cdn.xeiaso.net as well. It seems to have the same IPv4 from fly.io as the main domain, but you forgot to add it to the CDN subdomain.

Uhhhh, I thought I did that! I'm gonna go fix that, sorry!

Did that fix it?

Re: Rebuilding my homelab: Suffering as a service

#29

Post by sgarland » Sat, May 18, 2024, 2:12 PM UTC

moritonal wrote: post #23

Good place to tell people about CKD8S. It acts as an IaC translating TS to K3 Yalm greatly simplifying working in K8. Developers shouldn't be writing YAML.

Hot take: infrastructure shouldn't be created imperatively; you wind up with fun surprises too often.

Hotter take: devs shouldn't be running infra at all, DevOps was a mistake. Return to specialized roles.

Re: Rebuilding my homelab: Suffering as a service

#30

Post by distances » Sat, May 18, 2024, 2:15 PM UTC

jjbinx007 wrote: post #24

shrubble wrote: post #13

Earlier quoted context omitted.

That is retrocomputing, not homelabbing. Look into the sub-$200 Intel N100 based systems with 16GB RAM.

I recently bought 2 of these and they are EXCELLENT! I can leave them running 24/7 without worrying about how much electricity they're using. The performance, flexibility and reliability far exceeds the Raspberry Pis that are confined the to cupboard and they're probably a fair bit faster than my old desktop PCs that I rarely switch on any more. I've gone uber-minimalist and only have NVME drives attached via USB-3.…

> reliability far exceeds the Raspberry Pis

In which ways? Most commenters say the exact opposite, that cheap N100 mini PCs are less reliable than Raspberry Pis.

I'm just now trying to decide which way to go. Raspberry Pi 5 is definitely much much more interesting from the nerdy point of view, but would cost about the same as some cheap N100, for half the power. Though half the electricity usage too.