OpenStack Compute (nova)

introduce new FLAG for setting default DNSMASQ interface in nova-dhcpbridge

Bug #718621 reported by Christian Berendt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Wishlist
Josh Kearney
OpenStack Compute (nova) 2011.2 "cactus"

Bug Description

At the moment in nova-dhcpbridge there is 'br0' set as default value, if env variable DNSMASQ_INTERFACE is not set.

I would prefer setting the default value via a own flag dnsmasq_interface in /etc/nova/nova.conf.

106 interface = os.environ.get('DNSMASQ_INTERFACE', 'br0')

Related branches

lp:~jk0/nova/lp718621
Vish Ishaya (community): Needs Information
Devin Carlen (community): Approve
Diff: 21 lines (+3/-1)
1 file modified
bin/nova-dhcpbridge (+3/-1)
Thierry Carrez (ttx)
Changed in nova:
importance: Undecided → Wishlist
status: New → Confirmed
Josh Kearney (jk0)
Changed in nova:
status: Confirmed → In Progress
assignee: nobody → Josh Kearney (jk0)
Revision history for this message
Josh Kearney (jk0) wrote :

Added Devin's comment here for Vish: This fix makes something that will probably never need to be changed at least possible.

Josh Kearney (jk0)
Changed in nova:
status: In Progress → Fix Committed
Revision history for this message
Vish Ishaya (vishvananda) wrote :

To be more complete:
nova-dhcpbridge is started automatically by dnsmasq. The proper bridge is passed in by nova in the environment when it starts dnsmasq, so the existing 'br0' is never used in normal operations.

Now there is a flag, but the only time when the flag might be used is when starting nova-dhcpbridge by hand for some sort of testing scenario.

Thierry Carrez (ttx)
Changed in nova:
milestone: none → 2011.2
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.