Bug 1271335

Summary: [RFE] Support explicit configuration of L2 population
Product: [Community] RDO Reporter: Brent Eagles <beagles>
Component: rdo-managerAssignee: Brent Eagles <beagles>
Status: CLOSED CURRENTRELEASE QA Contact: Shai Revivo <srevivo>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: bderzhavets, chris.brown, jstransk, mburns, nyechiel, racedoro
Target Milestone: ---   
Target Release: Liberty   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Feature: Allow enabling Neutron L2 population feature. Reason: E.g. to reduce the amount of broadcast traffic in tenant networks. Result: Neutron L2 population can be optionally enabled using the NeutronEnableL2Pop parameter.
Story Points: ---
Clone Of:
: 1279615 (view as bug list) Environment:
Last Closed: 2017-06-18 07:30:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1279615    

Description Brent Eagles 2015-10-13 16:43:35 UTC
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
[ml2]
mechanism_drivers=...,l2population, ...


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

# for linuxbridge
[vxlan]
l2_population = [True|False]

Comment 2 Mike McCune 2016-03-28 22:19:01 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 4 Christopher Brown 2017-06-18 07:30:48 UTC
Change was merged so closing...