This patch changes the OVN module from DevStack to allow for using the OSapackaged version of OVN instead of compiling it from source. A new variable called OVN_BUILD_FROM_SOURCE has been introduced and when set to False (the default value) OVN will then use the packaged version for setting up DevStack. Note, in the stop_ovn() function, the OVN metadata agent service name was wrong and the service wasn't being stopped as part of ./unstack.sh. This patch also fixed it as well. Change-Id: Ib41e3b486550200572afd6b3ba783d7644d70d44 Signed-off-by: Lucas Alvares Gomes <lucasagomes@gmail.com> Co-Authored-By: Slawek Kaplonski <skaplons@redhat.com>
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_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