I think that as you move towards replacing cloud services with self-hosted ones you take on the responsibility of providing the same reliability as the cloud services.

Just installing a UPS will let you ride through 99% of all power failures because most of them are only a few seconds long. My UPS says that my entire HomeLab, including Internet modems runs at about 100W, and it will last for the better part of an hour.

The question then becomes about longer outages, that run the UPS dry. There are two issues.

The first issue is system shutdowns, if they just crash when the battery ends, then you run the risk of data corruption and disk buffers that haven’t flushed. But in truth, this is probably a minor possibility. Your servers were up, but the rest of your house was already down. No feed from the cameras, no events in HomeAssistant, no WiFi, no nothing. This means virtually no activity on your servers for an extended period of time.

This doesn’t eliminate the possibility of corruption, but it makes it less likely.

The second issue is getting the servers back up and running when the power returns. This can be a bit more complicated, what if the power is up and down a bit before the UPS has some charge built up?

Maybe your best just leaving them off for a bit until things have stabilized and the UPS has a charge.

NUTs deals with both of these issues in an automated fashion. It can shut your services down in a controlled manner so that they don’t crash when the battery dies. It can bring your servers back on line when the power is restored and stable.

For me, my main concern is for when the power failure goes past he battery life when I’m on vacation. I won’t be able to go and push power buttons on the server. NUTs can get a bit tricky if you are looking for 100% hands-free operation. I can deal with anything when I’m home, but away in problematic.

I’ve decided to leave NUTs out of the mix for now. All of my servers are configured to turn on when power is restored, and all of the services are configured to start up automatically when the server boots. I’m content to let the UPS drain dry, crash the mostly idle servers when that happens, and then reboot when power is restored.

There’s a risk, but I think I understand it.

My objection centres around the wording, “Premier is essentially the same as a US Governor”.

Not, “similar”, or “somewhat the same responsibilities”, “essentially the same”.

Yes, lots of countries use the term “Governor” for the leaders of states and provinces. But specifying, “US Governor”, adds a ton of baggage to the term that essentially makes the statement incorrect.

It’s a Parliamentary system, a different form of government and the roles are not “essentially” the same.

I didn’t see the “at war” part in the full text of the speech, and I don’t rememer hearing it when I watched it. Perhaps it was in response to one of the questions after the speech?

The scope of the powers is virtually identical within their jurisdictions. Provinces are clearly not going to be negotiating international treaties, for instance, but they are going to be negotiating inter-provincial relations.

Well, I object to the need to somehow relate everything to an American frame of reference. The two systems are fundamentally different, and the roles are not really analogous. Far better to say, “Like a Prime Minister, but for a province.” What’s hard about that?

“With a fucking dildo!”

This is essentially incorrect. Canadian provinces use a parliamentary system very similar to the federal government. The Premier of a province is analogous to the Prime Minister of the country, but for a single province.

The Premier in not elected separately like a US Governor, nor does he act separately from the legislature of the province. He’s the leader of the party that holds the most seats in the Legislature and forms the Government of the province.

When I started out, I really wanted to do it this way too. A bare metal install just seemed a little crude, and I thought I might want to run other firewall related services from that node. I had technical issues, and OPNSense just didn’t want to run under Proxmox for me.

Finally, I said to hell with it and went with a bare metal install and, in retrospect, I’m glad it worked out that way.

OPNSense just works, and I don’t feel like there are any opportunities lost due to the bare metal install. Instead, it just feels really clean and sequestered from the homelab cluster as it should be.

I totally get the desire to want to muck about with Proxmox hosting and learn about how it works. That’s the right attitude. But hosting an OPNSense virtual machine isn’t the right starting place.

As a beginner, do beginner stuff. Install a Technitium container and learn about DNS. Install Immich, or Jellyfin or an *arr stack. But not a firewall as a VM.

Yeah, there is a line of units that has a PCI slot that then requires a riser card in order to be able to use it. The problem is that those units, from what I’ve seen, tend to cost at least twice as much as the M910Q/M710Q. Even the M920Q/M720Q are significantly more expensive. Not to mention, a bit more difficult to get hold of.

IMHO, once you’re talking about dropping $300-$350 on one of these models with the riser card, you really have to think hard about whether it’s worth it for 6th/7th generation Core i5 processors. Especially if you’re looking at a cluster of three. It seems highly probable that you could get something with an 11th/12th generation processor and multiple or 2.5GB ethernet ports for only a bit more, and you’d end up only needing two of them instead of three, and price might end up being a wash.

I am really, really curious to see how external USB 2.5GB or 5GB adapters would work. I’m getting the impression that they are a lot more reliable than they were even a few years ago, and might be a viable, cheap option.

All that being said, network speed hasn’t been an issue for me so far, and I’m not convinced that CEPH + HA, is a path I should be going down. Or a path that’s worth it for most self-hosters.

So far, the only thing that I’ve encountered that pushes the CPU on an ongoing basis is Frigate, and even that is performing well and not affecting other containers on the same host. But I’m still adding services to my cluster, so who knows.

I watched a whole bunch of videos about those and it totally looks like they would work electronically. But most of them wouldn’t fit in any of the ports on the back without modification and 3D printing magic. Some people left them “just hanging out”.

I’ve got the article just about ready to go. I got myself swallowed up in a project to implement Frigate (finally) and just didn’t get around to posting it. It should be up tomorrow.

Yes, I saw that comment. I wasn’t sure what “But… it has so many downsides…” meant, and the comment doesn’t clarify.

To me, the big question is how the “improvements” they are going to make would my installation better. I suspect that most of the improvements are ones that allow them to make Music Assistant better, or allow them to add tighter integration with Music Assistant.

As far as I know, they haven’t rolled it out yet. But that thread is almost a year old now.

I would be interested to see what they’ve done.

That reference is in one of the programming articles. You must have poked around a bit to find it. “Set it and forget it!”.

It was in my list of options when I started. I liked the modularity of SnapCast, though. SnapCast just handles the whole-home aspect, and the you pair it with a music player that you like.

Not specifically, but SnapCast will accept a range of input methods and should be capable of taking output from virtually anything that plays sound.

This was a little problematic at first. Part of my shift over to OPNSense was that I bricked my mesh WiFi when attempting to put it into AP mode. So I had to scramble around to get a WiFi AP. Initially it was upstairs and connected to a swtich that was connected to the homelab in the basement through a Powerline AV. The Pi0’s dropped out a lot.

My house is too old for Cat5 in the walls, but does have some coax for cable TV. So I got some MoCa adapters and a second WiFi AP and sorted the WiFi out. After that, no WiFi problems with the streaming. I think the Powerline AV was just too unstable for the SnapCast.

There still are some occasional brief outages, and from what I can see this is caused by buffer overflows or something of that ilk with the SnapCast client software. I’ve adjusted the parameters as much as I can, and it seems pretty stable. I’ll notice a 1 or 2 second outage somewhere in the house every day or so.

Last week the SnapCast in the bathroom was glitching a lot, so I rebooted it and it’s been stable ever since. The one in the front room, which is literally 6" from the WiFi AP has never glitched at all, and it’s been running for about 3 months now.

I have a section in one of the articles where I talk about recovering from glitches that halt the Mopidy stream itself. In those cases, the Mopidy service is still running, but stops streaming. Using the REST API you can get it running again, so I wrote a cron job that checks every 3 minutes and restarts the stream if required.

I just came back from a 3 week vacation and after 2 weeks the Mopidy service itself crashed. I was getting Gotify notifications every 3 minutes from that cron job as it attempted to restart the stream. If since modified the Mopidy service to restart if it crashes, but it could be months before that ever happens.

I’ll wait to see.

Apparently you can run SnapCast on an ESP32 also. For me, the Pi0’s cost about $20 CDN, and the DAC card about the same, and the delivery from PiShop.ca was about 3 days. ESP32 would have cost less, but then require some kind of housing because of the two components flopping around. The Pi DAC’s slip onto the GPIO pins and the pair are essentially 1 thing at that point. Mine are just tucked away behind whatever the amps are.

I point out in Part II or III that these are essentially appliances once they’re set up. As long as they do the job, I don’t expect to upgrading them on a regular basis or anything like that. SendSpin looks cool because it does other stuff besides just stream music, but I’m not looking for that. From what I can see, SendSpin runs on Pi’s too, so it should be fairly simple to add that to the Pi0’s in the future if that’s what I want.

Depending on what you are doing with them, the drives can work just fine running through the USB ports, which can be faster than hard drives in most cases. I have my content - which is like 90% of the data space - on USB hard drives and the databases to manage them on the internal M.2 drive. Works fine for something like Immich.

How to say you come from the States without saying you come from the States.

I’ve seen people mention this a few times, but I’m not so sure that it’s actually a thing.

Switches are designed to route traffic intelligently, and they don’t blast all of the traffic to every port. If I remember correctly, at some point they do some kind of mapping between IP address and MAC address, and they know which MAC addresses are attached to which ports, and they only route the traffic to the port that has the MAC address they are looking for. I don’t know how much local switches collude with each other to share information about connected devices or how many hops they may be able to look into.

In any event, no matter how wrong I am about that, if you’ve got a device on switch A that needs to send packets to a device on Switch K, then Switch A either has to know that the device is on Switch K and the path to get to Switch K or it has to send the packet to every switch that it is connected to. That doesn’t change with VLAN’s, if Switch A doesn’t have knowledge about every other switch on the network, and which VLAN’s they are configured for, then it will have to send the packet to every switch it is connected to.