[lustre-discuss] Using rootsquashing on lustre

Aurelien Degremont adegremont at nvidia.com
Fri Nov 15 07:27:36 PST 2024


> Can someone help understand what are the pros and cons of these 2 methods ?
One is the legacy one and deprecated.
The new one (using nodemap) provides the same features and even more.

I see very little interest in sticking to the old one, and putting you at risk that this is not even supported in the future (very far future though)


Aurélien
________________________________
De : lustre-discuss <lustre-discuss-bounces at lists.lustre.org> de la part de Ravi Theja Reddy <ravithejareddy99 at gmail.com>
Envoyé : mardi 12 novembre 2024 17:09
À : lustre-discuss at lists.lustre.org <lustre-discuss at lists.lustre.org>
Objet : [lustre-discuss] Using rootsquashing on lustre

External email: Use caution opening links or attachments

Hi Lustre experts,

I am looking to enable rootsquashing feature on lustre. As part of it, I noticed we have 2 potential ways of doing it.
1. Using tunefs.lustre cmd on MDS servers.
2. Using  nodemap feature to enforce root squash and as part of it, creating a trustedSystems node map_group to all all the lustre server_nids and set the admin and trusted properties. And later removing the admin and trusted properties for default nodemap group and squash the UID and GIDs.

When checked on latest lustre manual, it recommends the node map way, Can someone help understand what are the pros and cons of these 2 methods ?

And as part of node map feature, we need to add all the lustre server_nids. Also have a question what would be the consequences if we do not add all the lustre server_nids into trustedSystems group ?

Thanks for the input.
Regards,
Theja
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-discuss-lustre.org/attachments/20241115/f42b363b/attachment.htm>


More information about the lustre-discuss mailing list