openstack/devstack
Code Issues Proposed changes
28491ef1f2
devstack/lib/neutron_plugins
History
Dean Troyer e3a9160c0d Fix Neutron plugin XTRACE handling 
The various Neutron plugin files need to have unique variables for the
xtrace state as they are sometimes nested more than two levels deep
and MY_XTRACE is getting stomped.  This gives each of the neutron_plugin
and neutron_thirdparty include files a unique XTRACE state variable.

I don't think this is a problem with any of the other plugin include
files (yet) so this just handles Neutron for now.

Change-Id: I7c272a48e7974edecaff5f431ff7443dd6622588
2014-03-28 12:40:59 -05:00
..
services Fix Neutron plugin XTRACE handling 2014-03-28 12:40:59 -05:00
bigswitch_floodlight Fix Neutron plugin XTRACE handling 2014-03-28 12:40:59 -05:00
brocade Enforce function declaration format in bash8 2014-02-28 07:59:03 +11:00
cisco Fix Neutron plugin XTRACE handling 2014-03-28 12:40:59 -05:00
embrane Fix Neutron plugin XTRACE handling 2014-03-28 12:40:59 -05:00
ibm Fix Neutron plugin XTRACE handling 2014-03-28 12:40:59 -05:00
linuxbridge Fix Neutron plugin XTRACE handling 2014-03-28 12:40:59 -05:00
linuxbridge_agent Enforce function declaration format in bash8 2014-02-28 07:59:03 +11:00
midonet Fix Neutron plugin XTRACE handling 2014-03-28 12:40:59 -05:00
ml2 Fix Neutron plugin XTRACE handling 2014-03-28 12:40:59 -05:00
nec Fix Neutron plugin XTRACE handling 2014-03-28 12:40:59 -05:00
nuage Fix Neutron plugin XTRACE handling 2014-03-28 12:40:59 -05:00
ofagent_agent Fix Neutron plugin XTRACE handling 2014-03-28 12:40:59 -05:00
oneconvergence Fix Neutron plugin XTRACE handling 2014-03-28 12:40:59 -05:00
openvswitch Fix Neutron plugin XTRACE handling 2014-03-28 12:40:59 -05:00
openvswitch_agent Fix Neutron plugin XTRACE handling 2014-03-28 12:40:59 -05:00
ovs_base Fix Neutron plugin XTRACE handling 2014-03-28 12:40:59 -05:00
plumgrid Fix Neutron plugin XTRACE handling 2014-03-28 12:40:59 -05:00
README.md update for name change to Neutron 2013-07-07 00:15:11 -04:00
ryu Fix Neutron plugin XTRACE handling 2014-03-28 12:40:59 -05:00
vmware_nsx Fix Neutron plugin XTRACE handling 2014-03-28 12:40:59 -05:00

README.md

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.

functions

lib/neutron calls the following functions when the $Q_PLUGIN is enabled

  • neutron_plugin_create_nova_conf : set NOVA_VIF_DRIVER and optionally set options in nova_conf e.g. NOVA_VIF_DRIVER=${NOVA_VIF_DRIVER:-"nova.virt.libvirt.vif.LibvirtGenericVIFDriver"}
  • neutron_plugin_install_agent_packages : install packages that is specific to plugin agent e.g. install_package bridge-utils
  • neutron_plugin_configure_common : set plugin-specific variables, Q_PLUGIN_CONF_PATH, Q_PLUGIN_CONF_FILENAME, Q_DB_NAME, 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 1
  • neutron_plugin_check_adv_test_requirements: return 0 if requirements are satisfied otherwise return 1