diff options
| author | Daniel P. Berrange <berrange@redhat.com> | 2013-01-16 16:55:05 +0000 |
|---|---|---|
| committer | Daniel P. Berrange <berrange@redhat.com> | 2013-01-16 20:28:22 +0000 |
| commit | 84341f7c51dca01c03d2d0a771f1afadc8b5131f (patch) | |
| tree | aed18d689c208fcc5bc83395267ebb397e7d73eb /setup.py | |
| parent | b709a9a80851d3c2c6242da960a318433d1f4aee (diff) | |
| download | nova-84341f7c51dca01c03d2d0a771f1afadc8b5131f.tar.gz nova-84341f7c51dca01c03d2d0a771f1afadc8b5131f.tar.xz nova-84341f7c51dca01c03d2d0a771f1afadc8b5131f.zip | |
Fix fallback when Quantum doesn't provide a 'vif_type'
In
commit 4babf7d7e12f35c137148727842f7af28312e858
Author: Daniel P. Berrange <berrange@redhat.com>
Date: Fri Jan 4 12:22:20 2013 +0000
Make Quantum plugin fill in the 'bridge' name
We changed libvirt VIF driver to pull 'bridge' out of the
VIF model. This only worked for new Quantum drivers that
provide the 'vif_type' portbinding metadata though. This
patch effectively reverts part of that patch, so we have
a combination of the new & old method for determining
bridge names. The libvirt VIF driver will look at the
network['bridge'] field first, and if missing will fallback
to its previous logic which hardcoded bridge names.
Bug: 1100199
Change-Id: I5fd66b0303159c42bd227e97ddab381b2b67670c
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Diffstat (limited to 'setup.py')
0 files changed, 0 insertions, 0 deletions