<div dir="ltr"><div><div><div><div>Folks,<br><br></div>Majority of the commits for Numa and CPU pinning feature are merged in time [0].<br><br></div>One commit for validation is still to be merged [1]. So we would need 2 more days to complete the feature.<br><br></div>Regards,<br></div>Dmitry.<br><br>[0] <a href="https://review.openstack.org/#/q/status:merged+AND+topic:bp/support-numa-cpu-pinning">https://review.openstack.org/#/q/status:merged+AND+topic:bp/support-numa-cpu-pinning</a><br>[1] <a href="https://review.openstack.org/#/c/285282/">https://review.openstack.org/#/c/285282/</a></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Mar 4, 2016 at 1:59 AM, Dmitry Borodaenko <span dir="ltr"><<a href="mailto:dborodaenko@mirantis.com" target="_blank">dborodaenko@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Granted, merge deadline March 16, feature to be marked experimental<br>
until QA has signed off that it's fully tested and stable.<br>
<br>
--<br>
Dmitry Borodaenko<br>
<div><div class="h5"><br>
<br>
On Tue, Mar 01, 2016 at 10:23:08PM +0300, Dmitry Klenov wrote:<br>
> Hi,<br>
><br>
> I'd like to to request a feature freeze exception for "Add support for<br>
> NUMA/CPU pinning features" feature [0].<br>
><br>
> Part of this feature is already merged [1]. We have the following patches<br>
> in work / on review:<br>
><br>
> <a href="https://review.openstack.org/#/c/281802/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/281802/</a><br>
> <a href="https://review.openstack.org/#/c/285282/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/285282/</a><br>
> <a href="https://review.openstack.org/#/c/284171/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/284171/</a><br>
> <a href="https://review.openstack.org/#/c/280624/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/280624/</a><br>
> <a href="https://review.openstack.org/#/c/280115/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/280115/</a><br>
> <a href="https://review.openstack.org/#/c/285309/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/285309/</a><br>
><br>
> No new patches are expected.<br>
><br>
> We need 2 weeks after FF to finish this feature.<br>
> Risk of not delivering it after 2 weeks is low.<br>
><br>
> Regards,<br>
> Dmitry<br>
><br>
> [0] <a href="https://blueprints.launchpad.net/fuel/+spec/support-numa-cpu-pinning" rel="noreferrer" target="_blank">https://blueprints.launchpad.net/fuel/+spec/support-numa-cpu-pinning</a><br>
> [1]<br>
> <a href="https://review.openstack.org/#/q/status:merged+topic:bp/support-numa-cpu-pinning" rel="noreferrer" target="_blank">https://review.openstack.org/#/q/status:merged+topic:bp/support-numa-cpu-pinning</a><br>
<br>
</div></div>> __________________________________________________________________________<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>
</blockquote></div><br></div>