I thought that’s what it was.

So does “tanking” mean being laid in front of a tank and run over multiple times?

Because I can get behind this.

Palm had front keyboards

Fuck, that made no sense to me until I saw this comment.

Qidi runs Klipper.

Under things me and my users notice aren’t working right away, at the top of the list is email. So I notice when those alerts aren’t able to get through, because if email is down I have my phone ringing off the hook because my dad can’t get to his online auctions to see if he won that toaster for $5. So email is like, the best option.

I check my backup notifications by looking in my junk mail for anything labeled “Spam Quarantine Notification” because I can’t be arsed to fix the SMTP whitelist rules to allow local network relay.

If you use Live Migrate, realize that it doesn’t work on an LXC, only VMs. Your containers will be restarted with the LXC on the new node.

I would like to play with ceph but I don’t have a lot of spare equipment anymore, and I understand ZFS pretty well, and trust it. Maybe the next cluster upgrade if I ever do another one.

And I have an almost unhealthy paranoia after see so many shitshows in my career, so having a pile of copies just helps me sleep at night. The day I have to delve into the last layer is the day I build another layer, but that hasn’t happened recently. PBS dedup is pretty damn good so it’s not much extra to keep a lot of copies.

I’d trust you on my 6.

You’ve made an enemy for life!

A horse.

Ah, OK. Now I get your point.

Yes, RAID 10 ZFS with no ARC, 6GB SAS drives.

I have no idea what you have going on, I’ve never seen LXCs take that long, even if I include the time it takes to down the containers and bring them up after a reboot.

What are you using for running them? I just tested my docker LXC and it took 16 seconds from when I typed “reboot” to having a login prompt. And that’s on an ancient R410 server running proxmox.

I think you’re doing it wrong. LXCs boot almost instantaneously on a hypervisor since they hijack the host kernel, I’d be surprised if my CTs take 5 seconds.

I would agree on the live migration issue but I guess you pick your services accordingly. I have a VM that runs docker and a LXC docker host, and I pick my containers for each accordingly.

The advantages you gain with running a hypervisor on something like ZFS is immeasurable, for snapshotting, replication, snapshot backups and high availability. You don’t have to quiese machines to back them up and you can do instant COW snapshots before upgrades.

KVM doesn’t really have overhead, that’s the kernel part. Maybe a bit of RAM, but with LXCs it’s negligible.

I think Mailcow is a fair bit further along in features than this. I used this for a short bit but wasn’t overly impressed, and you are right about how running a docker stack is less hassle for updating.

oops

I followed where it was going and it was a forgejo repo where there were some action sets but not that one. I figured they were using their own sets and hadn’t gotten around to java yet.