[edit] WARNING: This is the _old_ Lustre wiki, and it is in the process of being retired. The information found here is all likely to be out of date. Please search the new wiki for more up to date information.

If you want to try out a feature in your Lustre environment, use the appropriate feature test plan to verify the functionality. We '''especially''' need help with large-scale feature testing beyond the scope of our test systems. After testing, report your results by clicking the '''Discussion''' tab at the top of the page and entering:

+

If you want to try out a feature in your Lustre environment, use the appropriate feature test plan to verify the functionality. We ''especially'' need help with large-scale feature testing beyond the scope of our test systems. After testing, report your results by clicking the ''Discussion'' tab at the top of the page and entering:

* Your name and email address

* Your name and email address

Revision as of 21:16, 9 December 2009

Test plans for upcoming Lustre releases are now available for review and comment. As an open-source product, we invite the Lustre user community to contribute to our efforts to develop and test a more robust, feature-rich Lustre.

Commenting on the Test Plans

If you want to comment on a test plan, click the Discussion tab at the top of the page and enter:

Your name and email address

Date of your comment

Test plan you are commenting on (e.g., 1.8, VBR, etc.) and page number, if applicable

Comment or suggestion. If you have a proposed test case, paste it into your comment.

The Lustre Test group will review these comments, update test plans as needed, and post updated plans to this page.

Feature Testing with the Test Plans

If you want to try out a feature in your Lustre environment, use the appropriate feature test plan to verify the functionality. We especially need help with large-scale feature testing beyond the scope of our test systems. After testing, report your results by clicking the Discussion tab at the top of the page and entering:

Adaptive Timeouts

CMD

This is the Large-Scale Test Plan for CMD. The objective is to test the Clustered MetaData (CMD) feature at scale, and verify that performance improvements are seen with CMD, as compared to a single MDT configuration.

NOTE: CMD is designed for use only on non-production Lustre systems.

OSS Read Cache

This is the Large-Scale Test Plan for OSS Read Cache. The goal is to test OSS Read Cache on a large-scale system to be sure the feature scales, and verify that performance data, when OSS read cache is enabled, is better than data when the feature is disabled.

OST Pools

This is the Large-Scale Test Plan for OST Pools. The objective is to test OST Pools on a large-scale cluster to make sure the feature is scalable, and verify that file creation performance is the same (with or without OST Pools).

Quotas

Thoroughly test the quotas feature (block and inode quotas for users and groups) for each new Lustre release (during pre-release testing)

Focus on quotas hard limits

Find and document problems with quotas (and add them as release blockers).

Deliver working quotas feature code to Cray, Inc. with each new Lustre release and avoid bugs (especially regressions)

The components to be tested are:

ldiskfs

Lustre

lustre quotas feature code

Lustre Security

This is the Test Plan for Security Features. The test plan's objective is to find defects in the Lustre 2.0 security features and drive the security source code to a stable, production-ready state. The test plan contains:

Complete acceptance-small (acc-sm) run that shifts among different security flavors (null, krb5i and krb5p) between tests.