<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; "><div>Rossella,</div><div><br></div><div>Looking forward to getting more details!</div><div><br></div><div>Edgar</div><div><br></div><span id="OLK_SRC_BODY_SECTION"><div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span style="font-weight:bold">From: </span> Rossella Sblendido <<a href="mailto:rossella@midokura.com">rossella@midokura.com</a>><br><span style="font-weight:bold">Reply-To: </span> OpenStack List <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br><span style="font-weight:bold">Date: </span> Thursday, November 14, 2013 11:48 AM<br><span style="font-weight:bold">To: </span> OpenStack List <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br><span style="font-weight:bold">Subject: </span> Re: [openstack-dev] [Neutron] Port mirroring<br></div><div><br></div><div dir="ltr"><div><div><div><div><div>Hi Edgar,<br><br></div>documentation is a great idea. I will make sure to have it. Shall I add it to the blueprint or just have to keep that in mind?<br></div>Yes it will be configurable, if you look at the API I think it's quite flexible but if you or others have ideas on how to make it better, please add some comment.<br><br></div>Regarding the overhead, I could give only a vague answer now. Let me think more through it and I will come back to you. I think the best way is to provide more details about the implementation in the document so that everybody can have a better idea of the changes required and can give his/her feedback too. I will do that.<br><br></div>thanks a lot!<br><br></div>Rossella<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Nov 14, 2013 at 7:15 PM, Edgar Magana <span dir="ltr"><<a href="mailto:emagana@plumgrid.com" target="_blank">emagana@plumgrid.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello Rossella,<br><br>
Kyle has a very good point and I wanted to add the documentation request.<br>
Be sure you have a wiki/document (not a technical one) that we can easily<br>
transfer into the OpenStack Docs.<br><br>
This is a great feature, any idea of the overhead that it will cause?<br>
I assume that this is going to be totally configurable, right? :-)<br><span class="HOEnZb"><font color="#888888"><br>
Edgar<br></font></span><div class="HOEnZb"><div class="h5"><br>
On 11/14/13 8:34 AM, "Kyle Mestery (kmestery)" <<a href="mailto:kmestery@cisco.com">kmestery@cisco.com</a>> wrote:<br><br>
>On Nov 14, 2013, at 8:46 AM, Rossella Sblendido <<a href="mailto:rossella@midokura.com">rossella@midokura.com</a>><br>
>wrote:<br>
>><br>
>> Hello devs,<br>
>><br>
>> I'd like to start working at this blueprint:<br>
>><br>
>> <a href="https://blueprints.launchpad.net/neutron/+spec/port-mirroring" target="_blank">https://blueprints.launchpad.net/neutron/+spec/port-mirroring</a><br>
>><br>
>> I didn't receive much feedback so please have a look at it.<br>
>><br>
>> It was not approved yet. What's the usual workflow? Shall I wait for<br>
>>approval before I start implementing it? Sorry for the trivial question<br>
>>but I'm new here.<br>
>><br>
>Welcome Rossella!<br>
><br>
>One issue I have with the design document linked in the blueprint is the<br>
>testing section has nothing in it all. Given we're trying hard to focus<br>
>on quality and testing, I'd like you to add some specific testing<br>
>information to the document before we approve it. It would be ideal to<br>
>have Tempest tests which test out the new API functionality as well.<br>
>That's my main issue with this BP as seen now, but I'd like others to<br>
>comment on this as well.<br>
><br>
>Thanks!<br>
>Kyle<br>
><br>
>> thanks,<br>
>><br>
>> Rossella<br>
>><br>
>> _______________________________________________<br>
>> OpenStack-dev mailing list<br>
>> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</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>
><br>
><br>
>_______________________________________________<br>
>OpenStack-dev mailing list<br>
><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</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><br><br>
_______________________________________________<br>
OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</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></div></div></blockquote></div><br></div>
_______________________________________________
OpenStack-dev mailing list
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</span></body></html>