Bug 1290498

Summary: [RFE][nova]: Allow Neutron to specify OVS bridge name
Product: Red Hat OpenStack Reporter: Stephen Gordon <sgordon>
Component: openstack-novaAssignee: Russell Bryant <rbryant>
Status: CLOSED NEXTRELEASE QA Contact: nlevinki <nlevinki>
Severity: low Docs Contact:
Priority: low    
Version: 7.0 (Kilo)CC: berrange, dasmith, eglynn, kchamart, ndipanov, sbauza, sferdjao, sgordon, vromanso, yeylon
Target Milestone: Upstream M3Keywords: FutureFeature
Target Release: 10.0 (Newton)   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/nova/+spec/neutron-ovs-bridge-name
Whiteboard: upstream_milestone_mitaka-3 upstream_definition_approved upstream_status_implemented
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-08 19:50:55 UTC Type: ---
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: 1281573    

Description Stephen Gordon 2015-12-10 16:56:01 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/neutron-ovs-bridge-name.

Description:

(This blueprint is submitted as a specless blueprint.)

Nova currently gets the name of the OVS bridge to use from a nova.conf. configuration option.  nova/network/neutronv2/api.py contains the following:

     # TODO(berrange) temporary hack until Neutron can pass over the
     # name of the OVS bridge it is configured with
     cfg.StrOpt('ovs_bridge',
                default='br-int',
                help='Name of Integration Bridge used by Open vSwitch'),                                                                                                                                                                 

This blueprint proposes allowing Neutron to specify this in the VIF details that Neutron already sends to Nova.  The patch should be minimally invasive, as it should only affect the 2 places in the neutronv2.api code that currently read this configuration option.  It would grab it from VIF details if present, and fall back to the config option otherwise.

This came up as it would help with implementing the Neutron vlan-aware-vms spec with Neutron's OVS agent.  https://review.openstack.org/#/c/243786/   Even if not used there, it's still a very reasonable TODO item to knock out, as the choice of OVS bridge is really something Neutron should be specifying anyway, even if it's almost always br-int. 

Specification URL (additional information):

None
Comment 1 Mike McCune 2016-03-28 23:24:30 UTC 
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions