Description of problem: ======================= Following to Bug #1017144, Packstack should also support the l2population mechanism driver mentioned in Bug #1056594. At the moment, CONFIG_NEUTRON_ML2_MECHANISM_DRIVERS only accepts[1] openvswitch and linuxbridge as mechanism drivers [1] https://github.com/stackforge/packstack/blob/master/packstack/puppet/templates/neutron_ml2_plugin.pp#L3+L17 Version-Release number of selected component (if applicable): ============================================================= the most up to date packstack NVR: openstack-packstack-2014.1.1-0.4.dev1018.el6.noarch
Looking at the code and git log CONFIG_NEUTRON_ML2_MECHANISM_DRIVERS accepts following from the beginning of ML2 support: [para@elysium packstack]$ git show 7be825d7b3fcd5be5 | grep -A 12 "neutron-ml2-mechanism-drivers" + {"CMD_OPTION" : "neutron-ml2-mechanism-drivers", + "CONF_NAME" : "CONFIG_NEUTRON_ML2_MECHANISM_DRIVERS", + "USAGE" : ("A comma separated ordered list of " + "networking mechanism driver entrypoints " + "to be loaded from the " + "neutron.ml2.mechanism_drivers namespace."), + "PROMPT" : ("Enter a comma separated ordered list of " + "networking mechanism driver entrypoints"), + "OPTION_LIST" : ["logger", "test", "linuxbridge", + "openvswitch", "hyperv", "ncs", "arista", + "cisco_nexus", "l2population"], + "VALIDATORS" : [validators.validate_multi_options], + "DEFAULT_VALUE" : "openvswitch", Is there something else which needs to be configured to have l2population working?
(In reply to Martin Magr from comment #2) > Looking at the code and git log CONFIG_NEUTRON_ML2_MECHANISM_DRIVERS accepts > following from the beginning of ML2 support: > > [para@elysium packstack]$ git show 7be825d7b3fcd5be5 | grep -A 12 > "neutron-ml2-mechanism-drivers" > + {"CMD_OPTION" : "neutron-ml2-mechanism-drivers", > + "CONF_NAME" : "CONFIG_NEUTRON_ML2_MECHANISM_DRIVERS", > + "USAGE" : ("A comma separated ordered list of " > + "networking mechanism driver entrypoints " > + "to be loaded from the " > + "neutron.ml2.mechanism_drivers > namespace."), > + "PROMPT" : ("Enter a comma separated ordered list of " > + "networking mechanism driver > entrypoints"), > + "OPTION_LIST" : ["logger", "test", "linuxbridge", > + "openvswitch", "hyperv", "ncs", "arista", > + "cisco_nexus", "l2population"], > + "VALIDATORS" : [validators.validate_multi_options], > + "DEFAULT_VALUE" : "openvswitch", > > Is there something else which needs to be configured to have l2population > working? You need to append "l2population" to the comma seperated list of mechanism drivers, as well as enable the "l2_population" flag in the [agent] section of the plugin.ini file passed to every ovs/LB agent on every compute node and network node.
Of course value of CONFIG_NEUTRON_ML2_MECHANISM_DRIVERS is inserted to plugin.ini to parameter ml2/mechanism_drivers and (agent|vxlan)/l2_population is set to true if openvswitch/linuxbridge is cantained in mechanism drivers list together with l2population. So if this is it I'm gonna close this bug as WORKSFORME, unless there's other problem.
l2poplation was configured in answer file and into the plugins.ini file openstack-packstack-2014.1.1-0.20.dev1109.el7ost.noarch
Removing NEEDINFO since it has been tested by Ofer.