So what are #FreeBSD folks doing for multi-node, high availability file systems? I looked at #Gluster, but that doesn't work. I'm starting to look at #minio, but it's an S3-oriented API.
I'd like to get to a docker swarm sort of situation where I have 3 identical docker VMs, running 3 identical Caddy configurations, with 3 identical Apache VMs, and requests load balanced across them. And then I want a shared filesystem so the users can upload the files for their web sites to one location, and it's made available to all the web front ends.
I'm currently in a mixed environment:
- #xcpng on bare metal
- FreeBSD VMs running important services (bastions, email, DNS)
- #AlpineLinux VMs running docker for all my container-based stuff
So I'm trying to do the shared, highly available FS part of this design and I'd stay with FreeBSD if I could.
#selfhosted
ProxLB is a Load Balancer for #Proxmox clusters, which rebalances your VM/CT workloads across nodes in your cluster.
https://github.com/gyptazy/ProxLB/releases/tag/v1.0.2
#virtualization #virtualisation #vmware #esxi #esx #kvm #qemu #xcpng #xen #xenserver #alternatives #opensource #free #fediverse #support #migration #VM #virtualmachines #virtualmachines #container #containers #LXC
* Rolling updates!
This ensures, that nodes in a Proxmox cluster are being automatically patched. Therefore, ProxLB now also comes with its own API which provides other nodes to identify the current state of other nodes in cluster. By this, we're finally able to keep nodes aware of potential maintenance windows when being patched and to move workloads away to other nodes in a balanced way and honouring the resources. Also, we can identify if a system reboot for the newly installed packages is required and skip moving those workloads away. However, I want to have everything done by the Proxmox API or ProxLB API which requires me to extend the Proxmox API by the new features. I try to get those into upstream to avoid maintaining a dedicated packages providing this extended features in the Proxmox API. I'm happy to see people testing this feature, please do NOT use this on production systems right now.
PR:
https://github.com/gyptazy/ProxLB/pull/48
#vmware #proxmox #xcpng #updates #security #opensource #infrastructure #virtualization
https://gyptazy.ch/blog/xcpng-a-more-professional-alternative-to-proxmox-based-on-xen/
I warned that there would be mishaps and clown shoes in my #microISP journey. After 556 consecutive days of uptime, it wouldn’t boot when I brought to the garage. The reason why is embarrassing, but I’ll tell it anyway.
Almost 2 years ago, I had a disk fail. The system uses hardware #raid in a mirrored pair. So I was able to hot swap the drive.
I got cocky. After swapping the drive I bought a couple more drives. “I know! I’ll convert from a mirrored pair to a 4-drive RAID5 setup.” I managed all that with the onboard management system. Then I had to tell my hypervisor to increase the size of the partition to account for all the new space.
I don’t even remember what I did wrong. But I had one of those sinking feeling moments where I knew I had just fucked up. I had trashed the partition table for the drive entirely. Now, it was fine in memory. But it was gone from the disk. I jotted down what was in RAM. I tried writing out to disk the right partition table. It appears I did THAT right, but the drive wasn’t bootable.
When I booted an #xcpng USB, it found everything on the disk and it is happily upgrading. At the end of the upgrade process, I’m confident it will make the disk bootable again.
Kids don’t try this at home. I am a trained professional. #homelab #selfhosted
Alt...
Photo of a monitor on a server displaying a backup and upgrade progress bar.