improve documentation on strategy
Bug #1623486 reported by
David TARDIVEL
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
watcher |
Fix Released
|
High
|
Susanne Balle |
Bug Description
I tried to use the strategy workload_
I think we should propose a strategy documentation template with required section such as:
. Main purpose
. Metrics required (name, description, how to collect them ...)
. (opt) Parameters full description
. Algorithm main specification
. External links (publication, blogs, ...)
...
description: | updated |
Changed in watcher: | |
status: | New → Triaged |
Changed in watcher: | |
milestone: | none → ocata-1 |
importance: | Undecided → High |
Changed in watcher: | |
assignee: | nobody → David TARDIVEL (david-tardivel) |
Changed in watcher: | |
status: | Triaged → In Progress |
Changed in watcher: | |
status: | In Progress → Fix Committed |
status: | Fix Committed → Fix Released |
Changed in watcher: | |
status: | Fix Released → Triaged |
status: | Triaged → In Progress |
milestone: | ocata-1 → ocata-2 |
assignee: | David TARDIVEL (david-tardivel) → nobody |
assignee: | nobody → Susanne Balle (susanne-balle) |
To post a comment you must log in.
+1 It will be very useful since almost all watcher strategies contain pretty hard algorithm inside.