I should have addressed this to begin with. always been true, so a central multiuser repo in 2025 would use nfsv4 with kerberos because it exists. That is an entirely different matter then "Getting root on the server is a "hacking 101" exercise...
let me just verify I understood what you claim; having an NFS share open is a vector for an attacker to gain root access to the underlying server, and its a well known attack?
humor me, as I am clearly not in the know; since its a well known...
I was responding to the specific statement you made:
That is simply not true for "traditional" NFS without Kerberos. Getting root on the server is a "hacking 101" exercise, not something that is "HIGHLY speculative". It is a well-known attack...
easily remedied by limiting access to trusted guests at the network level.
Look, ANY method of sharing has tradeoffs between security and usability; its the task of the sysadmin/netsec/opsec staff to ensure that whatever solution deployed meets...
As @gurubert mentioned, your solution doesnt match your problem description.
you dont need 3 servers for a mssql cluster. you need two. You dont even need a nas/san at all, you have multiple options included windows failover cluster and storage...
If you want to run MSSQL in a clustered setup use local storage for its nodes.
There is no need to replicate on the storage level if the DB replicates its data on the application level.
For my curiousity, can you elaborate?
1. What does the number of devices have to do with you access control?
2. similarly, what does it have to do with people bringing their own devices?
3. a user having root at their side has no consequence on...
Wait; are you looking to use virtioFS as a replacement for a network file system?
I mean, ok, but thats a very tough hill to climb; NFS and SMB had decades to deal with various bugs, limitations, issues, etc.
and if you're not- well, nfs and...
....
that doesnt make any sense.
what do access controls have to do with network routing? any addressable device (including your network server) is routed according to rules you set.
I dont actually understand your point; maybe I misunderstood
nothing with virtiofs deals with this. perhaps, again, I dont understand what you're trying to accomplish.
NFS has access control...
It is not likely that you can beat the speed of native cephfs connection by sticking another obfuscation layer on top of it, regardless of how efficient. I hope you would post the results of your comparison.
I've been selling storage for 25 years. that was never the intent. its intended to facilitate multiple initiators so you're no longer tied to a single server spof.
Kinda true, but not because it "surpassed" the others. There are simply larger...
Shared storage is shared storage. the HOW is less relevant then the "what." both the above and the following list are all example of multi initiator capable solutions, either block or file. Logically its all the same thing. As for Glusterfs...
im not an expert on this but from what i've read on this forum so far
* don't create a 3 node ceph cluster for production, use 5 nodes ++
* ceph performance depends on amount of nodes, the local ssd's speed and network speed
* don't host vm's...