Details

    • Technical task
    • Resolution: Fixed
    • Critical
    • None
    • Lustre 2.4.0
    • None
    • Orion
    • 4014

    Description

      Please write and attach the test plan for how to test this feature.

      Attachments

        Activity

          [LU-1920] Create and attach Test Plan for quota testing

          It appears the tests were run twice on the 2.3.59 tag on both ldiskfs and ZFS and all passed.
          Sarah can comment more.

          jlevi Jodi Levi (Inactive) added a comment - It appears the tests were run twice on the 2.3.59 tag on both ldiskfs and ZFS and all passed. Sarah can comment more.

          Have we finally run the whole test plan? No major issues found?

          johann Johann Lombardi (Inactive) added a comment - Have we finally run the whole test plan? No major issues found?

          Sarah, it looks good to me. Thanks.

          niu Niu Yawei (Inactive) added a comment - Sarah, it looks good to me. Thanks.
          sarah Sarah Liu added a comment -

          For the online OST addition testing, here are the test steps, please comment if it is not enough.

          1. set up lustre with one OST-0, enable quota and create a file then use up all the blocks
          2. online OST addition to the file system
          3. check if the quota is enabled on the new OST-1
          4. create a new file make sure it is on the new OST-1 and then write, should expect EDQUOT
          5. delete the first file on OST-0 and write again on OST-1, should expect success

          sarah Sarah Liu added a comment - For the online OST addition testing, here are the test steps, please comment if it is not enough. 1. set up lustre with one OST-0, enable quota and create a file then use up all the blocks 2. online OST addition to the file system 3. check if the quota is enabled on the new OST-1 4. create a new file make sure it is on the new OST-1 and then write, should expect EDQUOT 5. delete the first file on OST-0 and write again on OST-1, should expect success

          I have updated the document. I think we need to run the same test with a lustre version <2.4 in order to compare.

          johann Johann Lombardi (Inactive) added a comment - I have updated the document. I think we need to run the same test with a lustre version <2.4 in order to compare.

          Johann,
          Can you please add the details for what the performance test should entail? Also, how is Quota enabled on Hyperion?
          Thank you!

          jlevi Jodi Levi (Inactive) added a comment - Johann, Can you please add the details for what the performance test should entail? Also, how is Quota enabled on Hyperion? Thank you!

          Does this need to be stressed at scale?

          Yes, it would be great to run the performance test on hyperion.

          If no: does this have a feature that needs to be enabled or disabled during normal SWL testing?

          I don't think SWL has any special code for quota. That said, we can probably run it on a filesystem with quota enabled.

          johann Johann Lombardi (Inactive) added a comment - Does this need to be stressed at scale? Yes, it would be great to run the performance test on hyperion. If no: does this have a feature that needs to be enabled or disabled during normal SWL testing? I don't think SWL has any special code for quota. That said, we can probably run it on a filesystem with quota enabled.

          Does this need to be stressed at scale? If no: does this have a feature that needs to be enabled or disabled during normal SWL testing?

          jlevi Jodi Levi (Inactive) added a comment - Does this need to be stressed at scale? If no: does this have a feature that needs to be enabled or disabled during normal SWL testing?

          the test plan looks comprehensive to me. thanks.

          niu Niu Yawei (Inactive) added a comment - the test plan looks comprehensive to me. thanks.

          Niu, could you please comment on the above TP? Thanks in advance.

          johann Johann Lombardi (Inactive) added a comment - Niu, could you please comment on the above TP? Thanks in advance.

          Quota test plan
          ***************

          1. Correctness (both ldiskfs and zfs)
          --------------

          • sanity-quota with SLOW=yes
          • online OST addition
          • failover tests (MDT & OST) with quota on and enforced
          • running all acc-sm tests with quota enabled and enforced

          2. Upgrade (ldiskfs only)
          ----------

          • create a filesystem with 1.8/2.1, enable quota, set some quota limits and create some files
          • upgrade to 2.4 (require tunefs.lustre --quota and lctl conf_param lustre.quota... to be run)
          • check limits and usage
          • remove / create more files and check behavior

          3. Client Interoperability (both ldiskfs and zfs)
          --------------------------
          2.3 client compatible, clients prior to 2.3 aren't yet (due to EINPROGRESS support)

          • run s-q with 2.3 client and 2.4 servers (require to use s-q version from 2.4)
          • compatibility with older clients to be tested once EINPROGRESS patches are landed to b2_! and b1_8.

          4. Impact on performance (both ldiskfs and zfs)
          ------------------------
          Run ior and mdtest on hyperion with:

          • fresh filesystem with no quota settings. This should provide us with reference numbers.
          • quota enabled via conf_param. Impact on performance should be null.
          • quota enforcement enabled with a large limit for the user (via setquota). Impact on performance should be close to null.
          • quota enforcement enabled with a limit close to expected usage (should still fit). Impact on performance to be compared with prior lustre release (2.1, 2.2 or 2.3)
          • quota enforcement enabled with a limit smaller than usage (EDQUOT error expected). We should again compare with a prior lustre release.
          • quota disabled via conf_param. Impact on performance should be NULL.

          5. DNE support (both ldiskfs and zfs)
          ---------------

          • sanity-quota with SLOW=yes with multiple MDTs
          • space rebalancing for inodes (never exercised when one single MDT)
          • impact on metadata performance with remote directory (on MDT1) while master still runs on MDT0
          • online MDT addition
          johann Johann Lombardi (Inactive) added a comment - - edited Quota test plan *************** 1. Correctness (both ldiskfs and zfs) -------------- sanity-quota with SLOW=yes online OST addition failover tests (MDT & OST) with quota on and enforced running all acc-sm tests with quota enabled and enforced 2. Upgrade (ldiskfs only) ---------- create a filesystem with 1.8/2.1, enable quota, set some quota limits and create some files upgrade to 2.4 (require tunefs.lustre --quota and lctl conf_param lustre.quota... to be run) check limits and usage remove / create more files and check behavior 3. Client Interoperability (both ldiskfs and zfs) -------------------------- 2.3 client compatible, clients prior to 2.3 aren't yet (due to EINPROGRESS support) run s-q with 2.3 client and 2.4 servers (require to use s-q version from 2.4) compatibility with older clients to be tested once EINPROGRESS patches are landed to b2_! and b1_8. 4. Impact on performance (both ldiskfs and zfs) ------------------------ Run ior and mdtest on hyperion with: fresh filesystem with no quota settings. This should provide us with reference numbers. quota enabled via conf_param. Impact on performance should be null. quota enforcement enabled with a large limit for the user (via setquota). Impact on performance should be close to null. quota enforcement enabled with a limit close to expected usage (should still fit). Impact on performance to be compared with prior lustre release (2.1, 2.2 or 2.3) quota enforcement enabled with a limit smaller than usage (EDQUOT error expected). We should again compare with a prior lustre release. quota disabled via conf_param. Impact on performance should be NULL. 5. DNE support (both ldiskfs and zfs) --------------- sanity-quota with SLOW=yes with multiple MDTs space rebalancing for inodes (never exercised when one single MDT) impact on metadata performance with remote directory (on MDT1) while master still runs on MDT0 online MDT addition

          People

            cliffw Cliff White (Inactive)
            jlevi Jodi Levi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: