All - I've been building some stuff against the API, it's working very well so far, nicely done, thanks. One of the things I would like to be able to do is RBAC for cluster objects, e.g. bricks, volumes, etc. I don't think that is something that Gluster needs to do but it would be useful if there was a way to store an ACL in Gluster so we wouldn't need to build a separate database of cluster objects (metadata!) to store the permissions. I'd like to propose an extension to the current volume options system. If Gluster supported arbitrary volume options it could make the development of tools much easier. An user created option would have to be prepended with 'user.', Gluster could just ignore those. For my project it would be great to have support for volume option names of up to 64 characters and options of up to 4k. I could the ACLs for each object, something like - user.mngt.acl.Brick1 (some JSON or whatever) Thoughts? Thanks, Craig
