<div dir="ltr"><div>Speaking as someone who was reviewing both specs, I would personally recommend you grant both exceptions. The code changes are very limited in scope - particularly the Nova one - which makes the code review simple, and they're highly unlikely to affect anyone who isn't actually using DPDK OVS (subject to the Neutron tests for its presence being solid), which makes them low risk. For even lower risk, we could have a config option to enable the test for a CUSE-based binding (and yes, I know earlier in the review everyone was against config items, but specifically what we didn't want was *two* config items, one in Nova nd one in Neutron, that only worked if they were in agreement; one solely in Neutron would, I think, be acceptable).<br>
<br>All this subject to Sean getting all the CRs out of his spec, and maybe we could add a spec test for that, because it's a right pain to have specs full of CRs if you're trying to diff them online...<br>-- <br>
</div>Ian.<br><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 23 July 2014 11:10, Mooney, Sean K <span dir="ltr"><<a href="mailto:sean.k.mooney@intel.com" target="_blank">sean.k.mooney@intel.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi kyle<br>
<br>
Thanks for your provisional support.<br>
I would agree that unless the nova spec is also granted an exception both specs should be moved<br>
To Kilo.<br>
<br>
I have now uploaded the most recent version of the specs.<br>
They are available to review here:<br>
<a href="https://blueprints.launchpad.net/nova/+spec/libvirt-ovs-use-usvhost" target="_blank">https://blueprints.launchpad.net/nova/+spec/libvirt-ovs-use-usvhost</a><br>
<a href="https://blueprints.launchpad.net/neutron/+spec/ml2-use-dpdkvhost" target="_blank">https://blueprints.launchpad.net/neutron/+spec/ml2-use-dpdkvhost</a><br>
<br>
regards<br>
<span class="HOEnZb"><font color="#888888">sean<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
-----Original Message-----<br>
From: Kyle Mestery [mailto:<a href="mailto:mestery@mestery.com">mestery@mestery.com</a>]<br>
Sent: Tuesday, July 22, 2014 2:47 PM<br>
To: OpenStack Development Mailing List (not for usage questions)<br>
Subject: Re: [openstack-dev] [Neutron] [Spec freeze exception] ml2-use-dpdkvhost<br>
<br>
On Mon, Jul 21, 2014 at 10:04 AM, Mooney, Sean K <<a href="mailto:sean.k.mooney@intel.com">sean.k.mooney@intel.com</a>> wrote:<br>
> Hi<br>
><br>
> I would like to propose<br>
> <a href="https://review.openstack.org/#/c/107797/1/specs/juno/ml2-use-dpdkvhost" target="_blank">https://review.openstack.org/#/c/107797/1/specs/juno/ml2-use-dpdkvhost</a><br>
> .rst<br>
> for a spec freeze exception.<br>
><br>
><br>
><br>
> <a href="https://blueprints.launchpad.net/neutron/+spec/ml2-use-dpdkvhost" target="_blank">https://blueprints.launchpad.net/neutron/+spec/ml2-use-dpdkvhost</a><br>
><br>
><br>
><br>
> This blueprint adds support for the Intel(R) DPDK Userspace vHost<br>
><br>
> port binding to the Open Vswitch and Open Daylight ML2 Mechanism Drivers.<br>
><br>
In general, I'd be ok with approving an exception for this BP.<br>
However, please see below.<br>
<br>
><br>
><br>
> This blueprint enables nova changes tracked by the following spec:<br>
><br>
> <a href="https://review.openstack.org/#/c/95805/1/specs/juno/libvirt-ovs-use-us" target="_blank">https://review.openstack.org/#/c/95805/1/specs/juno/libvirt-ovs-use-us</a><br>
> vhost.rst<br>
><br>
This BP appears to also require an exception from the Nova team. I think these both require exceptions for this work to have a shot at landing in Juno. Given this, I'm actually leaning to move this to Kilo. But if you can get a Nova freeze exception, I'd consider the same for the Neutron BP.<br>
<br>
Thanks,<br>
Kyle<br>
<br>
><br>
><br>
> regards<br>
><br>
> sean<br>
><br>
> --------------------------------------------------------------<br>
> Intel Shannon Limited<br>
> Registered in Ireland<br>
> Registered Office: Collinstown Industrial Park, Leixlip, County<br>
> Kildare Registered Number: 308263 Business address: Dromore House,<br>
> East Park, Shannon, Co. Clare<br>
><br>
> This e-mail and any attachments may contain confidential material for<br>
> the sole use of the intended recipient(s). Any review or distribution<br>
> by others is strictly prohibited. If you are not the intended<br>
> recipient, please contact the sender and delete all copies.<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>
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>
Intel Shannon Limited<br>
Registered in Ireland<br>
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare<br>
Registered Number: 308263<br>
Business address: Dromore House, East Park, Shannon, Co. Clare<br>
<br>
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.<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>