This is outstanding advice, because most people don't eat nearly enough fiber. Ya. Its poverty food. It's also magic that will make your guts work correctly and possibly save your life.
I boil up a batch of beans/rice/quinoa or some combination every week. I cook enough to be an ingredient or side for several meals. I don't heavily flavor it, and cook to avoid much sauce, so its more flexible to use. There's always a stock container of beans or rice in my fridge. It may take you a few batches to get good at cooking these things from scratch, but its pretty simple stuff.
Ya folks. Wash your food.This most especially applies to brown and wild rice, which has natural arsenic. Rice may well be the primary or only source of arsenic in your life. Really, if you don't already know, you should learn and stop eating arsenic.And quinoa. If you eat quinoa, you probly already know this. But quinoa has a chemical called saponin until its washed.But ANYTHING that comes from a factory and passed through innumerable hands, yes you should wash it before you eat it. Pesticides. Chemicals. Germs and dirt.
Washing beans, rice, quinoa is pretty easy. Put it in a bowl with water. Stir it. Let it sit a bit.Stir it again, and pour the water off the top.(I use a strainer, but that is not necessary if you get good at this.)Do this seven times. If there was any clouding in the water, there won't be by the seventh repeat.I usually let it go on about an hour or so, I'm also soaking the product while washing it.
This was painful to read. Yuck. It was written like clickbait. Like AI writes. Yuck.And of course it was crossposted. If you've got something you need everyone to know, you gotta crosspost it everywhere.
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/
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.
Well, that's interesting. I guess linux really is going more mainstream, if that's the more common user experience. The users I know are mostly professionals that enjoy tinkering under the hood. Thanks for your perspective, stranger.
Ok, I can see that in SteamOS, users that don't directly interact with a package manager. That seems likely.
I would say that 'most users' of just about any linux distro know all about command line package managers.So, my 'most users' and your 'most users' don't seem to be the same people.
I tried making my first chickpea mash the other day. I won't call it hummus. It looked more like salsa with all the peppers and garlic I added.