df875c5f16
XenServer already support OVS native mode and I have a patch for configuring it https://review.openstack.org/#/c/372952/ which is fine. But we have another patch which revert the usage of ml2_confi.ini and ml2_conf.ini.domU https://review.openstack.org/#/c/396573/. Both patches work well separately. But the two should have some dependent relationship. Once one merged, the other should change accordingly. Sorry that we missed the dependency. This patch is to fix the ovs config based on reverted ml2_conf.ini and ml2_conf.ini.domU to make sure we configure the correct IP for ovs agent Change-Id: Ib53e37e210cc849f161dd6630f81e5b2331a91d5
Neutron plugin specific files
Neutron plugins require plugin specific behavior.
The files under the directory, lib/neutron_plugins/, will be used
when their service is enabled.
Each plugin has lib/neutron_plugins/$Q_PLUGIN and define the following
functions.
Plugin specific configuration variables should be in this file.
- filename:
$Q_PLUGIN- The corresponding file name MUST be the same to plugin name
$Q_PLUGIN. Plugin specific configuration variables should be in this file.
- The corresponding file name MUST be the same to plugin name
functions
lib/neutron-legacy calls the following functions when the $Q_PLUGIN is enabled
neutron_plugin_create_nova_conf: optionally set options in nova_confneutron_plugin_install_agent_packages: install packages that is specific to plugin agent e.g. install_package bridge-utilsneutron_plugin_configure_common: set plugin-specific variables,Q_PLUGIN_CONF_PATH,Q_PLUGIN_CONF_FILENAME,Q_PLUGIN_CLASSneutron_plugin_configure_debug_commandneutron_plugin_configure_dhcp_agentneutron_plugin_configure_l3_agentneutron_plugin_configure_plugin_agentneutron_plugin_configure_serviceneutron_plugin_setup_interface_driverhas_neutron_plugin_security_group: return 0 if the plugin support neutron security group otherwise return 1neutron_plugin_check_adv_test_requirements: return 0 if requirements are satisfied otherwise return 1