Improving the test framework: Difference between revisions

From OpenSFS Wiki
Jump to navigation Jump to search
No edit summary
(Remove meeting info; no longer meeting)
 
(5 intermediate revisions by 2 users not shown)
Line 2: Line 2:
There are three areas of focus for improving Lustre's self-testing infrastructure.  These three items can be complimentary and may (should) share some of the same features.
There are three areas of focus for improving Lustre's self-testing infrastructure.  These three items can be complimentary and may (should) share some of the same features.


* Development of a completely [[new test framework]] that will provide the capabilities to test Lustre at exascale.
* Development of a completely new test framework that will provide the capabilities to test Lustre at exascale.
* Incremental benefits by [[improving current test framework]].
* Incremental benefits by improving current test framework.
* Providing better coverage by [[improving individual tests]].
* Providing better coverage by improving individual tests.


Currently, we are in the process of collecting the [[test framework requirements]] to facilitate the above.  Background on the current problems and some possible solutions were presented by Chris Gearing and Nathan Rutman at LAD '12, available [http://www.eofs.eu/fileadmin/lad2012/22_Rutman-Gearing_Xyratex-Intel_Lustre_Testing_LAD_2012.pdf here].  These were more fully developed [http://goo.gl/mCtwU in a Google doc here] [Nathan can grant edit rights]). <br />


Meetings are 8:00am PST on Tuesdays<br />
We are also looking into alternatives for an upper-level (no Lustre knowledge) [[automation framework evaluation]].  This would be used to automatically deploy test resources and test requests, and track the results.
Bridge Info:
916-356-2663, Bridge: 1, Passcode: 1146033

Latest revision as of 14:21, 15 October 2014

There are three areas of focus for improving Lustre's self-testing infrastructure. These three items can be complimentary and may (should) share some of the same features.

  • Development of a completely new test framework that will provide the capabilities to test Lustre at exascale.
  • Incremental benefits by improving current test framework.
  • Providing better coverage by improving individual tests.

Currently, we are in the process of collecting the test framework requirements to facilitate the above. Background on the current problems and some possible solutions were presented by Chris Gearing and Nathan Rutman at LAD '12, available here. These were more fully developed in a Google doc here [Nathan can grant edit rights]).

We are also looking into alternatives for an upper-level (no Lustre knowledge) automation framework evaluation. This would be used to automatically deploy test resources and test requests, and track the results.