If all of the VLANs are tagged, then I am having a hard time imagining
why you want to use only one of them as a flat network.
The only difference between a VLAN network and a flat network in Neutron
is that OVS handles tagging/untagging on VLAN networks and flat networks
are untagged.
It is poss
One small change for us recently is that we removed the vlan-splinters piece on
eth0 and eth2 during the creation of the bond.
Other than that – I am not really sure what to tell you. We use to do things
using linux bonding with bond., however when we went to production no
traffic actually flo
Thx Kris.
If I map flat with br-flat and I add bond.567 interface to br-flat, it does
not work ?
Regards
Ignazio
Il 19/Apr/2017 21:20, "Kris G. Lindgren" ha scritto:
We handle this a different way, I want to look to see if we can redo it, so
it requires less pre-configuration on the host. Howe
Many Thanks, Dan
Ignazio
Il 19/Apr/2017 21:20, "Kris G. Lindgren" ha scritto:
> We handle this a different way, I want to look to see if we can redo it,
> so it requires less pre-configuration on the host. However, this is what
> we currently do (and have been doing for ~4 years):
> http://www.
We handle this a different way, I want to look to see if we can redo it, so it
requires less pre-configuration on the host. However, this is what we
currently do (and have been doing for ~4 years):
http://www.dorm.org/blog/wp-content/uploads/2015/10/ovs-wiring-676x390.png
From there inside neut
Hi Dan, on the physical switch the 567 is not the native vlan but is
tagged like 555 and 556.
I know I could set 567 as a native vlan to receive it untagged.
But if I would like more than one flat network ?
I am not skilled in networking but I think only one native vlan can be set
in switch.
Any f
On 04/19/2017 09:02 AM, Ignazio Cassano wrote:
> Dear All, in my openstack Newton installation compute e controllers
> node have e separate management network nic and a lacp bond0 where
> provider vlan (555,556) and flat vlan (567) are trunked.
> Since I cannot specify the vlan id (567) when I cr
Dear All, in my openstack Newton installation compute e controllers node
have e separate management network nic and a lacp bond0 where provider vlan
(555,556) and flat vlan (567) are trunked.
Since I cannot specify the vlan id (567) when I create a flat network, I
need to know how I can create the
Hi,
I've been looking around various docs and wiki pages and code repos, and
I'm finding it hard to pin down the current possibilities for two related
things
1. Heat stacks that maintain a minimum number of instances [ if an
instance crashes, goes into an error state, or the kvm process d