[Task-Based] Deployment task scheduler should the most wanted task
Bug #1526501 reported by
Vladimir Kuklin
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Fix Released
|
High
|
Dmitry Ilyin | ||
| 8.0.x |
Fix Released
|
High
|
Dmitry Ilyin | ||
Bug Description
Currently, with task-based deployment in astute we have suboptimal task scheduling. All the avaialable tasks are equal for the scheduler, although it should be not. If there is a task that is more wanted by tasks on the other nodes, it should have higher priority for execution. Essentially, it means that task priority should be set according to the amount of tasks which depend on it.
| tags: | added: tbd-astute |
| Changed in fuel: | |
| assignee: | Fuel Python Team (fuel-python) → Vladimir Kuklin (vkuklin) |
| status: | Confirmed → In Progress |
| tags: | added: feature-task-based |
| summary: |
- Task Based Deployment task scheduler should the most wanted task + [Task-Based] Deployment task scheduler should the most wanted task |
| tags: | added: area-python |
| tags: | added: team-enhancements |
| Changed in fuel: | |
| assignee: | Vladimir Kuklin (vkuklin) → Vladimir Sharshov (vsharshov) |
| no longer affects: | fuel/mitaka |
Revision history for this message
| Vladimir Sharshov (vsharshov) wrote | #1 |
| Changed in fuel: | |
| assignee: | Vladimir Sharshov (vsharshov) → Dmitry Ilyin (idv1985) |
| status: | In Progress → Fix Committed |
| Changed in fuel: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This problem was solved in this commit: https:/