<div dir="ltr">
<blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px"></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span style="font-size:14px"># Questions<br></span><span style="font-size:14px">What's the status of shared resource providers? Did we even talk<br></span><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:14px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">about that in Dublin?</span></blockquote><div><br></div><div>In terms of bug fixes related to allocation candidates, I'll try to answer that question :) </div><div><div>Most of the bugs that have been reported in <a href="https://bugs.launchpad.net/nova/+bug/1731072">https://bugs.launchpad.net/nova/+bug/1731072</a> are sorted out and already fixed in Queens.</div><div><br></div><div>But we have some items left.</div><div><br></div><div>* <a href="https://review.openstack.org/#/c/533396">https://review.openstack.org/#/c/533396</a></div><div>AllocationCandidates.get_by_filters ignores shared RPs when the RC exists in both places</div><div><br></div><div>* <a href="https://review.openstack.org/#/c/519601/">https://review.openstack.org/#/c/519601/</a></div><div>* <a href="https://review.openstack.org/#/c/533437/">https://review.openstack.org/#/c/533437/</a></div><div>AllocationCandidates.get_by_filters does not handle indirectly connected sharing RPs</div><div>-> In the PTG, we discussed if we need “anchor” RPs in the response of the API, and if I get it correctly the agreement was "let’s re-open this once we face a concrete use case." I have updated the patches according to that conclusion.</div><div><br></div><div>* <a href="https://review.openstack.org/#/c/533195/">https://review.openstack.org/#/c/533195/</a></div><div>Placement returns no allocation candidate for request that needs both compute resources and custom shared resources</div><div>-> This is already fixed, and trivial comment fix is left and ready for review.</div><div><br></div><div>* No fix proposed - <a href="https://bugs.launchpad.net/nova/+bug/1724633">https://bugs.launchpad.net/nova/+bug/1724633</a></div><div>AllocationCandidates.get_by_filters hits incorrectly when traits are split across the main RP and aggregates</div><div>-> This is hard to fix as long as traits belong not to resource classes but to resource providers. While the current design allows a consumer to pick resource classes from multiple resource providers (in the same aggregate), we have no way to know which trait corresponds to which resource class.</div><div><br></div><div>Besides these bugs, how we collaborate and merge existing logic of shared resource provider and now being constructed logic of nested resource provider remains one of the challenges in Rocky in my understanding.</div><div><br></div><div>Thanks!</div></div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px"></blockquote></div>