Rossella, Looking forward to getting more details!
Edgar From: Rossella Sblendido <rosse...@midokura.com> Reply-To: OpenStack List <openstack-dev@lists.openstack.org> Date: Thursday, November 14, 2013 11:48 AM To: OpenStack List <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [Neutron] Port mirroring Hi Edgar, 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? 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. 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. thanks a lot! Rossella On Thu, Nov 14, 2013 at 7:15 PM, Edgar Magana <emag...@plumgrid.com> wrote: > Hello Rossella, > > Kyle has a very good point and I wanted to add the documentation request. > Be sure you have a wiki/document (not a technical one) that we can easily > transfer into the OpenStack Docs. > > This is a great feature, any idea of the overhead that it will cause? > I assume that this is going to be totally configurable, right? :-) > > Edgar > > On 11/14/13 8:34 AM, "Kyle Mestery (kmestery)" <kmest...@cisco.com> wrote: > >> >On Nov 14, 2013, at 8:46 AM, Rossella Sblendido <rosse...@midokura.com> >> >wrote: >>> >> >>> >> Hello devs, >>> >> >>> >> I'd like to start working at this blueprint: >>> >> >>> >> https://blueprints.launchpad.net/neutron/+spec/port-mirroring >>> >> >>> >> I didn't receive much feedback so please have a look at it. >>> >> >>> >> It was not approved yet. What's the usual workflow? Shall I wait for >>> >>approval before I start implementing it? Sorry for the trivial question >>> >>but I'm new here. >>> >> >> >Welcome Rossella! >> > >> >One issue I have with the design document linked in the blueprint is the >> >testing section has nothing in it all. Given we're trying hard to focus >> >on quality and testing, I'd like you to add some specific testing >> >information to the document before we approve it. It would be ideal to >> >have Tempest tests which test out the new API functionality as well. >> >That's my main issue with this BP as seen now, but I'd like others to >> >comment on this as well. >> > >> >Thanks! >> >Kyle >> > >>> >> thanks, >>> >> >>> >> Rossella >>> >> >>> >> _______________________________________________ >>> >> OpenStack-dev mailing list >>> >> OpenStack-dev@lists.openstack.org >>> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > >> > >> > >> >_______________________________________________ >> >OpenStack-dev mailing list >> >OpenStack-dev@lists.openstack.org >> >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
