5aa2014e67
override-defaults mechanism allows us to define s_neutron_plugin_security_group before loading lib/neutron, and we no longer need to have a plugin-specific file in the master DevStack repository. Change-Id: I78a4e05fa72b1dd545b8d9e97a8fd8fdbf23739c Depends-On: Id6765245459c1aff3aab27dbc60d320ce2951b38 |
||
---|---|---|
.. | ||
services | ||
bigswitch_floodlight | ||
brocade | ||
cisco | ||
embrane | ||
linuxbridge_agent | ||
midonet | ||
ml2 | ||
nuage | ||
openvswitch | ||
openvswitch_agent | ||
ovs_base | ||
README.md | ||
vmware_dvs | ||
vmware_nsx | ||
vmware_nsx_v | ||
vmware_nsx_v3 |
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_CLASS
neutron_plugin_configure_debug_command
neutron_plugin_configure_dhcp_agent
neutron_plugin_configure_l3_agent
neutron_plugin_configure_plugin_agent
neutron_plugin_configure_service
neutron_plugin_setup_interface_driver
has_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