Re: [openstack-dev] [nova] Latest and greatest on trying to get n-sch to require placement

2017-01-27 Thread Matt Riedemann
On 1/26/2017 8:40 AM, Matt Riedemann wrote: And circling back on *that*, we've agreed to introduce a new service version for the compute to indicate it's Ocata or not. Then we'll: * check in the scheduler if the minimum compute service version is ocata, * if minimum is ocata, then use placement

Re: [openstack-dev] [nova] Latest and greatest on trying to get n-sch to require placement

2017-01-26 Thread Jay Pipes
On 01/26/2017 09:14 AM, Ed Leafe wrote: On Jan 26, 2017, at 7:50 AM, Sylvain Bauza wrote: That's where I think we have another problem, which is bigger than the corner case you mentioned above : when upgrading from Newton to Ocata, we said that all Newton computes have be upgraded to the lates

Re: [openstack-dev] [nova] Latest and greatest on trying to get n-sch to require placement

2017-01-26 Thread Matt Riedemann
On 1/26/2017 7:41 AM, Sylvain Bauza wrote: Circling back to the problem as time flies. As the patch Matt proposed for option #4 is not fully working yet, I'm implementing option #3 by making the HostManager.get_filtered_hosts() method being resilient to the fact that there are no hosts given by

Re: [openstack-dev] [nova] Latest and greatest on trying to get n-sch to require placement

2017-01-26 Thread Sylvain Bauza
Le 26/01/2017 05:42, Matt Riedemann a écrit : > This is my public hand off to Sylvain for the work done tonight. > > Starting with the multinode grenade failure in the nova patch to > integrate placement with the filter scheduler: > > https://review.openstack.org/#/c/417961/ > > The test_sched

Re: [openstack-dev] [nova] Latest and greatest on trying to get n-sch to require placement

2017-01-26 Thread Sylvain Bauza
Le 26/01/2017 15:14, Ed Leafe a écrit : > On Jan 26, 2017, at 7:50 AM, Sylvain Bauza wrote: >> >> That's where I think we have another problem, which is bigger than the >> corner case you mentioned above : when upgrading from Newton to Ocata, >> we said that all Newton computes have be upgraded

Re: [openstack-dev] [nova] Latest and greatest on trying to get n-sch to require placement

2017-01-26 Thread John Garbutt
On 26 January 2017 at 14:14, Ed Leafe wrote: > On Jan 26, 2017, at 7:50 AM, Sylvain Bauza wrote: >> >> That's where I think we have another problem, which is bigger than the >> corner case you mentioned above : when upgrading from Newton to Ocata, >> we said that all Newton computes have be upgra

Re: [openstack-dev] [nova] Latest and greatest on trying to get n-sch to require placement

2017-01-26 Thread Ed Leafe
On Jan 26, 2017, at 7:50 AM, Sylvain Bauza wrote: > > That's where I think we have another problem, which is bigger than the > corner case you mentioned above : when upgrading from Newton to Ocata, > we said that all Newton computes have be upgraded to the latest point > release. Great. But we fo

Re: [openstack-dev] [nova] Latest and greatest on trying to get n-sch to require placement

2017-01-26 Thread John Garbutt
On 26 January 2017 at 13:50, Sylvain Bauza wrote: > Le 26/01/2017 05:42, Matt Riedemann a écrit : >> This is my public hand off to Sylvain for the work done tonight. >> > > Thanks Matt for your help yesterday, was awesome to count you in even > you're personally away. > > >> Starting with the mult

Re: [openstack-dev] [nova] Latest and greatest on trying to get n-sch to require placement

2017-01-26 Thread Sylvain Bauza
Le 26/01/2017 05:42, Matt Riedemann a écrit : > This is my public hand off to Sylvain for the work done tonight. > Thanks Matt for your help yesterday, was awesome to count you in even you're personally away. > Starting with the multinode grenade failure in the nova patch to > integrate place

[openstack-dev] [nova] Latest and greatest on trying to get n-sch to require placement

2017-01-25 Thread Matt Riedemann
This is my public hand off to Sylvain for the work done tonight. Starting with the multinode grenade failure in the nova patch to integrate placement with the filter scheduler: https://review.openstack.org/#/c/417961/ The test_schedule_to_all_nodes tempest test was failing in there because t