<div dir="ltr"><div dir="ltr"><div>Hey Naichuan, <br></div><div>FWIW, we discussed on the missing pieces for nested resource providers. See the (currently-in-use) etherpad <a href="https://etherpad.openstack.org/p/nova-ptg-stein">https://etherpad.openstack.org/p/nova-ptg-stein</a> and lookup for "closing the gap on nested resource providers" (L144 while I speak)</div><div><br></div><div>The fact that we are not able to schedule yet is a critical piece that we said we're going to work on it as soon as we can.</div><div><br></div><div>-Sylvain<br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 13, 2018 at 9:14 AM, Eric Fried <span dir="ltr"><<a href="mailto:openstack@fried.cc" target="_blank">openstack@fried.cc</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">There's a patch series in progress for this:<br>
<br>
<a href="https://review.openstack.org/#/q/topic:use-nested-allocation-candidates" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/q/topic:use-nested-<wbr>allocation-candidates</a><br>
<br>
It needs some TLC. I'm sure gibi and tetsuro would welcome some help...<br>
<br>
efried<br>
<div><div class="h5"><br>
On 09/13/2018 08:31 AM, Naichuan Sun wrote:<br>
> Thank you very much, Jay.<br>
> Is there somewhere I could set microversion(some configure file?), Or just modify the source code to set it?<br>
> <br>
> BR.<br>
> Naichuan Sun<br>
> <br>
> -----Original Message-----<br>
> From: Jay Pipes [mailto:<a href="mailto:jaypipes@gmail.com">jaypipes@gmail.com</a>] <br>
> Sent: Thursday, September 13, 2018 9:19 PM<br>
> To: Naichuan Sun <<a href="mailto:naichuan.sun@citrix.com">naichuan.sun@citrix.com</a>>; OpenStack Development Mailing List (not for usage questions) <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.<wbr>openstack.org</a>><br>
> Cc: melanie witt <<a href="mailto:melwittt@gmail.com">melwittt@gmail.com</a>>; <a href="mailto:efried@us.ibm.com">efried@us.ibm.com</a>; Sylvain Bauza <<a href="mailto:sbauza@redhat.com">sbauza@redhat.com</a>><br>
> Subject: Re: About microversion setting to enable nested resource provider<br>
> <br>
> On 09/13/2018 06:39 AM, Naichuan Sun wrote:<br>
>> Hi, guys,<br>
>><br>
>> Looks n-rp is disabled by default because microversion matches 1.29 : <br>
>> <a href="https://github.com/openstack/nova/blob/master/nova/api/openstack/place" rel="noreferrer" target="_blank">https://github.com/openstack/<wbr>nova/blob/master/nova/api/<wbr>openstack/place</a><br>
>> ment/handlers/allocation_<wbr>candidate.py#L252<br>
>><br>
>> Anyone know how to set the microversion to enable n-rp in placement?<br>
> <br>
> It is the client which must send the 1.29+ placement API microversion header to indicate to the placement API server that the client wants to receive nested provider information in the allocation candidates response.<br>
> <br>
> Currently, nova-scheduler calls the scheduler reportclient's<br>
> get_allocation_candidates() method:<br>
> <br>
> <a href="https://github.com/openstack/nova/blob/0ba34a818414823eda5e693dc2127a534410b5df/nova/scheduler/manager.py#L138" rel="noreferrer" target="_blank">https://github.com/openstack/<wbr>nova/blob/<wbr>0ba34a818414823eda5e693dc2127a<wbr>534410b5df/nova/scheduler/<wbr>manager.py#L138</a><br>
> <br>
> The scheduler reportclient's get_allocation_candidates() method currently passes the 1.25 placement API microversion header:<br>
> <br>
> <a href="https://github.com/openstack/nova/blob/0ba34a818414823eda5e693dc2127a534410b5df/nova/scheduler/client/report.py#L353" rel="noreferrer" target="_blank">https://github.com/openstack/<wbr>nova/blob/<wbr>0ba34a818414823eda5e693dc2127a<wbr>534410b5df/nova/scheduler/<wbr>client/report.py#L353</a><br>
> <br>
> <a href="https://github.com/openstack/nova/blob/0ba34a818414823eda5e693dc2127a534410b5df/nova/scheduler/client/report.py#L53" rel="noreferrer" target="_blank">https://github.com/openstack/<wbr>nova/blob/<wbr>0ba34a818414823eda5e693dc2127a<wbr>534410b5df/nova/scheduler/<wbr>client/report.py#L53</a><br>
> <br>
> In order to get the nested information returned in the allocation candidates response, that would need to be upped to 1.29.<br>
> <br>
> Best,<br>
> -jay<br>
</div></div>> ______________________________<wbr>______________________________<wbr>______________<br>
<span class="">> OpenStack Development Mailing List (not for usage questions)<br>
</span>> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
> <br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
<span class="">OpenStack Development Mailing List (not for usage questions)<br>
</span>Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
</blockquote></div><br></div>