fixes bug 1179820 we must set firewall driver if we want to use quantum security group because quantum will disable security group if we do not change the default firewall driver. Currently devstack will not change the default firewall driver if we just running quantum server on a node which will cause nova unable to security group information. Change-Id: Ie274325decbf252630a237ed3d6ee3136eb259fe
Quantum plugin specific files
Quantum plugins require plugin specific behavior.
The files under the directory, lib/quantum_plugins/, will be used
when their service is enabled.
Each plugin has lib/quantum_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/quantum calls the following functions when the $Q_PLUGIN is enabled
quantum_plugin_create_nova_conf: setNOVA_VIF_DRIVERand optionally set options in nova_conf e.g. NOVA_VIF_DRIVER=${NOVA_VIF_DRIVER:-"nova.virt.libvirt.vif.LibvirtGenericVIFDriver"}quantum_plugin_install_agent_packages: install packages that is specific to plugin agent e.g. install_package bridge-utilsquantum_plugin_configure_common: set plugin-specific variables,Q_PLUGIN_CONF_PATH,Q_PLUGIN_CONF_FILENAME,Q_DB_NAME,Q_PLUGIN_CLASSquantum_plugin_configure_debug_commandquantum_plugin_configure_dhcp_agentquantum_plugin_configure_l3_agentquantum_plugin_configure_plugin_agentquantum_plugin_configure_servicequantum_plugin_setup_interface_driverhas_quantum_plugin_security_group: return 0 if the plugin support quantum security group otherwise return 1