From: mdilger Date: Fri, 7 Jun 2024 20:29:13 +0000 (-0400) Subject: LUDOC-522 Nodemap: Added nodemap_del examples. X-Git-Url: https://git.whamcloud.com/?a=commitdiff_plain;h=HEAD;p=doc%2Fmanual.git LUDOC-522 Nodemap: Added nodemap_del examples. The Lustre manual was missing expamples for nodemap_del and nodemap_del_range. Added a section with examples for both that will fit the existing style and documentation. Signed-off-by: Maximilian Dilger Change-Id: I56630e10941972099871bc6adad2558a4182d01f Reviewed-on: https://review.whamcloud.com/c/doc/manual/+/55368 Tested-by: jenkins Reviewed-by: Sebastien Buisson Reviewed-by: Andreas Dilger --- diff --git a/LustreNodemap.xml b/LustreNodemap.xml index 1efa676..d17b29f 100644 --- a/LustreNodemap.xml +++ b/LustreNodemap.xml @@ -15,6 +15,10 @@ + + + + @@ -38,8 +42,7 @@
Setting a Mapping - The nodemap feature supported in Lustre 2.9 was first - introduced in Lustre 2.7 as a technology preview. It allows UIDs and GIDs + The nodemap feature allows UIDs and GIDs from remote systems to be mapped to local sets of UIDs and GIDs while retaining POSIX ownership, permissions and quota information. As a result, multiple sites with conflicting user and group identifiers can operate on @@ -136,14 +139,28 @@ mgs# lctl nodemap_modify --name TrustedSystems --prop Consider a deployment where researchers are working on data relating to birds. The researchers use a computing system which mounts - Lustre from a single IPv4 address, 192.168.0.100. - Name this policy group BirdResearchSite. The IP - address forms the NID 192.168.0.100@tcp. Create the - policy group and add the NID to that group on the MGS - using the lctl command: + the filesystem from a single IPv4 address, 192.168.0.100, + and sensors which mount the filesystem from an address range + 192.168.0.[50-99]. Name this policy group + BirdResearchSite. Create the policy group and add the + NID ranges to that group on the MGS using the lctl command: - mgs# lctl nodemap_add BirdResearchSite -mgs# lctl nodemap_add_range --name BirdResearchSite --range 192.168.0.100@tcp + + mgs# lctl nodemap_add BirdResearchSite + mgs# lctl nodemap_add_range --name BirdResearchSite --range 192.168.0.100@tcp + mgs# lctl nodemap_add_range --name BirdResearchSite --range 192.168.0.[50-99]@tcp + + + + Later, additional sensors were added that use addresses in the range + 192.168.10.[101-150] that increased the number of + nodes in the BirdResearchSite nodemap, but otherwise + are managed as part of the same nodemap. + + + + mgs# lctl nodemap_add_range --name BirdResearchSite --range 192.168.0.[101-150]@tcp + A NID cannot be in more than one policy group. Assign a NID to @@ -256,6 +273,31 @@ drwxr-xr-x 3 root root 4096 Jul 23 09:02 ..
+
+ Removing Nodemaps + + + It is possible to delete a NID range from a nodemap, any + clients in this NID range will be moved to the default nodemap. + + mgs# lctl nodemap_del_range --name BirdResearchSite --range 192.168.0.[101-150]@tcp + + When deleting a range from a nodemap it must be the same range that was + declared when using nodemap_add_range. This means that it is not possible + to remove a range inside of the initial values or a (partially) overlapping + range. Also worth noting, if two different ranges are added that are adjacent, + they are still treated as two independent ranges and must be each individually + deleted. + + + + When deleting a whole policy group all of the associated ID mappings, + NID ranges, and other parameters will be removed, and existing clients + will be moved to the default nodemap. The default nodemap cannot be deleted. + The syntax is: + mgs# lctl nodemap_del BirdResearchSite +
+
Altering Properties