[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.

Lustre Test Plans

From Obsolete Lustre Wiki
(Difference between revisions)
Jump to: navigation, search
(Feature Testing)
Line 18: Line 18:
 
=== Lustre 2.0 Test Plan (coming soon) ===
 
=== Lustre 2.0 Test Plan (coming soon) ===
  
== Feature Testing ==
+
==Feature Testing==
  
=== Lustre Security ===
+
These are the feature test plans used by the Lustre QE team.
 +
 
 +
===OST Pools===
 +
 
 +
This is the [http://wiki.lustre.org/images/0/0e/Ostpools-large-scale-tp.pdf 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===
 +
 
 +
 
 +
===Lustre Security===
  
 
This is the [http://wiki.lustre.org/images/3/35/SecurityTestPlan.pdf 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:  
 
This is the [http://wiki.lustre.org/images/3/35/SecurityTestPlan.pdf 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 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.
 
  
=== Feature 2 ===
+
* 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.
  
=== Feature 3 ===
+
===Version-Based Recovery===

Revision as of 18:52, 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.

Contents

Release Testing

Test plans are available for upcoming Lustre releases.

Lustre 1.8 Test Plan

Lustre 2.0 Test Plan (coming soon)

Feature Testing

These are 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

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

Personal tools
Navigation