Improving the test framework - Revision history

Spitzcor: Remove meeting info; no longer meeting

2014-10-15T21:21:55Z

Remove meeting info; no longer meeting

← Older revision		Revision as of 14:21, 15 October 2014
Line 9:		Line 9:

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

	~~Meetings are 8:00am PST on Tuesdays<br />~~
	~~Bridge Info:~~
	~~916-356-2663, Bridge: 1, Passcode: 1146033~~

Nrutman at 18:42, 18 January 2013

2013-01-18T18:42:00Z

← Older revision		Revision as of 11:42, 18 January 2013
Line 6:		Line 6:
	* 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].<br />		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 />

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

Spitzcor: Add link to LAD'12 presentation by Chris G. and Nathan R.

2013-01-17T18:31:37Z

Add link to LAD'12 presentation by Chris G. and Nathan R.

← Older revision		Revision as of 11:31, 17 January 2013
Line 6:		Line 6:
	* 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.<br />		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].<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.		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.

Nrutman at 21:56, 19 December 2012

2012-12-19T21:56:46Z

← Older revision		Revision as of 14:56, 19 December 2012
Line 6:		Line 6:
	* 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.		Currently, we are in the process of collecting the [[test framework requirements]] to facilitate the above.<br />
	We are also looking into alternatives for an upper-level (no Lustre knowledge) [[automation framework evaluation]].		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.

	Meetings are 8:00am PST on Tuesdays<br />		Meetings are 8:00am PST on Tuesdays<br />
	Bridge Info:		Bridge Info:
	916-356-2663, Bridge: 1, Passcode: 1146033		916-356-2663, Bridge: 1, Passcode: 1146033

Nrutman at 21:54, 19 December 2012

2012-12-19T21:54:51Z

← Older revision		Revision as of 14:54, 19 December 2012
Line 7:		Line 7:

	Currently, we are in the process of collecting the [[test framework requirements]] to facilitate the above.		Currently, we are in the process of collecting the [[test framework requirements]] to facilitate the above.
			We are also looking into alternatives for an upper-level (no Lustre knowledge) [[automation framework evaluation]].

	Meetings are 8:00am PST on Tuesdays<br />		Meetings are 8:00am PST on Tuesdays<br />
	Bridge Info:		Bridge Info:
	916-356-2663, Bridge: 1, Passcode: 1146033		916-356-2663, Bridge: 1, Passcode: 1146033

Nrutman at 00:28, 19 December 2012

2012-12-19T00:28:23Z

← Older revision		Revision as of 17:28, 18 December 2012
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.

	Meetings are 8:00am PST on Tuesdays<br />		Meetings are 8:00am PST on Tuesdays<br />
	Bridge Info:		Bridge Info:
	916-356-2663, Bridge: 1, Passcode: 1146033		916-356-2663, Bridge: 1, Passcode: 1146033

Nrutman at 00:20, 19 December 2012

2012-12-19T00:20:10Z

← Older revision		Revision as of 17:20, 18 December 2012
Line 5:		Line 5:
	* 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]].


			Meetings are 8:00am PST on Tuesdays<br />
			Bridge Info:
			916-356-2663, Bridge: 1, Passcode: 1146033

Nrutman: Created page with " 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. ..."

2012-12-19T00:10:34Z

Created page with " 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. ..."

New page

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