launchpad development|
Size: 1450
Comment:
|
← Revision 8 as of 2012-04-12 00:47:39 ⇥
Size: 1766
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 6: | Line 6: |
| '''Current week:''' 1<<BR>> '''Next [[PolicyandProcess/FeatureDevelopmentCheckpoint|checkpoint]]:''' TBD |
'''Current week:''' 14<<BR>> '''Next [[PolicyandProcess/FeatureDevelopmentCheckpoint|checkpoint]]:''' 2012-04-18 |
| Line 27: | Line 27: |
| || Secure test hardware || flacoste || 2012-01-20 || IN-PROGRESS || || Secure production hardware || flacoste || 2012-02-22 || || |
|| Secure test hardware || flacoste || 2012-02-28 || COMPLETED || || Get repeatable deployment story || yellow || 2012-03-07 || COMPLETED || || Determine scaling behavior || yellow || 2012-03-27 (2012-03-07) || IN-PROGRESS|| || Root out instability || yellow || 2012-03-21 || IN-PROGRESS || || Secure production hardware || flacoste || 2012-04-04 (2012-03-07) || || |
| Line 38: | Line 41: |
| * [[12W9MbXPJ746x3I7YRbL2iBBPfjVJxWEGyOs3Quiwzr8|2012-01-05 kick-off call]] | * [[https://docs.google.com/document/d/12W9MbXPJ746x3I7YRbL2iBBPfjVJxWEGyOs3Quiwzr8/edit|2012-01-05 kick-off call]] <<PageList(regex:^Projects/ParallelTesting/Checkpoint-*)>> |
| Line 40: | Line 44: |
| == ACtion items for next checkpoint == | == Action items for next checkpoint == |
| Line 42: | Line 46: |
| * [yellow] Reproduce existing parallel LXC setup * [yellow] Close some of the existing bugs * [flacoste] Requisition test hardware * [yellow] Establish experimental plan to assess final hardware need. * [yellow] Make prediction for success criteria |
* [yellow] Bug fixes for test failures discovered in parallel test runs. * [yellow] Scaling assessment based on experimental results * [yellow] Get data center box running tests, and have a single comparison run with ec2. |
Parallel Testing
See also paralleltest bug tag
Squad started: 2012-01-02
Current week: 14
Next checkpoint: 2012-04-18
Scope
Out of scope
As documented in the LEP.
Blockers
None
Deliverables
Whatever you need to keep track of deliverables. An example, including some common ones is included below. Deliverables often correspond to a group of user stories or a single user story
Item |
Owner |
Expected date |
Status |
Signed off LEPs |
lifeless |
2012-01-05 |
COMPLETED |
Secure test hardware |
flacoste |
2012-02-28 |
COMPLETED |
Get repeatable deployment story |
yellow |
2012-03-07 |
COMPLETED |
Determine scaling behavior |
yellow |
2012-03-27 (2012-03-07) |
IN-PROGRESS |
Root out instability |
yellow |
2012-03-21 |
IN-PROGRESS |
Secure production hardware |
flacoste |
2012-04-04 (2012-03-07) |
|
Feature documentation |
gary |
|
|
Blog post |
gary |
|
|
Notes
Checkpoints Notes
Action items for next checkpoint
- [yellow] Bug fixes for test failures discovered in parallel test runs.
- [yellow] Scaling assessment based on experimental results
- [yellow] Get data center box running tests, and have a single comparison run with ec2.
