Name one. What I mean by multi-tenant is that the namespace, security space, capacity quota and I/O quota are fully isolated and managed at the storage-system API, not via other facilities such as cgroups which aren't even applicable beyond a single-host level. Each tenant gets something that looks like a private service with predictable limits (appropriate for an SLA) regardless of what other tenants are doing, despite being on shared infrastructure. Commercial vendors like NetApp and all the "hyperconverged" crowd have support for this kind of isolation at the cluster level, as do some bespoke storage systems such as the one I work on at Facebook, but in the open-source world? Nada.
Name one. What I mean by multi-tenant is that the namespace, security space, capacity quota and I/O quota are fully isolated and managed at the storage-system API, not via other facilities such as cgroups which aren't even applicable beyond a single-host level. Each tenant gets something that looks like a private service with predictable limits (appropriate for an SLA) regardless of what other tenants are doing, despite being on shared infrastructure. Commercial vendors like NetApp and all the "hyperconverged" crowd have support for this kind of isolation at the cluster level, as do some bespoke storage systems such as the one I work on at Facebook, but in the open-source world? Nada.