openstack/devstack
Code Issues Proposed changes

Clone neutron_lbaas for midonet plugin

Browse Source 
MidoNet plugin needs the 'neutron_lbaas' module available when it
starts up without needing to start the LBaaS service.  After the
advanced service split, however, devstack clones 'neutron_lbaas'
only when the 'lbaas' service is enabled.  To get around this
conflict, clone 'neutron_lbaas' everytime midonet is configured
as the Neutron plugin.

Change-Id: Ide620db383fc44a66a84d00b2365ec2e846469fe
Closes-Bug: 1402242
This commit is contained in:
Ryu Ishimoto 2015-01-15 17:00:03 +00:00
parent 116f9f826e
commit 5bc957711d
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
lib/neutron_plugins/midonet
View File

@ -29,6 +29,18 @@ function neutron_plugin_configure_common {
Q_PLUGIN_CONF_PATH=etc/neutron/plugins/midonet
Q_PLUGIN_CONF_FILENAME=midonet.ini
Q_PLUGIN_CLASS="neutron.plugins.midonet.plugin.MidonetPluginV2"
# MidoNet implements LBaaS API in the plugin, not as an LBaaS driver.
# In this model, the plugin references the 'neutron_lbaas' module but
# does not require starting an LBaaS service. Devstack, however, clones
# 'neutron_lbaas' only if 'lbaas' service is enabled. To get around this,
# always clone 'neutron_lbaas' so that it is made available to the plugin.
# Also, discontinue if the 'lbaas' service is enabled.
if is_service_enabled q-lbaas; then
die $LINENO "LBaaS service should be disabled for the MidoNet plugin"
fi
git_clone $NEUTRON_LBAAS_REPO $NEUTRON_LBAAS_DIR $NEUTRON_LBAAS_BRANCH
setup_develop $NEUTRON_LBAAS_DIR
}
function neutron_plugin_configure_debug_command {