dos.py revert-resume is pretty slow and ineffective
Bug #1611933 reported by
Sergey Yudin
This bug affects 4 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Confirmed
|
Medium
|
Fuel QA Team | ||
| Mitaka |
Confirmed
|
Medium
|
Fuel QA Team | ||
Bug Description
Hello.
devops reverts environment in quite ineffective way in a single thread. On relatively big environments it takes long time. Is that possible to revert environments in parallel and make concurrency configurable through cli?
Workload cause by revert of environment with ~40 nodes in attachment.
Revision history for this message
| Sergey Yudin (tsipa740) wrote | #1 |
| description: | updated |
| Changed in fuel: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| assignee: | nobody → Fuel CI (fuel-ci) |
| milestone: | none → 10.0 |
| Changed in fuel: | |
| assignee: | Fuel CI (fuel-ci) → Fuel QA Team (fuel-qa) |
| status: | Confirmed → New |
Revision history for this message
| Dennis Dmitriev (ddmitriev) wrote | #2 |
| Changed in fuel: | |
| status: | New → Confirmed |
To post a comment you must log in.
Libvirt is pretty unstable if it do some actions in parallel at the same time.
Use 'dos.py revert ... && dos.py resume ...' if you don't need to syncronize time on your environment, it will be much faster.