Bug 1279615 - [RFE] Support explicit configuration of L2 population
[RFE] Support explicit configuration of L2 population
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates (Show other bugs)
8.0 (Liberty)
Unspecified Unspecified
medium Severity unspecified
: ga
: 8.0 (Liberty)
Assigned To: Jiri Stransky
Amit Ugol
: FutureFeature
Depends On: 1271335
  Show dependency treegraph
Reported: 2015-11-09 16:00 EST by Brent Eagles
Modified: 2016-04-07 17:42 EDT (History)
8 users (show)

See Also:
Fixed In Version: openstack-tripleo-heat-templates-0.8.7-5.el7ost
Doc Type: Enhancement
Doc Text:
This update allows enabling of the Neutron L2 population feature. This helps reduce the amount of broadcast traffic in Tenant networks. Set the NeutronEnableL2Pop parameter in an environment file's 'default_parameters' section to enable Neutron L2 population.
Story Points: ---
Clone Of: 1271335
Last Closed: 2016-04-07 17:42:12 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
OpenStack gerrit 244723 None None None Never

  None (edit)
Description Brent Eagles 2015-11-09 16:00:39 EST
+++ This bug was initially created as a clone of Bug #1271335 +++

Support explicit configuration of L2 population in the overcloud:

The relevant configuration options are made to ml2_conf.ini on the controller.

# Insert l2population into the list of ML2 mechanism drivers
mechanism_drivers=...,l2population, ...

# enable l2 population in the agent configuration on all nodes running the agents
# (computes and network controllers)
# for openvswitch
l2_population = [True|False]

# for linuxbridge
l2_population = [True|False]
Comment 2 Brent Eagles 2015-11-12 10:53:44 EST
Patch u/s for review to enable the variable in heat. It can be enabled/disable through a parameter override in a heat environment file at deployment time. Support for mechanism driver configuration already exists so it should be configurable the same way.
Comment 4 Nir Yechiel 2015-12-30 04:43:46 EST
Hi Brent,

It looks like your upstream patch is merged now. Can you confirm that this is going to be included with OSP-8 or do we need a backport for that?

Comment 5 Brent Eagles 2016-01-05 08:42:19 EST
Hi Nir,

I checked with Mike Burns and it seems like a rebase is expected so this should get in. We'll need to keep an eye on it.
Comment 8 errata-xmlrpc 2016-04-07 17:42:12 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.