It seems that allow.auth should allow more than one 'network' and should control access by netmasks as oppose to a simple wild card. Example is that I have a clients sitting on a /23 network and a simple wild card opens up the gluster volume to all kinds of systems that I don't want to have access. Or if that is not possible at least a list of wild card based 'networks' should be able to be added. Maybe this should be an enhancement and not a bug, I am not sure if I am going outside the original use case/requirement here..
priority will be re-addressed after 3.3.0 GA
I was absolutely astounded when I discovered that the nfs.rpc-auth-allow parameter did not support netmasks. It is incredible that this product can be used in all but the simplest of circumstances. This is a essential feature please increase the priority to high.
(In reply to Alastair Neil from comment #2) > I was absolutely astounded when I discovered that the nfs.rpc-auth-allow > parameter did not support netmasks. It is incredible that this product can > be used in all but the simplest of circumstances. This is a essential > feature please increase the priority to high. Saw the note above that priority would be addressed after 3.3.0 GA - well 3.4.0 is now out.
Feature requests make most sense against the 'mainline' release, there is no ETA for an implementation and requests might get forgotten when filed against a particular version.
because of the large number of bugs filed against mainline version\ is ambiguous and about to be removed as a choice. If you believe this is still a bug, please change the status back to NEW and choose the appropriate, applicable version for it.