There have been multiple accounts created with the sole purpose of posting advertisement posts or replies containing unsolicited advertising.

Accounts which solely post advertisements, or persistently post them may be terminated.

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.

just_another_person ,

I think you’re doing this on hard mode. K8s and Longhorn gets you what you want.

You could try Ceph in your setup, but you’re going to run into issues if your environments aren’t all exactly the same.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • [email protected]
  • random
  • lifeLocal
  • goranko
  • All magazines