<div dir="ltr">Hi Yamamoto,<div><br></div><div>Thanks for resuming work on this effort. TAP-as-a-service is a very important feature, and great to see we are considering use case scenarios and adjusting APIs accordingly. I have some thoughts on the use case scenarios, which are seen as most common ones, when talking to operators.</div><div><br></div><div>There are two types of tap filters, which serve some of the use cases:</div><div><br></div><div>   * Port based packet mirroring/redirection</div><div>   * Policy based packet mirroring/redirection</div><div><br></div><div>I see both of them as important from operator use case scenarios. Also, I mentioned traffic redirection in addition to the traffic mirroring and that serves use cases where services like IPS are deployed and incorporated. </div><div><br></div><div>Do you happen to have a blueprint proposed with the original API demonstrated that we can iterate over and add the use cases and adjust the API accordingly to take further for review?</div><div><br></div><div>Thanks,</div><div class="gmail_extra"><div><div><div dir="ltr">Fawad Khaliq<div><br></div></div></div></div>
<br><div class="gmail_quote">On Wed, Nov 18, 2015 at 1:57 PM, Irena Berezovsky <span dir="ltr"><<a href="mailto:irenab.dev@gmail.com" target="_blank">irenab.dev@gmail.com</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"><br><div class="gmail_extra"><br><div class="gmail_quote"><span>On Wed, Nov 18, 2015 at 8:31 AM, Takashi Yamamoto <span dir="ltr"><<a href="mailto:yamamoto@midokura.com" target="_blank">yamamoto@midokura.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">hi,<br>
<span><br>
On Thu, Nov 12, 2015 at 2:11 AM, Vikram Hosakote (vhosakot)<br>
<<a href="mailto:vhosakot@cisco.com" target="_blank">vhosakot@cisco.com</a>> wrote:<br>
> Hi,<br>
><br>
> TAAS looks great for traffic monitoring.<br>
><br>
> Some questions about TAAS.<br>
><br>
> 1) Can TAAS be used for provider networks as well, or just for tenant<br>
> networks ?<br>
<br>
</span>currently only for VM ports on tenant networks.<br>
<span><br>
><br>
> 2) Will there be any performance impact is every neutron port and every<br>
> packet is mirrored/duplicated ?<br>
<br>
</span>i guess per-port impact is negligible.<br>
there's definitely per-packet impacts.<br>
i don't have any numbers though.<br>
<span><br>
><br>
> 3) How is TAAS better than a non-mirroring approaches like packet-sniffing<br>
> (wireshark/tcpdump) and tracking interface counters/metrics ?<br>
<br>
</span>i think taas is richer but probably slower than them.<br>
<span><br>
><br>
> 4) Is TAAS a legal/lawful way to intercept/duplicate customer traffic in a<br>
> production cloud ? Or, TAAS is used just for debugging/troubleshooting ?<br>
<br>
</span>although i'm not sure about legal/lawful requirements,<br>
i guess taas can be used for such purposes.<br></blockquote><div><br></div></span><div>You check this presentation for potential usage scenarios:</div><div><br></div><div> <a href="https://www.openstack.org/summit/vancouver-2015/summit-videos/presentation/tap-as-a-service-taas-port-monitoring-for-neutron-networks" target="_blank">https://www.openstack.org/summit/vancouver-2015/summit-videos/presentation/tap-as-a-service-taas-port-monitoring-for-neutron-networks</a></div><div><div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><div>
><br>
> I was not able to find answers for these questions in<br>
> <a href="https://etherpad.openstack.org/p/mitaka-neutron-unplugged-track" rel="noreferrer" target="_blank">https://etherpad.openstack.org/p/mitaka-neutron-unplugged-track</a>.<br>
><br>
> Thanks!<br>
><br>
><br>
> Regards,<br>
> Vikram Hosakote<br>
> <a href="mailto:vhosakot@cisco.com" target="_blank">vhosakot@cisco.com</a><br>
> Software Engineer<br>
> Cloud and Virtualization Group (CVG)<br>
> Cisco Systems<br>
> Boxborough MA USA<br>
><br>
> From: Takashi Yamamoto <<a href="mailto:yamamoto@midokura.com" target="_blank">yamamoto@midokura.com</a>><br>
> Reply-To: "OpenStack Development Mailing List (not for usage questions)"<br>
> <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
> Date: Tuesday, November 10, 2015 at 10:08 PM<br>
> To: "OpenStack Development Mailing List (not for usage questions)"<br>
> <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
> Subject: [openstack-dev] [neutron][tap-as-a-service] weekly meeting<br>
><br>
> hi,<br>
><br>
> tap-as-a-service meeting will be held weekly, starting today.<br>
> <a href="http://eavesdrop.openstack.org/#Tap_as_a_Service_Meeting" rel="noreferrer" target="_blank">http://eavesdrop.openstack.org/#Tap_as_a_Service_Meeting</a><br>
> anyone interested in the project is welcome.<br>
> sorry for immediate notice.<br>
><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>
><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>
<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>
</div></div></blockquote></div></div></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><br></div></div>