[Bug 1067669] Re: Mapping same bridge to different phyiscal networks succeed

2013-04-04 Thread Thierry Carrez
** Changed in: quantum Milestone: grizzly-1 = 2013.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1067669 Title: Mapping same bridge to different phyiscal networks succeed To manage

[Bug 1067669] Re: Mapping same bridge to different phyiscal networks succeed

2013-03-07 Thread Robert Kukura
Eric, It sounds like your DEV_WDMZ ... DEV_FDMZ are all VLANs on the same physical network. If so, you should just set something like network_vlan_ranges = DEV_TRUNK on the quantum server, and physical_interface_mappings = DEV_TRUNK:bond0 on the compute and network nodes. The linuxbridge server

[Bug 1067669] Re: Mapping same bridge to different phyiscal networks succeed

2013-03-07 Thread Eric Hankins
Thanks for the information Bob, much appreciated. I had it in my head that the network name i was specifying in my quantum net-create command needed to map all the way down to the physical_interface_mappings keys. Now that I think about it, the --provider:physical_network phys-net- name is the

[Bug 1067669] Re: Mapping same bridge to different phyiscal networks succeed

2013-03-06 Thread Eric Hankins
I'm not sure if this bug has affected me, but the fix seems to be affecting me, and I'm now confused about my understanding of the network_vlan_ranges and physical_interface_mappings configs. My scenario is strictly provider network with a bunch of 802.1q VLANs riding a single bond, managed via

[Bug 1067669] Re: Mapping same bridge to different phyiscal networks succeed

2013-01-29 Thread Launchpad Bug Tracker
This bug was fixed in the package quantum - 2012.2.1-0ubuntu1 --- quantum (2012.2.1-0ubuntu1) quantal-proposed; urgency=low * Resynchronize with stable/folsom (1e774867) (LP: #1085255): - [aeabb42] There are routing problems when the dnsmasq port does not come first in

[Bug 1067669] Re: Mapping same bridge to different phyiscal networks succeed

2013-01-29 Thread Launchpad Bug Tracker
This bug was fixed in the package quantum - 2012.2.1-0ubuntu1 --- quantum (2012.2.1-0ubuntu1) quantal-proposed; urgency=low * Resynchronize with stable/folsom (1e774867) (LP: #1085255): - [aeabb42] There are routing problems when the dnsmasq port does not come first in

[Bug 1067669] Re: Mapping same bridge to different phyiscal networks succeed

2013-01-22 Thread Mark McLoughlin
** Tags removed: in-stable-folsom -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1067669 Title: Mapping same bridge to different phyiscal networks succeed To manage notifications about this bug go

[Bug 1067669] Re: Mapping same bridge to different phyiscal networks succeed

2013-01-11 Thread Launchpad Bug Tracker
** Branch linked: lp:ubuntu/quantal-proposed/quantum -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1067669 Title: Mapping same bridge to different phyiscal networks succeed To manage notifications

[Bug 1067669] Re: Mapping same bridge to different phyiscal networks succeed

2012-12-28 Thread Clint Byrum
Hello Alex, or anyone else affected, Accepted quantum into quantal-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/quantum/2012.2.1-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Bug 1067669] Re: Mapping same bridge to different phyiscal networks succeed

2012-12-03 Thread Adam Gandelman
** Changed in: quantum (Ubuntu) Status: New = Fix Released ** Also affects: quantum (Ubuntu Quantal) Importance: Undecided Status: New ** Changed in: quantum (Ubuntu Quantal) Status: New = Confirmed -- You received this bug notification because you are a member of

[Bug 1067669] Re: Mapping same bridge to different phyiscal networks succeed

2012-12-03 Thread Adam Gandelman
** Changed in: quantum (Ubuntu) Status: New = Fix Released ** Also affects: quantum (Ubuntu Quantal) Importance: Undecided Status: New ** Changed in: quantum (Ubuntu Quantal) Status: New = Confirmed -- You received this bug notification because you are a member of