I’ve scoured the forums, but what I don’t understand is how to mitigate the 1 volume, 1 machine problem. I have an application that must write to disk, not an object store like s3/minio for reasons. What should I do? Is it possible to create my own Gluster cluster and connect my app? Does Gluster require a volume mount? And if so, how would I even mount a Gluster volume in an Fly context? I feel like the documentation should offer slightly more guidance. Not every application can easily be modified to leverage an object store. I need resilient volumes to scale this specific application.
Any guidance would be appreciated. Is Gluster the right rabbit hole?
I’d have suggested Tigris, but it sounds like you reckon that won’t suit your app. Could you expand on the reasons so that readers can best advise you?
Ooh, I just had a scan-read of Gluster, it looks ace. I had a ferret about for an auto-synchronising multi-node filing system some months ago, and I didn’t spot this one. Thanks!
It would be pretty great if the [mounts] section of fly.toml could have a flag in it to connect all of the instances of the source volume with Gluster, and if Fly took care of all the details to make that work.
This is mentioned as being one of the many things that Fly.io is looking for third-party extensions partners to do, :
What you bring is: almost everything else.
[…]
Our platform offers fast attached storage. There’s so much more to build on top of that, from object storage to distributed filesystems.
I infer that your best bet would be to find a brave soul that’s been wanting to try their hand at some variety of distributed-systems startup—but doesn’t have a firm idea yet of what people might want in that parameter space exactly—rather than trying to convince Fly directly…
wow that’s one of the most out there suggestions I’ve seen in response to a question on this forum (and I mean this in a positive way!)
for a more today option, maybe rclone mount would work? it lets you mount a s3 bucket to a directory as a FUSE filesystem. I haven’t tried it myself though.
Ha-ha… The forum software doesn’t consistently mark exactly which post people were replying to—alas…
I only meant that paragraph in the (side) context of @Alex21’s far more ambitious, “have a flag to connect all of the instances of the source volume with Gluster, and Fly [takes] care of all the details to make that work.”
(Which I contend is only medium out-there, overall. People have asked for Ampere hardware and MirageOS in the past, remember, …)
Nice find, @halfer! Unfortunately, the punchline from that link didn’t make it into the embedded teaser. If Mount Tigris as a Filesystem | Tigris Object Storage Documentation really works as well as claimed, that sounds like a really good option for a lot of use cases; don’t know if it solves the OP’s use case though.
:
…)