<div dir="ltr">From spec [1], I read:<div><br></div><div><ul class="" style="color:rgb(62,67,73);font-family:Arial,sans-serif;font-size:14.3999996185303px"><li style="line-height:1.5em">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.</li></ul><div>I can't seem to find in the code where this is implemented though. Can you elaborate?</div><div><br></div><div>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.<br></div><div><br></div><div>A</div><div><br></div><div>[1] <a href="http://specs.openstack.org/openstack/neutron-specs/specs/kilo/nfv-vlan-trunks.html">http://specs.openstack.org/openstack/neutron-specs/specs/kilo/nfv-vlan-trunks.html</a></div><div><br></div><div><br><div><br></div><div><br></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 24 March 2015 at 11:17, Ian Wells <span dir="ltr"><<a href="mailto:ijw.ubuntu@cack.org.uk" target="_blank">ijw.ubuntu@cack.org.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>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.<br><br>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.<br><br></div><div>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.<span class="HOEnZb"><font color="#888888"><br>-- <br></font></span></div><span class="HOEnZb"><font color="#888888"><div>Ian.<br></div></font></span><div><div class="h5"><br><div class="gmail_extra"><br><div class="gmail_quote">On 24 March 2015 at 09:43, Daniele Casini <span dir="ltr"><<a href="mailto:daniele.casini@dektech.com.au" target="_blank">daniele.casini@dektech.com.au</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi all:<br>
<br>
in reference to the following specification about the creation of VLAN trunking network for NFV<br>
<br>
<a href="https://review.openstack.org/#/c/136554/3/specs/kilo/nfv-vlan-trunks.rst" target="_blank">https://review.openstack.org/#<u></u>/c/136554/3/specs/kilo/nfv-<u></u>vlan-trunks.rst</a><br>
<br>
I would like to better understand how the tagged traffic will be realized. In order to explain myself, I report the following use case:<br>
<br>
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?<br>
Does it put an additional tag or replace the existing one keeping the match with a table or something like that?<br>
<br>
Thank you very much.<br>
<br>
Daniele<br>
<br>
<br>
______________________________<u></u>______________________________<u></u>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.<u></u>openstack.org?subject:<u></u>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
</blockquote></div><br></div></div></div></div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>