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.

Difference between revisions of "Lustre Test Plans"

From Obsolete Lustre Wiki
Jump to navigationJump to search
Line 20: Line 20:
 
==Feature Testing==
 
==Feature Testing==
  
These are the feature test plans used by the Lustre QE team.  
+
This section lists the feature test plans used by the Lustre QE team.  
  
 
===OST Pools===
 
===OST Pools===
Line 28: Line 28:
 
===Quotas===
 
===Quotas===
  
 +
This is the [http://wiki.lustre.org/images/9/9c/Quotas-tp.pdf Lustre Quotas Test Plan]. The test plan's objective is to:
 +
 +
*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===
 
===Lustre Security===

Revision as of 12:59, 13 November 2008

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.

If you would like to comment on the posted test plans, 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.6.6, 1.8, 2.0) 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.

Release Testing

Test plans are available for upcoming Lustre releases.

Lustre 1.8 Test Plan

Lustre 2.0 Test Plan (coming soon)

Feature Testing

This section lists the feature test plans used by the Lustre QE team.

OST Pools

This is the Lustre 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 with OST Pools).

Quotas

This is the Lustre Quotas Test Plan. The test plan's objective is to:

  • 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 Lustre Test Plan for Security Features. The test plan's objective is to find defects in 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.
  • Complete I/O benchmark (IOR and mdsrate), to run against all Lustre-supported security flavors (null, plain, krb5n, krb5a, krb5i and krb5p), gather and analyze performance data.

Version-Based Recovery