PDash 2.0
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Zorba |
New
|
Critical
|
Chris Hillery |
Bug Description
Functionality-wise, the general idea is to have a web-based interface to administer and configure the site. The two two most urgent and important capabilities I would like to have are
1. Be able to set the default baseline for each test, and
2. Be able to set the default starting date from which data is going to be displayed.
Other nice-to-haves are:
3. Be able to add/remove tests
4. Set the default number of times each test is going to be run (and remove this number from the name of the test).
5. Thin-out history, e.g. say for a particular period of time I want only 1 out of each 5 data point to be displayed.
It would be cool if all these config settings were on a per-user basis, but I think think this is something we should sweat too much about.
Another wish is to have a dedicated machine to run the tests, or at least make sure that while the tests are run, nothing else is running on that machine.
---
Mauro did a proposed "PDash 2.0" some time ago, but it is unclear whether that had any infrastructure or other significant improvements from what is run today.
Changed in zorba: | |
importance: | Undecided → Critical |
assignee: | nobody → Sorin Marian Nasoi (sorin.marian.nasoi) |
milestone: | none → 3.0 |
description: | updated |
summary: |
- release PDash 2.0 + PDash 2.0 |
tags: | added: new-functionality-requirement |
tags: | added: performance-problem |
Changed in zorba: | |
assignee: | Sorin Marian Nasoi (sorin.marian.nasoi) → Chris Hillery (ceejatec) |
Changed in zorba: | |
milestone: | 3.0 → 3.1 |
A correction:
It would be cool if all these config settings were on a per-user basis, but I think think this is something we should NOT sweat too much about.