7bc9b81699
There are two in-tree options for the xenserver.vif_driver, the bridge driver and the ovs driver. The XenAPI subteam has confirmed that the bridge driver is for nova-network (which is deprecated) and the ovs driver is for Neutron, and that's how things are tested in CI. Since we changed the default on use_neutron to be True for Ocata we need to change the default on the vif_driver to be the ovs driver so it works with the default config, which is Neutron. We're deprecating the option though since we can use the use_neutron option to decide which vif driver to load - which will make deploying and configuring nova with xen as the backend simpler. Change-Id: I599f3449f18d2821403961fb9d52e9a14dd3366b
14 lines
630 B
YAML
14 lines
630 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
The default value for the ``[xenserver]/vif_driver`` configuration option
|
|
has been changed to ``nova.virt.xenapi.vif.XenAPIOpenVswitchDriver`` to
|
|
match the default configuration of ``[DEFAULT]/use_neutron=True``.
|
|
deprecations:
|
|
- |
|
|
The ``[xenserver]/vif_driver`` configuration option is deprecated for
|
|
removal. The ``XenAPIOpenVswitchDriver`` vif driver is used for Neutron and
|
|
the ``XenAPIBridgeDriver`` vif driver is used for nova-network, which
|
|
itself is deprecated. In the future, the ``use_neutron`` configuration
|
|
option will be used to determine which vif driver to load.
|