f652e0fb6d
This patch makes it easier to support the all-in-one installation of
XenServer with Quantum:
- separate agents for domU and dom0 openvswitches. The domU agent's name
is "q-domua", and the dom0 agent is called "q-agt"
- create a physnet1 physical network to connect those openvswitches
Note: This patch depends on the quantum patch:
https://review.openstack.org/15022
For a diagram, see:
http://goo.gl/BuAdg
Change-Id: Iff851438553528b9051edd380ecbb2c0415cbf78
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 1quantum_plugin_check_adv_test_requirements: return 0 if requirements are satisfied otherwise return 1