,----
| I was wondering if the planned quota support would be
| filesystem-based or more flexible like OpenAFS, which has
| volume-level quotas? What about quota-support integration with NFS
| re-export and SAMBA shares ?
`----
Our plan was to do file system level quotas (based on
UIDs). Implementing volume level or file level or dir level quota is
easy. If you tell us what all are you looking for, we can plan around
it.
For NFS quota integration, rquotad module should be loaded on the
server side. GlusterFS should just appear like a regular filesystem with
quota support for NFS. The same goes for SAMBA. "smbd -b" should show
"WITH_QUOTAS".
I am just curious, why there is a need to re-export with NFS or
SAMBA, when glusterfs can be mounted directly. We don't support
proprietary OSes though.
,----
| Also, are there any plans to implement some of the other cool
| aspects of OpenAFS, such as a unified name space, the ability to
| move data from one storage target to another while the filesytem
| remains available, and snapshots?
`----
We already have unified name space support (cluster/unify translator
implements this). For moving files between bricks, we have it in our
roadmap. For example, defrag tool can re-organize files between bricks
based on load statistics. You will also be able to manually move
files between bricks with the management tool. I will plan for
on-the-fly snapshot support too. We are adding more developers in a
month. Snapshot will be implemented as a translator in a distributed
manner. Each snapshot translator will have its own private directory
for storing changes. You will be able to have a chronological sequence
of multiple distributed snapshots and tools to manage them.
One of our developer implemented "trashcan" translator for fun. May be
that will help till we implement snapshot support.
--
Anand Babu
GPG Key ID: 0x62E15A31
Blog [http://ab.freeshell.org]
The GNU Operating System [http://www.gnu.org]
