Details
Minor Description
Administrators might want to immediately prevent access to Lustre for a particular client, based on criteria such as client activity or generated load on the file system.
In addition to the ability for administrators to shut off this client, it would also be useful to be able to deny this client access to data administratively. This would provide a stronger ability to protect access to Lustre, especially in cloud environments where Lustre admins may not have the ability to interact with or shut off client nodes.
In order to address this requirement, we could add a new 'banlist' nodemap property. So once a storage admin has identified clients from a given nodemap that must be blocked, they are able to add theirs NIDs to this ban list. The banned clients would still be considered part of that nodemap, but all file system accesses from those clients would be blocked. This means not only new mounts from the banned clients would be blocked, but also existing mounts would not be permitted to access Lustre anymore. Later on, as the clients are removed from the ban list, they would be able to mount Lustre again, and get back access to Lustre.