yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1101187] Re: in case ow two networks on the same bridge nova overwrites dnsmasq config

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Tom Fifield <1101187@xxxxxxxxxxxxxxxxxx>
Date: Fri, 01 Apr 2016 11:12:12 -0000
Reply-to: Bug 1101187 <1101187@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

Hi,

nova-network was designed for relatively simple networking use cases, so
it struggles to support things like this. However, for what you're
trying to achieve the neutron project should work very well! Check out
the networking guide at : http://docs.openstack.org/networking-guide/
and see about moving to neutron for this.

Given that this bug is a few years old now, I think it's time to close
it with our apologies.

** Changed in: nova
       Status: Confirmed => Won't Fix

** Changed in: nova (Ubuntu)
       Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1101187

Title:
  in case ow two networks on the same bridge nova overwrites dnsmasq
  config

Status in OpenStack Compute (nova):
  Won't Fix
Status in nova package in Ubuntu:
  Invalid

Bug description:
  Some background: I run a private cloud environment (folsom/stable,
  FlatDhcp) in the 172.17.11.XXX/24 range. The private range for
  instances is 192.168.100.XX/24 . Basically if I add a floating IP it
  get's assigned from the 172.17.11.XX/24 range. Recently, I needed to
  assign 172.17.11.XX fixed addresses for local usage.

  nova-manage network list

  1       192.168.100.0/24        None            192.168.100.2   8.8.4.4         None            None          
  3       172.17.11.224/28        None            172.17.11.226   8.8.8.8         None            None 

  This should happen on the same bridge (br100).

  Now when activating an instance with a fixed ip,
  /var/lib/nova/networks/nova-br100.conf gets overwitten. So I end up
  with only the 172.17.11.XXX fixed ip in that list. While i would
  expect 192.168 addresses and 172.17.11 addresses. It seems that nova
  is not able to handle multiple ipranges/dnsmasq on one bridge?

  As a workaround I activated the network on a new bridge. I needed to
  activate proxy_arp and change some iptables to make sure traffic gets
  to the instance. Not something really maintainable :).

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1101187/+subscriptions