<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 13 July 2016 at 16:51, Kevin Benton <span dir="ltr"><<a href="mailto:kevin@benton.pub" target="_blank">kevin@benton.pub</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Sub ports are just regular ports from a logical model perspective, right? If so, there should be no problem attaching the port to a shared network or RBAC granted network.</p></blockquote><div><br></div><div>True, but I don't believe it until I test it :)</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr"> </p><div><div>
<div class="gmail_quote">On Jul 13, 2016 7:15 PM, "Armando M." <<a href="mailto:armamig@gmail.com" target="_blank">armamig@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 13 July 2016 at 15:32, Cathy Zhang <span dir="ltr"><<a href="mailto:Cathy.H.Zhang@huawei.com" target="_blank">Cathy.H.Zhang@huawei.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Everyone,<br>
<br>
We have been discussing on multi-tenant VNF for service chain on the OVN mailing alias.<br>
We are thinking about leveraging the vlan-aware-VM for supporting this.<br>
<br>
AFAIK, with current nova, we cannot create a multi-tenant VNF.<br>
Currently, nova checks whether the neutron port belongs to the same tenant as the VM itself.<br>
You attach a network interface (neutron port) to a VM using nova interface-attach, if the port and the VM are in different tenants, an error is given.<br>
<br>
With the introduction of the trunk-port/sub-port feature of Neutron, the sub-ports of a VM are allowed to associate with different networks. But it seems these networks need to all belong to the same tenant if we read the vlan-aware-vm spec correctly (<a href="http://specs.openstack.org/openstack/neutron-specs/specs/newton/vlan-aware-vms.html" rel="noreferrer" target="_blank">http://specs.openstack.org/openstack/neutron-specs/specs/newton/vlan-aware-vms.html</a>).<br>
<br>
Is our understanding correct? Does it work properly if these networks belong to different tenants?<br></blockquote><div><br></div><div>At the moment this area is still WIP, but we're focusing on the single tenant use case. RBAC may help us down the road to address what you need, but it's premature to speculate on how the implementation looks like.</div><div><br></div><div>Cheers,</div><div>Armando</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Thanks,<br>
Cathy<br>
<br>
-----Original Message-----<br>
From: dev [mailto:<a href="mailto:dev-bounces@openvswitch.org" target="_blank">dev-bounces@openvswitch.org</a>] On Behalf Of Farhad Sunavala<br>
Sent: Tuesday, July 12, 2016 7:59 PM<br>
To: <a href="mailto:dev@openvswitch.org" target="_blank">dev@openvswitch.org</a><br>
Subject: Re: [ovs-dev] SFC-Summary: MultiTenant<br>
<br>
>I was thinking this could be handled with child / sub-ports. We do<br>
>this today for containers in VMs. We can have a single VIF for a VM<br>
>that is connected to multiple networks that are owned by separate<br>
>tenants. Some sort of encapsulation (VLAN ID, MPLS header, whatever)<br>
>would be used to differentiate the traffic for each networking in/out<br>
>of that VIF. I had started adding the ability to use MPLS for this in<br>
>my prototype for this reason, as that was what networking-sfc had defined.<br>
I have a quick question on the above. (multi-tenancy).Yes, I know the containers can be in different networks of the same tenant.How does it work when the containers are in different tenants ?<br>
Below is the latest spec for vlan-aware-vms <a href="https://specs.openstack.org/openstack/neutron-specs/specs/liberty/vlan-aware-vms.html" rel="noreferrer" target="_blank">https://specs.openstack.org/openstack/neutron-specs/specs/liberty/vlan-aware-vms.html</a><br>
<br>
The trick is to create neutron ports (for the subports) and then link them to the trunk port using neutron trunk-subport-add TRUNK \ PORT[,SEGMENTATION-TYPE,SEGMENTATION-ID] \ [PORT,...]<br>
<br>
In the above command all the neutron ports (trunk ports and subports) must be in the same tenant.As far as I know, a tenant will not see neutron ports from another tenant. Or will this command allow neutron ports from different tenants to be attached ?<br>
E.g. VM "X" consists of containers C1 in Tenant 1 with portID = C10000 (network dn1)container C2 in Tenant 2 with portID = C20000 (network dn2)The trunk port of VM "X" is in tenant 100 with portID = T10000 (network dt) The above command will be neutron trunk-subport-add T10000 \ A vlan 10000 \ B vlan 20000 Is my understanding correct? thanks,Farhad.<br>
_______________________________________________<br>
dev mailing list<br>
<a href="mailto:dev@openvswitch.org" target="_blank">dev@openvswitch.org</a><br>
<a href="http://openvswitch.org/mailman/listinfo/dev" rel="noreferrer" target="_blank">http://openvswitch.org/mailman/listinfo/dev</a><br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div><br></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" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></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" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div>