<div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div>Just a tiny report to summarize the situation to offer a big picture and to analyze proposed solutions since peoples have submits new patches and some other people have shared their opinions.</div><div><br></div><div>Each solution contains the impacted projects, the related gerrit reviews, pro/cons.</div><div><br></div><div><div>### 1 - Backport master changer and also backport new feature into a stable branch<br></div><div>impacted projects: oslo.service, nova</div><div>related reviews:</div><div>- <a href="https://review.openstack.org/617989">https://review.openstack.org/617989</a></div><div>- <a href="https://review.openstack.org/619022">https://review.openstack.org/619022</a></div><div>- <a href="https://review.openstack.org/619019">https://review.openstack.org/619019</a><br></div><div><br></div><div>pros:</div><div>- follow the master changes<br></div><div>- just use a backport<br></div><div>cons:</div><div>- backport a new feature into a stable branch and then this a violation of the stable policy<br></div><div>- introduce a semver minor bump and a version 1.32 already exist</div><div>- won't be able to use either an older nova with a newer oslo.service</div><div>- increasing lower-constraints is not allowed on stable branches</div><div>- vendors need to ensure that there is a 'fixture' package available<br></div><div><br></div><div>### 2 - Update the nova test to mock the new private interface<br></div><div><div>impacted projects: nova</div><div>reviews:</div><div>- <a href="https://review.openstack.org/619246">https://review.openstack.org/619246</a><br></div><div><br></div><div>pros:</div><div>- straightforward<br></div><div>cons:</div><div>- still mocking a private inferface</div><div>- stable only patches<br></div><div><br></div></div><div>### 3 - Maintain a private interface for ThreadingEvent only on stable/rocky<br></div><div><div>impacted projects: oslo.service<br></div><div>related reviews:</div><div>- <a href="https://review.openstack.org/619342/">https://review.openstack.org/619342/</a></div><div><br></div><div>pros:</div><div>- straightforward<br></div><div>cons:</div><div>- Changing the loopingcall module semantics as it is different type<br></div><div>- stable only patches</div><div>- misunderstoud service customer between Threading, eventlet, etc.. and master behavior</div><div><br></div></div><div>### 4 - Don't use private interface in oslo.service<br></div><div><div>impacted projects: nova</div><div>related reviews:</div><div>- <a href="https://review.openstack.org/#/c/619360/">https://review.openstack.org/#/c/619360/</a></div><div><br></div><div>pros:</div><div>- straightforward<br></div><div>cons:</div><div>- this could work but it is not the same sematics as before as the type has changed</div><div>- stable only patches</div><div>- misunderstoud service customer between Threading, eventlet, etc.. and master behavior</div></div><div><br></div><div><div>### 5 - Leave the CPU bug open on rocky<br></div><div><div>impacted projects: oslo.service<br></div><div>related reviews: -<br></div><div><br></div><div>pros: <br></div><div>- Nova project doesn't impacted  </div><div>cons:</div><div>- reintroduce the CPU issue<br></div><div><br></div><div>### 6 - Revert CPU fix and totally rework it into someting that doesn't break the Nova CI</div><div><div><div>impacted projects: oslo.service<br></div><div>related reviews: -<br></div><div><br></div><div>pros: <br></div><div>- Nova project doesn't impacted <br></div><div>cons:</div><div><div>- potentially introduce more rewrites in the futures that depends on fix on oslo.service loopingcall master <br></div></div><div>- stable only patches<div>- increase potential backport difficulties on oslo.service upstream and downstream<br></div></div><div>- increase work load on upstream and downstream<br></div></div></div></div></div></div><div><br></div><div>Personally:</div><div>- I prefer the #4 or the #2 and they seem to be smooth changes without earthquake or anything like this<br></div><div>- the #6 seems to be the worst solution on my side</div><div>- the #1 introduce semver issue and policy violations so I don't think we can continue with it</div><div><br></div><div>Thoughts?</div><div><br></div><div>I hope this summarize help you to have a better overview :)</div><div><br></div><div><span id="gmail-result_box" class="gmail-" lang="en"><span class="gmail-">I hope I have not forgotten anything and if so I apologize in advance.</span></span></div></div></div></div></div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr">Le mer. 21 nov. 2018 à 15:47, Herve Beraud <<a href="mailto:hberaud@redhat.com">hberaud@redhat.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div id="m_-5471532235688025461gmail-magicdomid2" class="m_-5471532235688025461gmail-ace-line"><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z">Hey all!</span></div><div id="m_-5471532235688025461gmail-magicdomid3" class="m_-5471532235688025461gmail-ace-line"><br></div><div id="m_-5471532235688025461gmail-magicdomid4" class="m_-5471532235688025461gmail-ace-line"><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z">Here is a </span><span class="m_-5471532235688025461gmail-author-a-z69zz79z34z79zm1yz74zwz65zz80zyz69z72">thread</span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z"> to coordinate all the teams (oslo, nova, stable, requirements) </span><span class="m_-5471532235688025461gmail-author-a-z69zz79z34z79zm1yz74zwz65zz80zyz69z72">working on</span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z"> the update of </span><span class="m_-5471532235688025461gmail-author-a-z69zz79z34z79zm1yz74zwz65zz80zyz69z72">the </span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z">oslo.service constraint in the</span><span class="m_-5471532235688025461gmail-author-a-z69zz79z34z79zm1yz74zwz65zz80zyz69z72"> Rocky</span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z"> requirements.</span></div><div id="m_-5471532235688025461gmail-magicdomid5" class="m_-5471532235688025461gmail-ace-line"><br></div><div id="m_-5471532235688025461gmail-magicdomid6" class="m_-5471532235688025461gmail-ace-line"><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z"># Summary</span></div><div id="m_-5471532235688025461gmail-magicdomid7" class="m_-5471532235688025461gmail-ace-line"><br></div><div id="m_-5471532235688025461gmail-magicdomid8" class="m_-5471532235688025461gmail-ace-line"><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z">Usage of threading event with eventlet caused inefficient code (causing many useless system calls and  high CPU usage).</span></div><div id="m_-5471532235688025461gmail-magicdomid9" class="m_-5471532235688025461gmail-ace-line"><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z">This issue was already fixed on oslo.service master and we also want to fix it in stable/rocky.</span></div><div id="m_-5471532235688025461gmail-magicdomid10" class="m_-5471532235688025461gmail-ace-line"><br></div><div id="m_-5471532235688025461gmail-magicdomid11" class="m_-5471532235688025461gmail-ace-line"><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z">Our main issue is how to fix the high CPU usage on stable/rocky without break the nova CI.</span></div><div id="m_-5471532235688025461gmail-magicdomid12" class="m_-5471532235688025461gmail-ace-line"><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z"> </span></div><div id="m_-5471532235688025461gmail-magicdomid231" class="m_-5471532235688025461gmail-ace-line"><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z">Indeed, we already have backport</span><span class="m_-5471532235688025461gmail-author-a-z69zz79z34z79zm1yz74zwz65zz80zyz69z72">ed</span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z"> the eventlet related fix to oslo.service but this fix requires also a nova update to avoid nova CI errors due to threading removal on oslo.service that introduce the nova CI errors.</span></div><div id="m_-5471532235688025461gmail-magicdomid14" class="m_-5471532235688025461gmail-ace-line"><br></div><div id="m_-5471532235688025461gmail-magicdomid15" class="m_-5471532235688025461gmail-ace-line"><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z">A fix was proposed and merged on oslo.service master to introduce a new feature (fixture) that avoid the nova CI errors, but</span></div><div id="m_-5471532235688025461gmail-magicdomid229" class="m_-5471532235688025461gmail-ace-line"><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z">backport</span><span class="m_-5471532235688025461gmail-author-a-z69zz79z34z79zm1yz74zwz65zz80zyz69z72">ing</span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z"> the master fix to Rocky introduce</span><span class="m_-5471532235688025461gmail-author-a-z69zz79z34z79zm1yz74zwz65zz80zyz69z72">s</span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z"> a new feature into a stable branch so this is also an issue.</span></div><div id="m_-5471532235688025461gmail-magicdomid17" class="m_-5471532235688025461gmail-ace-line"><br></div><div id="m_-5471532235688025461gmail-magicdomid18" class="m_-5471532235688025461gmail-ace-line"><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z">So we need to discuss with all the teams to find a proper solution.</span></div><div id="m_-5471532235688025461gmail-magicdomid19" class="m_-5471532235688025461gmail-ace-line"><br></div><div id="m_-5471532235688025461gmail-magicdomid20" class="m_-5471532235688025461gmail-ace-line"><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z"># History</span></div><div id="m_-5471532235688025461gmail-magicdomid21" class="m_-5471532235688025461gmail-ace-line"><br></div><div id="m_-5471532235688025461gmail-magicdomid240" class="m_-5471532235688025461gmail-ace-line"><span class="m_-5471532235688025461gmail-author-a-z69zz79z34z79zm1yz74zwz65zz80zyz69z72">A f</span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z">ew weeks ago this issue was opened on oslo.service (</span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z m_-5471532235688025461gmail-url"><a href="https://bugs.launchpad.net/oslo.service/+bug/1798774)" target="_blank">https://bugs.launchpad.net/oslo.service/+bug/1798774)</a></span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z"> and it was fixed by this submited patch</span><span class="m_-5471532235688025461gmail-author-a-z69zz79z34z79zm1yz74zwz65zz80zyz69z72"> on the master branch</span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z"> ( </span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z m_-5471532235688025461gmail-url"><a href="https://review.openstack.org/#/c/611807/" target="_blank">https://review.openstack.org/#/c/611807/</a></span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z"> ).</span></div><div id="m_-5471532235688025461gmail-magicdomid23" class="m_-5471532235688025461gmail-ace-line"><br></div><div id="m_-5471532235688025461gmail-magicdomid239" class="m_-5471532235688025461gmail-ace-line"><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z">This change use the proper event primitive to fix the performance issue.</span></div><div id="m_-5471532235688025461gmail-magicdomid25" class="m_-5471532235688025461gmail-ace-line"><br></div><div id="m_-5471532235688025461gmail-magicdomid26" class="m_-5471532235688025461gmail-ace-line"><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z">A new version of oslo.service was released (1.32.1)</span></div><div id="m_-5471532235688025461gmail-magicdomid27" class="m_-5471532235688025461gmail-ace-line"><br></div><div id="m_-5471532235688025461gmail-magicdomid241" class="m_-5471532235688025461gmail-ace-line"><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z">Since these changes was introduced into oslo.service master, nova facing some issues into the master CI process, due to the threading changes, and they was fixed by these patches ( </span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z m_-5471532235688025461gmail-url"><a href="https://review.openstack.org/#/c/615724/" target="_blank">https://review.openstack.org/#/c/615724/</a></span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z">, </span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z m_-5471532235688025461gmail-url"><a href="https://review.openstack.org/#/c/617989/" target="_blank">https://review.openstack.org/#/c/617989/</a></span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z"> ) into master.</span></div><div id="m_-5471532235688025461gmail-magicdomid29" class="m_-5471532235688025461gmail-ace-line"><br></div><div id="m_-5471532235688025461gmail-magicdomid243" class="m_-5471532235688025461gmail-ace-line"><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z">Few weeks ago I have backport to oslo.service some changes ( </span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z m_-5471532235688025461gmail-url"><a href="https://review.openstack.org/#/c/614489/" target="_blank">https://review.openstack.org/#/c/614489/</a></span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z"> ) from master to stable/rocky to also fix the problem in the rocky release.</span></div><div id="m_-5471532235688025461gmail-magicdomid31" class="m_-5471532235688025461gmail-ace-line"><br></div><div id="m_-5471532235688025461gmail-magicdomid245" class="m_-5471532235688025461gmail-ace-line"><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z">When this backport was merged we have created a new release of oslo.service (1.31.6) ( </span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z m_-5471532235688025461gmail-url"><a href="https://review.openstack.org/#/c/616505/" target="_blank">https://review.openstack.org/#/c/616505/</a></span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z"> ) (stable/rocky version).</span></div><div id="m_-5471532235688025461gmail-magicdomid33" class="m_-5471532235688025461gmail-ace-line"><br></div><div id="m_-5471532235688025461gmail-magicdomid34" class="m_-5471532235688025461gmail-ace-line"><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z">Then the openstack proposal bot submit a patch to requirements on stable rocky to update the oslo.service version with the latest version (1.31.6) but if we'll use it we'll then break the CI  </span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z m_-5471532235688025461gmail-url"><a href="https://review.openstack.org/#/c/618834/" target="_blank">https://review.openstack.org/#/c/618834/</a></span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z"> so this patch is currently blocked to avoid nova CI error.</span></div><div id="m_-5471532235688025461gmail-magicdomid35" class="m_-5471532235688025461gmail-ace-line"><br></div><div id="m_-5471532235688025461gmail-magicdomid36" class="m_-5471532235688025461gmail-ace-line"><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z"># Issue</span></div><div id="m_-5471532235688025461gmail-magicdomid37" class="m_-5471532235688025461gmail-ace-line"><br></div><div id="m_-5471532235688025461gmail-magicdomid38" class="m_-5471532235688025461gmail-ace-line"><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z">Since the oslo.services threading changes w</span><span class="m_-5471532235688025461gmail-author-a-z69zz79z34z79zm1yz74zwz65zz80zyz69z72">ere</span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z"> backported to rocky we risk to  faces the same issues inside the nova rocky CI if we update the requirements.</span></div><div id="m_-5471532235688025461gmail-magicdomid39" class="m_-5471532235688025461gmail-ace-line"><br></div><div id="m_-5471532235688025461gmail-magicdomid369" class="m_-5471532235688025461gmail-ace-line"><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z">In parallel in oslo.service we have start</span><span class="m_-5471532235688025461gmail-author-a-z69zz79z34z79zm1yz74zwz65zz80zyz69z72">ed</span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z"> to backport a new patch who introduces fixture  ( </span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z m_-5471532235688025461gmail-url"><a href="https://review.openstack.org/#/c/617989/" target="_blank">https://review.openstack.org/#/c/617989/</a></span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z"> ) from master to rocky, and also we start to backport on nova rocky branch ( </span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z m_-5471532235688025461gmail-url"><a href="https://review.openstack.org/619019" target="_blank">https://review.openstack.org/619019</a></span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z">, </span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z m_-5471532235688025461gmail-url"><a href="https://review.openstack.org/619022" target="_blank">https://review.openstack.org/619022</a></span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z"> ) patches who use oslo.service.fixture and who solve the nova CI issue. The patch on oslo.service exposes a public oslo_service.fixture.SleepFixture for this purpose. It can be maintained opaquely as internals change without affecting its consumers. </span></div><div id="m_-5471532235688025461gmail-magicdomid41" class="m_-5471532235688025461gmail-ace-line"><br></div><div id="m_-5471532235688025461gmail-magicdomid42" class="m_-5471532235688025461gmail-ace-line"><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z">The main problem is that the patch bring a new functionality to a stable branch (oslo.service rocky) but this patch help to fix the nova issue.</span></div><div id="m_-5471532235688025461gmail-magicdomid43" class="m_-5471532235688025461gmail-ace-line"><br></div><div id="m_-5471532235688025461gmail-magicdomid44" class="m_-5471532235688025461gmail-ace-line"><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z">Also openstack proposal bot submit a patch to requirements on stable rocky to update the oslo.service version with the latest version (1.31.6) but if we'll use it we'll then break the CI  </span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z m_-5471532235688025461gmail-url"><a href="https://review.openstack.org/#/c/618834/" target="_blank">https://review.openstack.org/#/c/618834/</a></span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z"> since the oslo service 1.31.6 is incompatible with novas stable rocky unittest due to the threading changes.</span></div><div id="m_-5471532235688025461gmail-magicdomid45" class="m_-5471532235688025461gmail-ace-line"><br></div><div id="m_-5471532235688025461gmail-magicdomid46" class="m_-5471532235688025461gmail-ace-line"><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z"># Questions and proposed solutions</span></div><div id="m_-5471532235688025461gmail-magicdomid47" class="m_-5471532235688025461gmail-ace-line"><br></div><div id="m_-5471532235688025461gmail-magicdomid48" class="m_-5471532235688025461gmail-ace-line"><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z">This thread try to summarize the current situation.</span></div><div id="m_-5471532235688025461gmail-magicdomid49" class="m_-5471532235688025461gmail-ace-line"><br></div><div id="m_-5471532235688025461gmail-magicdomid50" class="m_-5471532235688025461gmail-ace-line"><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z">We need to find how to be able to proceed, so this thread aim to allow to discuss between team to find the best way to fix.</span></div><div id="m_-5471532235688025461gmail-magicdomid51" class="m_-5471532235688025461gmail-ace-line"><br></div><div id="m_-5471532235688025461gmail-magicdomid52" class="m_-5471532235688025461gmail-ace-line"><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z">1. Do we need to continue to try to backport fixture on oslo.service to fix the CI problem (</span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z m_-5471532235688025461gmail-url"><a href="https://review.openstack.org/#/c/617989/)" target="_blank">https://review.openstack.org/#/c/617989/)</a></span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z"> ?</span></div><div id="m_-5471532235688025461gmail-magicdomid53" class="m_-5471532235688025461gmail-ace-line"><br></div><div id="m_-5471532235688025461gmail-magicdomid54" class="m_-5471532235688025461gmail-ace-line"><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z">2. Do we need to find an another approach like mocking oslo.service.loopingcall._Event.wait in nova instead of mocking oslo_service.loopingcall._ThreadingEvent.wait (example: </span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z m_-5471532235688025461gmail-url"><a href="https://review.openstack.org/#/c/616697/2/nova/tests/unit/compute/test_compute_mgr.py)" target="_blank">https://review.openstack.org/#/c/616697/2/nova/tests/unit/compute/test_compute_mgr.py)</a></span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z"> ?  </span></div><div id="m_-5471532235688025461gmail-magicdomid235" class="m_-5471532235688025461gmail-ace-line"><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z">This is only a fix on the nova side and </span><span class="m_-5471532235688025461gmail-author-a-z69zz79z34z79zm1yz74zwz65zz80zyz69z72">it</span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z"> allow</span><span class="m_-5471532235688025461gmail-author-a-z69zz79z34z79zm1yz74zwz65zz80zyz69z72">s</span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z"> us to update oslo.service requirements and allow</span><span class="m_-5471532235688025461gmail-author-a-z69zz79z34z79zm1yz74zwz65zz80zyz69z72">s</span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z"> us to fix the high CPU usage issue. I've submit this patch (</span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z m_-5471532235688025461gmail-url"><a href="https://review.openstack.org/619246)" target="_blank">https://review.openstack.org/619246)</a></span><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z"> who implement the description above.</span></div><div id="m_-5471532235688025461gmail-magicdomid56" class="m_-5471532235688025461gmail-ace-line"><br></div><div id="m_-5471532235688025461gmail-magicdomid118" class="m_-5471532235688025461gmail-ace-line"><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z">Personaly I think we need to find an another approach like the mocking remplacement (c.f 2).</span></div><div id="m_-5471532235688025461gmail-magicdomid120" class="m_-5471532235688025461gmail-ace-line"><br></div><div id="m_-5471532235688025461gmail-magicdomid185" class="m_-5471532235688025461gmail-ace-line"><span class="m_-5471532235688025461gmail-author-a-o0z122zo9qz74zz66zz69zz66zgdxz89zz75zz65z">We need to decide which way we use and to discuss about other solutions.</span></div><div><br>-- <br><div dir="ltr" class="m_-5471532235688025461m_5390074029165786051gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div>Hervé Beraud</div><div>Senior Software Engineer<br></div><div>Red Hat - Openstack Oslo</div><div>irc: hberaud</div><div>-----BEGIN PGP SIGNATURE-----<br><br>wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+<br>Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+<br>RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP<br>F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G<br>5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g<br>glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw<br>m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ<br>hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0<br>qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y<br>F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3<br>B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O<br>v6rDpkeNksZ9fFSyoY2o<br>=ECSj<br>-----END PGP SIGNATURE-----<br><br></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div>Hervé Beraud</div><div>Senior Software Engineer<br></div><div>Red Hat - Openstack Oslo</div><div>irc: hberaud</div><div>-----BEGIN PGP SIGNATURE-----<br><br>wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+<br>Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+<br>RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP<br>F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G<br>5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g<br>glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw<br>m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ<br>hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0<br>qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y<br>F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3<br>B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O<br>v6rDpkeNksZ9fFSyoY2o<br>=ECSj<br>-----END PGP SIGNATURE-----<br><br></div></div></div></div></div></div></div></div></div></div></div></div></div>