There's a patch series in progress for this: https://review.openstack.org/#/q/topic:use-nested-allocation-candidates
It needs some TLC. I'm sure gibi and tetsuro would welcome some help... efried On 09/13/2018 08:31 AM, Naichuan Sun wrote: > Thank you very much, Jay. > Is there somewhere I could set microversion(some configure file?), Or just > modify the source code to set it? > > BR. > Naichuan Sun > > -----Original Message----- > From: Jay Pipes [mailto:jaypi...@gmail.com] > Sent: Thursday, September 13, 2018 9:19 PM > To: Naichuan Sun <naichuan....@citrix.com>; OpenStack Development Mailing > List (not for usage questions) <openstack-dev@lists.openstack.org> > Cc: melanie witt <melwi...@gmail.com>; efr...@us.ibm.com; Sylvain Bauza > <sba...@redhat.com> > Subject: Re: About microversion setting to enable nested resource provider > > On 09/13/2018 06:39 AM, Naichuan Sun wrote: >> Hi, guys, >> >> Looks n-rp is disabled by default because microversion matches 1.29 : >> https://github.com/openstack/nova/blob/master/nova/api/openstack/place >> ment/handlers/allocation_candidate.py#L252 >> >> Anyone know how to set the microversion to enable n-rp in placement? > > 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. > > Currently, nova-scheduler calls the scheduler reportclient's > get_allocation_candidates() method: > > https://github.com/openstack/nova/blob/0ba34a818414823eda5e693dc2127a534410b5df/nova/scheduler/manager.py#L138 > > The scheduler reportclient's get_allocation_candidates() method currently > passes the 1.25 placement API microversion header: > > https://github.com/openstack/nova/blob/0ba34a818414823eda5e693dc2127a534410b5df/nova/scheduler/client/report.py#L353 > > https://github.com/openstack/nova/blob/0ba34a818414823eda5e693dc2127a534410b5df/nova/scheduler/client/report.py#L53 > > In order to get the nested information returned in the allocation candidates > response, that would need to be upped to 1.29. > > Best, > -jay > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
