After almost half a century, I'm still doing it...
-
It's VMs within VMs within VMs.
-
Use cockpit by Red Hat. It gives you a GUI to make networking changes*, and will check if the connection still works before making the change. If the connection doesn't work (like the ip addresses changed), it will undo the change and then warn you. You can then either force the change through or leave it be.
*via NetworkManager only.
-
Nice! I currently have a PiKVM but haven't been able to get it working with my NVR. Maybe this would work better.
-
I still prefer net-tools and use ifconfig eth0 up
That ip mess I'd rather do without, and those funky UU device/interface names I wish them out of my system -
That's probably because of netplan, right? You should be able to get the same results with just
netplan try. -
Netplan is an abstraction layer, so it can go over systemd-networkd, NetworkManager, or ip. I suppose it's better though, because it can be used with multiple backends.
-
Right, but the entirety of Cockpit is not necessarily required.
-
You don't need to install cockpit om the server being configured, you can use it as a gui to connect from other machines via the flatpak, over ssh.
-
Right.
My point is that a wrench was needed and a batmobile was recommended. -
This is why IPMI is so important.
-
No. Netplan uses it's own yaml format, which people would have to learn and use. I don't want to do that, I would rather just configure my existing networkmanager setup, rather than learning another abstraction layer over what is already an abstraction layer.
Also, for me, allowing NetworkManager to do the configuration is important, due to it's integrations with other Red Hat software like libvirt.
I understand that cockpit (and similar type tools) are "the whole kitchen sink" of utilities, and it may seem like they come with more than you may need. But that doesn't change the fact that they get the job done, and in some usecases, are better than dedicated tools.
-
I've done this kind of thing remotely in screen with
ifdown eth0 ; sleep 10 ; ifup eth0 ; -
That is a totally fair explanation. End of story. No blame. Honest mistake.
-
I wish.
It was a bcachefs array with data replicas being a mix of 1,2 & 4 depending on what was most important, but thankfully I had the foresight to set metadata to be mirrored for all 4 drives.
I didn't get the good fortune of only having to do a resilver, but all I really had to do was fsck to remove references to non-existent nodes until the system would mount read-only, then back it up and rebuild it.
NixOS did save my bacon re: being able to get back to work on the same system by morning.
-
Can also use Pi KVM to add a similar capability to non server grade hardware that doesn't have it. I did that for a workstation once.
-
Lol; I've done this too. Thankfully not to anything important.
-
Yup, I use PiKVM, too. Fun fact, PiKVM's first commit is a clone of my DIY IPMI repo
-
Awesome job!
-
Thanks! Yea, it was a really fun project to make back before there were any real options. And I'm glad the PiKVM team could expand upon it.
Somewhere along the way I lost the "based on" credit, likely whenever they fully modernized the stack. I wasn't really keeping track, but did find it humorous when LTT said the creator complained someone based another project on them. I was like "Hmmmmmmm..." but just laughed because I didn't make it for it to stagnate like it had been with me.