christoph/fail
1
Fork 0
Code Releases Activity

wishlist for ideas/wishes from a user perspective

Browse Source 
Please add all kinds of weird ideas, nice-to-haves, or inconveniences (with or
without suggestions on how to deal with them) you experience when using Fail*.

git-svn-id: https://www4.informatik.uni-erlangen.de/i4svn/danceos/trunk/devel/fail@1600 8c4709b5-6ec9-48aa-a5cd-a96041d1645a
This commit is contained in:
hsc
2012-09-06 15:07:13 +00:00
parent 0349f3dfee
commit e25b4aeea0
1 changed files with 12 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
doc/wishlist.txt Normal file
View File

@ -0,0 +1,12 @@
This file documents ideas/wishes especially from a Fail* *user* perspective.
- Recurring Fail* API usage patterns in experiment/campaign implementations
(that could be implemented in a reusable way, e.g. in a library that sits
between the Fail* API and the experiment)
* Fault-space pruning (FIXME elaborate)
* Preparation vs. final experiment steps -> cmake-driven, automatically
build 2 fail-client binaries? (FIXME elaborate)
* ...
- Campaign distribution: More foolproof host CPU load/local users/RAM usage
examination