diff options
| author | Daniel P. Berrange <berrange@redhat.com> | 2013-01-04 13:03:38 +0000 |
|---|---|---|
| committer | Daniel P. Berrange <berrange@redhat.com> | 2013-01-30 14:33:13 +0000 |
| commit | 11aec7eccbbd786afb919c914404d33fbd690f36 (patch) | |
| tree | c009465797c1e16b0f2179e0af26606bfda1b04b /nova/utils.py | |
| parent | e0333fa56a0f998a5d44ebeade5b754875c3c7d3 (diff) | |
| download | nova-11aec7eccbbd786afb919c914404d33fbd690f36.tar.gz nova-11aec7eccbbd786afb919c914404d33fbd690f36.tar.xz nova-11aec7eccbbd786afb919c914404d33fbd690f36.zip | |
Merge QuantumLinuxBridgeVIFDriver into LibvirtGenericVIFDriver
The only difference between the Quantum bridge driver and the
new generic VIF driver bridge support is the name of the bridge.
This is now provided via the VIF mapping parameter, so there is
no need for the dedicated Quantum VIF driver for bridging. This
This has the advantage that libvirt firewall filter parameters
are correctly configured.
The QuantumLinuxBridgeVIFDriver class functionality is merged into
LibvirtGenericVIFDriver. For backwards compatibility with
the Folsom release, the existing QuantumLinuxBridgeVIFDriver class
is made to inherit from LibvirtGenericVIFDriver and directly
call the bridge specific setup APIs. This eases migration to
the new VIF impl during the Grizzly deployment lifecycle, with
an expectation that the QuantumLinuxBridgeVIFDriver stub will be
deleted after the Havana release.
Blueprint: libvirt-vif-driver
Change-Id: I19664f20e5137f495513999214f66279292bda58
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Diffstat (limited to 'nova/utils.py')
0 files changed, 0 insertions, 0 deletions