>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 in the code where this is implemented though. Can you
elaborate?

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...for
that reason, I am starting to become really wary of the shape this has been
merged in. Let's hope we tie the appropriate loose ends in the next couple
of days, otherwise we're left with no other option than pulling this out of
Kilo.

A

[1]
http://specs.openstack.org/openstack/neutron-specs/specs/kilo/nfv-vlan-trunks.html





On 24 March 2015 at 11:17, Ian Wells <ijw.ubu...@cack.org.uk> wrote:

> 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 that if
> you try and create a VLAN trunk on a cloud that uses the OVS driver, you'll
> be told you can't.  in the future, the OVS driver can be fixed, but that's
> how things stand at present.  Fixing the OVS driver really involves getting
> in at the OVS flow level - can be done, but we started with the basics.
>
> If you want to use a VLAN trunk using the current code, I recommend VXLAN
> or GRE along with the Linuxbridge driver, both of which support VLAN
> transparent networking.  If they're configured and you ask for a VLAN trunk
> you'll be told you got one.
> --
> Ian.
>
>
> On 24 March 2015 at 09:43, Daniele Casini <daniele.cas...@dektech.com.au>
> wrote:
>
>> Hi all:
>>
>> in reference to the following specification about the creation of VLAN
>> trunking network for NFV
>>
>> https://review.openstack.org/#/c/136554/3/specs/kilo/nfv-vlan-trunks.rst
>>
>> I would like to better understand how the tagged traffic will be
>> realized. In order to explain myself, I report the following use case:
>>
>> A VNF is deployed in one VM, which has a trunk port carrying traffic for
>> two VLANs over a single link able to transport more than one VLAN through a
>> single integration-bridge (br-int) port. So, How does br-int manage the
>> VLAN-ID? In other words, what are the action performed by the br-int when a
>> VM forwards traffic to another host?
>> Does it put an additional tag or replace the existing one keeping the
>> match with a table or something like that?
>>
>> Thank you very much.
>>
>> Daniele
>>
>>
>> ____________________________________________________________
>> ______________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
>> unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to