[OSTF] Timeouts for operations should be set dynamically
Bug #1275667 reported by
Anastasiia Naboikina
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Invalid
|
Medium
|
Fuel Python (Deprecated) | ||
Bug Description
Timeouts in OSTF tests should be set up depending on the cluster nodes load.
First, it`s necessary to gather some metrics on what timeout values should be set with corresponding cluster load. Then, we can implement some code that polls cluster load and provides timeouts for different OSTF operations.
| Changed in fuel: | |
| milestone: | none → 5.0 |
| tags: | added: ostf |
| Changed in fuel: | |
| assignee: | nobody → Fuel QA Team (fuel-qa) |
| Changed in fuel: | |
| status: | New → Confirmed |
| Changed in fuel: | |
| assignee: | Fuel QA Team (fuel-qa) → Anastasiia Naboikina (anaboikina) |
| assignee: | Anastasiia Naboikina (anaboikina) → Fuel QA Team (fuel-qa) |
| Changed in fuel: | |
| milestone: | 5.0 → 5.1 |
| Changed in fuel: | |
| assignee: | Fuel QA Team (fuel-qa) → Fuel Python Team (fuel-python) |
| importance: | Low → Medium |
Revision history for this message
| Dima Shulyak (dshulyak) wrote | #1 |
| tags: | added: feature |
Revision history for this message
| Dmitry Pyzhov (dpyzhov) wrote | #2 |
| Changed in fuel: | |
| status: | Confirmed → Invalid |
To post a comment you must log in.
Actually it can not be done properly without external monitoring solution, even if zabbix will be merged in 5.1 - it is very complex task.
So if it is required - this should not be a bug, but a feature.