<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi,<br>
<br>
Thanks for your suggestion - I don't think that's it, because that
gives me:<br>
<br>
Unable to add br224 to brqf709c220-fd! Exception: Exit code: 1;
Stdin: ; Stdout: ; Stderr: device br224 is a bridge device itself;
can't enslave a bridge device to a bridge device.<br>
<br>
and<br>
<br>
Skip adding device tapf99013c6-6b to brqf709c220-fd. It is owned
by compute:nova and thus added elsewhere. _add_tap_interface
/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/drivers/linuxbridge/agent/linuxbridge_neutron_agent.py:473<br>
<br>
while this tapf99013c6-6b now actually is enslaved to
brqf709c220-fd, even with the wrong physical_interface_mappings
setting. So I guess it's ignored because of the error, or some
other code built that bridge (nova? as it's owned by compute:nova
? I had no idea a bridge/interface could have an owner...)<br>
<br>
Regards,<br>
Paul<br>
<br>
<br>
On 16-08-16 17:39, George Paraskevas wrote:<br>
</div>
<blockquote
cite="mid:CAMY8EK8dbGOJP1ek0tkTB-kQhaGj0EVgG-GJOuehZrGAGzX2Kw@mail.gmail.com"
type="cite">
<p dir="ltr">Hello,<br>
With Linux bridge, I believe you should use physical
_interface_mappings =provider:br224<br>
Beat regards<br>
George</p>
<br>
<div class="gmail_quote">
<div dir="ltr">On Tue, 16 Aug 2016, 16:48 Paul Dekkers, <<a
moz-do-not-send="true" href="mailto:paul.dekkers@surfnet.nl">paul.dekkers@surfnet.nl</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I'm using Ubuntu 16.04.1 with it's Mitaka release, and neutron
flat<br>
networking with linuxbridge+ml2:<br>
<br>
I'd like to attach my flat neutron network to an existing
linuxbridge on<br>
my system. This fails with an error like:<br>
<br>
2016-08-16 15:07:00.711 7982 DEBUG<br>
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent<br>
[req-720266dc-fe8d-47c4-a7df-19fee7a8d679 - - - - -] Skip
adding device<br>
tapf99013c6-6b to br224. It is owned by compute:nova and thus
added<br>
elsewhere. _add_tap_interface<br>
/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/drivers/linuxbridge/agent/linuxbridge_neutron_agent.py:473<br>
<br>
with the result that the tap interface is added to a newly
created<br>
bridge instead of the existing (br224) bridge.<br>
<br>
I've set<br>
bridge_mappings = provider:br224<br>
in /etc/neutron/plugins/ml2/linuxbridge_agent.ini<br>
<br>
(because if I use<br>
physical_interface_mappings = provider:vlan224<br>
the vlan224 interface is actually detached from the original
bridge)<br>
<br>
I've created the bridge via /etc/network/interfaces:<br>
<br>
auto br224<br>
iface br224 inet manual<br>
bridge_ports vlan224<br>
<br>
auto vlan224<br>
iface vlan224 inet manual<br>
vlan_raw_device eno1<br>
<br>
Reason for doing this is that I'd like to attach an lxc
container to<br>
this bridge (and only when neutron needs it the
"brqf709c220-fd" (with<br>
for me an unpredictable name) is setup, so I can't use that),
and/or<br>
like to have the machine itself use an interface on this
network. (This<br>
is also my reason for using flat networking, and not vlan.)<br>
<br>
I've created the neutron networks with<br>
<br>
neutron net-create default --shared
--provider:physical_network provider<br>
--provider:network_type flat<br>
<br>
(I would repeat this with a different physical_network name if
I need<br>
more VLANs, instead of using the --provider:segmentation_id.)<br>
<br>
Instance networking works when I let nova/neutron create the
bridge<br>
interfaces.<br>
<br>
Any idea why neutron refuses to use the bridge_mappings and
why it<br>
creates a new interface?<br>
<br>
Regards,<br>
Paul<br>
<br>
P.S. To me it feels like this is what people would need when
setting up<br>
a small single-network setup (both for instances and
OpenStack), but<br>
most examples use multiple networks anyway.<br>
<br>
_______________________________________________<br>
OpenStack-operators mailing list<br>
<a moz-do-not-send="true"
href="mailto:OpenStack-operators@lists.openstack.org"
target="_blank">OpenStack-operators@lists.openstack.org</a><br>
<a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators"
rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
</blockquote>
</div>
</blockquote>
<p><br>
</p>
</body>
</html>