summaryrefslogtreecommitdiffstats
path: root/nova/exception.py
diff options
context:
space:
mode:
authorDaniel P. Berrange <berrange@redhat.com>2013-01-04 12:22:20 +0000
committerDaniel P. Berrange <berrange@redhat.com>2013-01-10 10:25:30 +0000
commit4babf7d7e12f35c137148727842f7af28312e858 (patch)
tree567bfefb13959e1d90f27f6d0762aa2c834128f0 /nova/exception.py
parentf863697be1cf1abc49805f1345b81f49ba4556b4 (diff)
downloadnova-4babf7d7e12f35c137148727842f7af28312e858.tar.gz
nova-4babf7d7e12f35c137148727842f7af28312e858.tar.xz
nova-4babf7d7e12f35c137148727842f7af28312e858.zip
Make Quantum plugin fill in the 'bridge' name
There is a comment in the quantum driver code that says it ignores the 'bridge' name field. This is misleading, because the bridge name is still required by any virt drivers when configuring VIFs so they know how to connect them. Currently the libvirt Bridge driver invents a bridge name based on 'qbr' and network['id'], while the OVS drivers use the libvirt_ovs_bridge config. Move this logic into the Quantum driver, renaming the config option to quantum_ovs_bridge. The config option should go away completely once Quantum can pass across the name, as it does for vif_type Blueprint: libvirt-vif-driver Change-Id: Ib043e1e6af5712ae1d1665cdca2e9fdbc89d4351 Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Diffstat (limited to 'nova/exception.py')
0 files changed, 0 insertions, 0 deletions