Well, the more of youtube we import … the more of youtube we import. Part of the reason we aren’t flooded with crap on the fediverse is that we are too small to matter. And perhaps we are small enough to effectively police our own. So … why would we want to import youtube at all? Bigger is not better.

That’s a link. They also call them URLs. We learned about them in web class, back in the stone age.

wat

I’ve posted here and had it deleted. So I don’t bother.
The instance I’m a member of had an unused selfhosting comm, and I started using it. Other people did too. Thanks for the shout out.

Damn. It took me 3 paragraphs to say that. Good job.

Ok, I quibble with much of what you just wrote, but your first line contained a lucid point.

In essence, you propose that a federated monetization scheme would direct the bulk of the pie to the participants and not to the big corporate interests.

Now that’s a damned interesting thing to consider.
I think its obvious that it would/will go awry. Any time you get non-profits screwing around with money, somebody figures out how to steal it.
But if even a bit more went to the participants and paid for infrastructure, that would be a positive thing.

But again … non-profits and coops never handle money correctly. Watch this get all the way to the goalpost and then swoop, it all gets handled with GooglePay. Its doomed. DOOM.

Youtube was a lot more fun before it was flooded with professionals out to make a buck on advertising. This thing you seek … it is not good.

Ok. I can follow this line of reasoning.
If you want to avoid corporate platforms, fediverse doesn’t provide as viable an alternative as one might like.
This is clear, and makes sense. Thanks for the succinct explanation. At least I see some sense here now.

I’m not entirely sure that it matters.
Like, when was it decided that the ‘making money’ bit needed to be imported from YouTube?

Alright already! I’ll work on my upgrade.
I’m wondering if I should just build a new docker and then migrate the data instead of upgrading in place. I bet that’s the easier thing to do in the end. Sounds safer too. I got backups and all, but …

Hey, um … I read your article. Or I tried to.
It lost me at the point where I need to give money to somebody else. So, basically right at the start.

To be more specific, your article starts of lamenting that its not convenient enough for me to give money to someone (“content creators”, a bullshit term if I’ve ever heard one) on these federated platforms. “this is a bit of a problem” There’s no examination of whether we should be doing this. Its taken as a given that monetization is a positive goal.

So … I really tried to get there and understand your point, but there’s this vast gulf between us.
Why would it be bad if nobody makes any money off the fediverse?
That sounds good to me.

Netbox is a hell of a package, of which I’ve essentially only touched the IPAM, and I don’t even use it programmatically. I just use the web console to keep track of 4 subnets and about 50 IPs.

It’s got a whole virtualization section that I haven’t touched, although that would make my device mapping more sensible. I just treat em like they are all real, and only map the physical nics on the hypervisor hosts.

I do keep text notes in Netbox entries, but that’s sort of a backup. If its something I’m likely to need to know, I’ll have a note in Proxmox. Usually login links for apps hosted there and the like. And of course I’ve got a folder full of text files with all my deepest secrets.

I’m not real clear what exactly you need to document.
Infrastructure documentation starts with an IPAM.
A good IPAM can help you document all kinds of stuff.

I use NetBox.
https://github.com/netbox-community/netbox?tab=readme-ov-file#getting-started

I’m running it as a Docker container on a Linux VM.
I just looked at their latest screenshots, and it appears they’ve done quite a bit with it since I stood up my copy.
It does even more now. I’ll have to upgrade.

Cool.

Here. SSH key issues. There was a huge forum war.
https://forum.proxmox.com/threads/ssh-keys-in-a-proxmox-cluster-resolving-replication-host-key-verification-failed-errors.138102/
But its still a thing. That still needs to be fixed by a human. Today that’s me.

Regarding CEPH and corosync on the same network … well I’m just getting started with that now. I do have them on different vlans, but its the same 10gb set of nics. I’m hoping if it gets really lousy, my netadmin can prioritize the corosync vlan. I’ll burn that bridge when I come to it.

EDIT … The linked forum post above leads to the SSH key answer, but its convoluted.
Here’s what I put in my own wiki.

Get the right key from each server.
cat ~/.ssh/id_rsa.pub

Make sure they match in here. Fix em if they don’t.
/etc/pve/priv/authorized_keys

There’s a couple symlinks to fix too, but this should get it.

SSH key management in PVE is handled in a set of secondary files, while the original debian files are replaced with symlinks. Well, that’s still debian. And in some circumstances the symlinks get b0rked or replaced with the original SSH files, the keys get out of sync, and one machine in the cluster can’t talk to another. The really irritating thing about this is that the tools meant to fix it (pvecm updatecerts) don’t work. I’ve got an elaborate set of procedures to gather the certs from the hosts and fix the files when it breaks, but it sux bad enough that I’ve got two clusters I’m putting off fixing.

Corosync is the cluster. It’s a shared file system that immediately replicates any changes to all members. That’s essentially anything under /etc/pve/. Corosync is very sensitive. I believe they ask for 10ms lag or less between hosts, so it can’t work over a WAN connection. Shit like VM restores or vmotion between hosts can flood it out. Looks fukin awful when it goes down. Your whole cluster goes kaput.

All corosync does is push around this set of config files, so a dedicated NIC is overkill, but in busy environments, you might wind up resorting to that. You can put cororsync on its own network, but you obviously need a network for that. And you can establish throttles on various types of host file transfer activities, but that’s a balancing act that I’ve only gotten right in our colos where we only have 1gb networks. I have my systems provisioned on a dedicated corosync vlan and also use a secondary IP on a different physical interface, but corosync is too dumb to fall back to the secondary if the primary is still “up”, regardless of whether its actually communicating, so I get calls on my day off about “the cluster is down!!!1” when people restore backups.

I use PVE professionally. I could spent some time bitching about how it handles ssh keys and the fragile corosync cluster management. I could complain about the sloppy release cycle and the way they move fast and break shit. Or all the janky shit they’ve slapped together in PBS. I could go on.

But I actually pay for a license for my homelab. And ya, it is THE thing at work now.

I’ve often heard it said that Proxmox isn’t a great option. But its the best one.
If you do try it, don’t bother asking questions here.
Go to the source. https://forum.proxmox.com/

Good riddance.

Hmm. I used to volunteer with Free Geek in Portland OR. It was essentially that, an e-disposal site and we made refurbs for community organizations. But they did have a store for sale to the public.

I have so much computer junk. I got rid of most of it, but then I got a bunch more when we closed the company office. Got at least 10 monitors, 5 PCs, a mini, couple laptops … and a storage shelf to put it on.

Buy? That’s garbage. Look in garbage places. Used shops of any sort.
I like the college junk store suggestion. I used to do that.

You better watch it. You will shortly have a closet full of junk computer parts.

wat

Sometimes you are just right. No mind reading required.