Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-13307

add LCFG_NODEMAP_ADD_RANGEv6 records for IPv6

Details

    • Improvement
    • Resolution: Fixed
    • Minor
    • Lustre 2.16.0
    • Lustre 2.16.0
    • 9223372036854775807

    Description

      Add LCFG_NODEMAP_ADD_RANGEv6 and LCFG_NODEMAP_DEL_RANGEv6 records to hold IPv6 addresses. There may need to be some better semantics for what constitutes a "range" for IPv6 addresses, as we definitely do not want enumeration of addresses involved.

      Attachments

        Issue Links

          Activity

            [LU-13307] add LCFG_NODEMAP_ADD_RANGEv6 records for IPv6
            pjones Peter Jones added a comment -

            Merged for 2.16

            pjones Peter Jones added a comment - Merged for 2.16

            "Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/c/fs/lustre-release/+/53135/
            Subject: LU-13307 nodemap: have nodemap_add_member support large NIDs
            Project: fs/lustre-release
            Branch: master
            Current Patch Set:
            Commit: 0ea23e019454e03810d532758afa52aa054995d8

            gerrit Gerrit Updater added a comment - "Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/c/fs/lustre-release/+/53135/ Subject: LU-13307 nodemap: have nodemap_add_member support large NIDs Project: fs/lustre-release Branch: master Current Patch Set: Commit: 0ea23e019454e03810d532758afa52aa054995d8

            Per comments in the patch, it would be much better if IPv6 netmask could handle more than just a single NID per entry. Otherwise, I'm worried at the prospect of each connect walking a linked list of 5000+ clients in a nodemap on every connection to find if the NID belongs there or not. I don't think this is fatal as it would only apply to sites that actually do this, but it would be much better to fix it if possible before the release.

            adilger Andreas Dilger added a comment - Per comments in the patch, it would be much better if IPv6 netmask could handle more than just a single NID per entry. Otherwise, I'm worried at the prospect of each connect walking a linked list of 5000+ clients in a nodemap on every connection to find if the NID belongs there or not. I don't think this is fatal as it would only apply to sites that actually do this, but it would be much better to fix it if possible before the release.

            Got  https://review.whamcloud.com/c/fs/lustre-release/+/53135 fully working for IPv6 and IPv4. Its ready for review. Once this lands we can put lustre into a feature freeze.

            simmonsja James A Simmons added a comment - Got   https://review.whamcloud.com/c/fs/lustre-release/+/53135 fully working for IPv6 and IPv4. Its ready for review. Once this lands we can put lustre into a feature freeze.

            Currently working on https://review.whamcloud.com/c/fs/lustre-release/+/53135.

            Works for IPv4 and it mostly works for IPv6. Still some issues for final deleting of the nodemap due to the records support missing currently. Also for this patch only one large NID is stored for each nodemap.

             

            simmonsja James A Simmons added a comment - Currently working on https://review.whamcloud.com/c/fs/lustre-release/+/53135. Works for IPv4 and it mostly works for IPv6. Still some issues for final deleting of the nodemap due to the records support missing currently. Also for this patch only one large NID is stored for each nodemap.  

            This patch allows a single nodemap entry to be specified but not a range of NIDs. I don't think this ticket should be closed when 53135 is landed, since we really need to have a solution for specifying multiple IPv6 NIDs into a range efficiently instead of listing 5000 NIDs individually for multiple nodemaps.

            adilger Andreas Dilger added a comment - This patch allows a single nodemap entry to be specified but not a range of NIDs. I don't think this ticket should be closed when 53135 is landed, since we really need to have a solution for specifying multiple IPv6 NIDs into a range efficiently instead of listing 5000 NIDs individually for multiple nodemaps.

            People

              simmonsja James A Simmons
              adilger Andreas Dilger
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: