Hi Jimmy, I am working on a fix for this problem. I'll send out a patch for code-review next week.
Best regards, Anil -----Original Message----- From: SUZUKI, Kazuhiro [mailto:[email protected]] Sent: Tuesday, July 05, 2016 5:26 AM To: [email protected] Cc: [email protected] Subject: Re: [openstack-dev] [neutron][taas] Taas can not capture the packet, if the two VM on the same host. Is it a Bug? Hi Jimmy, I guess that it has not been resoved yet. You should try to ask it on IRC meeting, I think. http://eavesdrop.openstack.org/#Tap_as_a_Service_Meeting Regards, Kaz From: 张广明 <[email protected]> Subject: Re: [openstack-dev] [neutron][taas] Taas can not capture the packet, if the two VM on the same host. Is it a Bug? Date: Tue, 5 Jul 2016 19:31:14 +0800 > Hi Kaz > Thanks for your answer. But int the log, i can not find how to > resolve this issue. In fact ,this issue is not related with br-ex. > In OVS, the normal action add or remove vlan id when output the pac > ket. So we should add another rule that use in_port that belongs to > the same vlan with mirror port as rule condition in br- int. > > > > Jimmy > > 2016-07-05 17:01 GMT+08:00 SUZUKI, Kazuhiro <[email protected]>: > >> Hi, >> >> I also have seen the same situation. >> The same issue is discussed at the IRC meeting of TaaS. >> Please take a look at the log. >> >> >> http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-04-13- >> 06.30.log.html >> >> Regards, >> Kaz >> >> >> From: 张广明 <[email protected]> >> Subject: [openstack-dev] [neutron][taas] Taas can not capture the >> packet, if the two VM on the same host. Is it a Bug? >> Date: Fri, 1 Jul 2016 16:03:53 +0800 >> >> > Hi , >> > I found a limitation when use taas. My test case is descrip >> ped as >> > follow: >> > VM1 and VM2 is running on the same host and they are belong >> the >> vlan. >> > The monitor VM is on the same host or the other host . I want t >> o monitor >> > the only INPUT flow to the VM1. >> > So I configure the tap-flow like this "neutron tap-flow-crea >> te >> --port >> > 2a5a4382-a600-4fb1-8955-00d0fc9f648f --tap-service >> > c510e5db-4ba8-48e3-bfc8-1f0b61f8f41b --direction IN ". >> > When ping from VM2 to VM1. I can not get the flow in the mo >> nitor VM. >> > The reason is the the flow from VM2 to VM1 in br-int has not >> vlan >> > information. The vlan tag was added in flow when output the pack >> et in >> OVS. >> > So the code in file ovs_taas.py did not work in this case . >> > >> > if direction == 'IN' or direction == 'BOTH': >> > port_mac = tap_flow['port_mac'] >> > self.int_br.add_flow(table=0, >> > priority=20, >> > dl_vlan=port_vlan_id, >> > dl_dst=port_mac, >> > >> actions="normal,mod_vlan_vid:%s,output:%s" % >> > (str(taas_id), str(patch_int_ta >> p_id))) >> > >> > >> > >> > >> > Is this is a Bug or a Design ?? >> > >> > >> > >> > Thanks. >> __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
