:* Re: [openstack-dev] [Neutron] VLAN trunking network for NFV
That spec ensures that you can tell what the plugin is doing. You can ask
for a VLAN transparent network, but the cloud may tell you it can't make
one.
The OVS driver in Openstack drops VLAN tagged packets, I'm afraid
Development Mailing List (not for usage questions)
*Subject:* Re: [openstack-dev] [Neutron] VLAN trunking network for NFV
That spec ensures that you can tell what the plugin is doing. You can ask
for a VLAN transparent network, but the cloud may tell you it can't make
one.
The OVS driver
- Original Message -
*From:* Ian Wells [mailto: ijw.ubuntu at cack.org.uk ] *Sent:* Wednesday,
March 25, 2015 2:18 AM That spec ensures that you can tell what the
plugin is doing. You can ask for a VLAN transparent network, but the
cloud may tell you it can't make one. If
On 24 March 2015 at 11:45, Armando M. arma...@gmail.com wrote:
This may be besides the point, but I really clash with the idea that we
provide a reference implementation on something we don't have CI for...
Aside from the unit testing, it is going to get a test for the case we can
test - when
Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron] VLAN trunking network for NFV
That spec ensures that you can tell what the plugin is doing. You can ask for
a VLAN transparent network, but the cloud may tell you it can't make one.
The OVS driver in Openstack drops VLAN
From spec [1], I read:
- Of the core drivers, the VLAN and OVS drivers will be marked as not
supporting VLAN transparent networks and the LB, VXLAN and GRE drivers will
be marked as supporting VLAN transparent networks. Other drivers will have
legacy behaviour.
I can't seem to find
That spec ensures that you can tell what the plugin is doing. You can ask
for a VLAN transparent network, but the cloud may tell you it can't make
one.
The OVS driver in Openstack drops VLAN tagged packets, I'm afraid, and the
spec you're referring to doesn't change that. The spec does ensure