nova-network doesn't handle large amount of concurrent booting instances well
Bug #1257788 reported by
Joe Gordon
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Fix Released
|
Low
|
Dan Smith | ||
| neutron |
Invalid
|
Medium
|
Venkata Siva Vijayendra Bhamidipati | ||
Bug Description
As seen by the large-ops test nova-network has trouble booting 150 VMs concurrently. Part of the problem is that setting up the network for each instance is relatively expensive with many locks and root-wrapped calls. Both of which significantly hurt performance. One possible fix would be to do more bulk network operations when possible, so instead of 100 separate calls to a root-wrapped tool call it once.
Revision history for this message
| Joe Gordon (jogo) wrote | #1 |
| Changed in nova: | |
| importance: | Undecided → Low |
Revision history for this message
| Joe Gordon (jogo) wrote | #2 |
Revision history for this message
| Joe Gordon (jogo) wrote | #3 |
| Changed in neutron: | |
| status: | New → Triaged |
| tags: | added: nova-neutron |
| Changed in neutron: | |
| importance: | Undecided → Medium |
| Changed in nova: | |
| status: | New → Triaged |
| Changed in neutron: | |
| assignee: | nobody → Venkata Siva Vijayendra Bhamidipati (vijayendra-bhamidipati) |
Revision history for this message
| Eugene Nikanorov (enikanorov) wrote | #4 |
| Changed in neutron: | |
| status: | Triaged → Invalid |
Revision history for this message
| Joe Gordon (jogo) wrote | #5 |
| Changed in nova: | |
| status: | Triaged → Fix Released |
| assignee: | nobody → Dan Smith (danms) |
To post a comment you must log in.
Setting this to a low priority because workarounds exist (run more nova-networks) and because nova-network is frozen.