I meant to mention yesterday, I have a branch with the mds-obeys-blacklist behaviour here: https://github.com/jcsp/ceph/tree/wip-17980 For the other side (blacklisting clients from the MDS), I also remembered that we currently we have a precedent for special-casing an mds->OSDMonitor operation, in the form of the MRemoveSnaps message. I think the options we currently have for blacklisting clients from the MDS are: A) Add a new MBlacklist message a la MRemoveSnaps B) Send a MMonCommand and special case the auth on the mon side to allow any mds.* entity to run "osd blacklist add" without needing the usual caps C) Send a MMonCommand and ask users/scripts setting up Ceph to explicitly include the mon cap to run the blacklist command. D) Piggy-back a list of clients to evict on MMDSBeacon, where the MDS daemon would trim that list once it saw that the blacklist had been updated to include those clients. D is a bit circuitous, but I think it could be interesting as it would let the mon exercise some discretion on whether to do the client blacklisting or not, rather than giving the MDSs such power. John -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
