Adam,
depending on your current setup and what you are trying to do, there are
different possibilities.
The easiest would be if you want transparent VLANs, meaning that neither
Neutron nor your VM guests know about VLANs. Then you would have one bridge
(earlier: br-join) where all the
Am 27.04.2015 um 16:36 schrieb Mike Spreitzer:
Uwe Sauter uwe.sauter...@gmail.com wrote on 04/25/2015 04:17:35 PM:
Or instead of using Linux bridges you could use a manually created
OpenVSwitch bridge. This allows you to add internal
ports that could be used by Neutron like any other
Uwe Sauter uwe.sauter...@gmail.com wrote on 04/25/2015 04:17:35 PM:
Or instead of using Linux bridges you could use a manually created
OpenVSwitch bridge. This allows you to add internal
ports that could be used by Neutron like any other interface.
- Create OVS bridge
- Add your external
Uwe Sauter uwe.sauter...@gmail.com wrote on 04/27/2015 10:54:15 AM:
Am 27.04.2015 um 16:36 schrieb Mike Spreitzer:
Uwe Sauter uwe.sauter...@gmail.com wrote on 04/25/2015 04:17:35 PM:
Or instead of using Linux bridges you could use a manually created
OpenVSwitch bridge. This allows you
So quickly since I'm working on a similar use case:
What are the requirements to implement multiple external networks on the
same NIC if we *can* use VLAN tags? Is it as simple as adding the external
network to Neutron the same way we did with the existing external network
and trunk that subnet
Uwe Sauter uwe.sauter...@gmail.com wrote on 04/27/2015 01:22:35 PM:
if I understood Georges answer correctly he suggested one bridge
(br-join, either OVS or linux bridge) to connect other bridges
via patch links, one for each external network you'd like to create.
These second level
On 2015-04-27 22:59, Mike Spreitzer wrote:
Uwe Sauter uwe.sauter...@gmail.com wrote on 04/27/2015 10:54:15 AM:
What I suggested later on is that you probably don't need any second
level bridge at all. Just create a second/third external
network with appropriate CIDR. As long as those
gustavo panizzo (gfa) g...@zumbi.com.ar wrote on 04/27/2015 11:23:13
AM:
On 2015-04-27 22:59, Mike Spreitzer wrote:
Uwe Sauter uwe.sauter...@gmail.com wrote on 04/27/2015 10:54:15 AM:
What I suggested later on is that you probably don't need any second
level bridge at all. Just create a
Am 27.04.2015 um 17:23 schrieb gustavo panizzo (gfa):
you can only have one flat network per bridge.
I didn't know that.
Well, than the only idea that comes to *my* mind is to have cascading bridges
like George suggested. It won't matter if
you use Linux bridges or OVS. I heard that OVS
gustavo panizzo (gfa) g...@zumbi.com.ar wrote on 04/27/2015 11:23:13
AM:
On 2015-04-27 22:59, Mike Spreitzer wrote:
Uwe Sauter uwe.sauter...@gmail.com wrote on 04/27/2015 10:54:15
AM:
What I suggested later on is that you probably don't need any
second
level bridge at all. Just
Uwe Sauter uwe.sauter...@gmail.com wrote on 04/27/2015 10:54:15 AM:
Am 27.04.2015 um 16:36 schrieb Mike Spreitzer:
Uwe Sauter uwe.sauter...@gmail.com wrote on 04/25/2015 04:17:35 PM:
Or instead of using Linux bridges you could use a manually created
OpenVSwitch bridge. This allows you
if I understood Georges answer correctly he suggested one bridge
(br-join, either OVS or linux bridge) to connect other bridges
via patch links, one for each external network you'd like to create.
These second level bridges are then used for the Neutron
configuration:
Is there a way to create multiple external networks from Neutron's point
of view, where both of those networks are accessed through the same host
NIC? Obviously those networks would be using different subnets. I need
this sort of thing because the two subnets are treated differently by the
Uwe Sauter uwe.sauter...@gmail.com wrote on 04/25/2015 04:42:06 PM:
Am 25.04.2015 um 22:28 schrieb Mike Spreitzer:
From: Uwe Sauter uwe.sauter...@gmail.com
Or instead of using Linux bridges you could use a manually created
OpenVSwitch bridge. This allows you to add internal
ports that
Bridge mappings is an agent configuration value, it's not in the neutron
server config.
Run ps -ef and look for the neutron openvswitch agent process to see which
configuration files it's referencing. The bridge mappings will be in one of
those.
On Apr 25, 2015 1:55 PM, Mike Spreitzer
Can you put them to different vlans? After that it would be very easy task.
If not, AFAIK, neutron does not allow this.
Or you can trick it thinking it is (are) separate networks.
Create brige (br-join), plug eth to it.
Create to fake external bridges (br-ex1, br-ex2). Join them together to
Kevin Benton blak...@gmail.com wrote on 04/25/2015 08:38:25 PM:
Bridge mappings is an agent configuration value, it's not in the
neutron server config.
Run ps -ef and look for the neutron openvswitch agent process to see
which configuration files it's referencing. The bridge mappings will
17 matches
Mail list logo
