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

HSM archive ID mapping for nodemaps

Details

    • Improvement
    • Resolution: Unresolved
    • Minor
    • None
    • Lustre 2.17.0
    • 3
    • 9223372036854775807

    Description

      In order to allow HSM operations to be handled by a Tenant administrator, it would be useful to allow remapping of the HSM Archive ID within a tenancy via the nodemap ID offset mechanism, so that each tenant gets a unique range of Archive IDs.

      This will allow configuring HSM copytools independently for each tenant, and eventually even allowing regular users to configure copytools running on their own compute nodes for attaching S3 buckets to the filesystem.

      Attachments

        Issue Links

          is related to

          New Feature - A new feature of the product, which has yet to be developed. LU-18109 Nodemap UID/GID/PROJID idmap offsetting

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Activity

            [LU-18775] HSM archive ID mapping for nodemaps
            rread Robert Read added a comment -

            For example, if a copytool running in a nodemap registers to receive actions for all achive_ids by specifying 0, then it should only receive actions in its nodemap range. 

            rread Robert Read added a comment - For example, if a copytool running in a nodemap registers to receive actions for all achive_ids by specifying 0, then it should only receive actions in its nodemap range. 

            People

              wc-triage WC Triage
              adilger Andreas Dilger
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: