[openstack-dev] [neutron][tacker] Trunk ports in Tacker?

Armando M. armamig at gmail.com
Wed Nov 23 16:24:45 UTC 2016


On 23 November 2016 at 01:47, zhi <changzhi1990 at gmail.com> wrote:

> Hi, all
>
> Recently I did some research about trunk port in neutron by following
> document[1]. By creating a trunk port, I can use this port ( aka " parent
> port " ) to create a VM. So I can add or remove subports on this "parent
> port" which used by the VM I created.
>
> I want to know how Tacker can use " trunk port ". In Tacker, I can create
> a VNFD template which contains network infos like
> "
>     VL1:
>       type: tosca.nodes.nfv.VL
>       properties:
>         network_name: net_mgmt
>         vendor: Tacker
> "
> So I can use this template to create VNFs with specific network info(
> naming net_mgmt ). Finally VNFs own its normal ports in neutron. So my
> question is:
>
> Can I use trunk ports in Tacker?
>
> I read some document about VLAN transparent in Neutron. In my thought, I
> can create a vlan transparent network in Neutron and using this network in
> VNFD template. At last, every VNF's
> port is " trunk port " and I can add or remove subports on it. Am I right?
>
> In Newton, I enabled the vlan-transparent in neutron server and try to
> create a vlan transparent network. But I failed. I got the error message
> is: " Backend does not support VLAN Transparency ".
>
> VLAN transparent doesn't support in Newton now?
>

VLAN transparency is backend dependent. OVS, if that's the one you were
using, does not support it.


>
>
> Thanks
> Zhi Chang
>
> [1]: https://wiki.openstack.org/wiki/Neutron/TrunkPort
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20161123/9f6e777e/attachment.html>


More information about the OpenStack-dev mailing list