Re: [openstack-dev] [nova] Order of n-api (placement) and n-sch upgrades for Ocata

On 1/20/2017 9:00 AM, Matt Riedemann wrote: On 1/20/2017 4:53 AM, Eoghan Glynn wrote: Do we also need to be concerned about the placement API "warm-up" time? i.e. if a placement-less newton deployment is upgraded to placement-ful ocata, then would there surely be a short period during which

Re: [openstack-dev] [nova] Order of n-api (placement) and n-sch upgrades for Ocata

On 1/20/2017 4:53 AM, Eoghan Glynn wrote: Do we also need to be concerned about the placement API "warm-up" time? i.e. if a placement-less newton deployment is upgraded to placement-ful ocata, then would there surely be a short period during which placement is able to respond to the incoming

Re: [openstack-dev] [nova] Order of n-api (placement) and n-sch upgrades for Ocata

> >> What are these issues? My original message was to highlight one > >> particular deployment type which is completely independent of > >> how things get packaged in the traditional sense of the word > >> (rpms/deb/tar.gz). Perhaps it's getting lost in terminology, > >> but packaging the

Re: [openstack-dev] [nova] Order of n-api (placement) and n-sch upgrades for Ocata

2017-01-19 23:43 GMT+08:00 Sylvain Bauza : > > > Le 19/01/2017 16:27, Matt Riedemann a écrit : > > Sylvain and I were talking about how he's going to work placement > > microversion requests into his filter scheduler patch [1]. He needs to > > make requests to the placement API

Re: [openstack-dev] [nova] Order of n-api (placement) and n-sch upgrades for Ocata

Le 19/01/2017 21:39, Matt Riedemann a écrit : > On Thu, Jan 19, 2017 at 2:29 PM, Alex Schultz > wrote: >> >> What are these issues? My original message was to highlight one >> particular deployment type which is completely independent of >> how things get packaged in the

Re: [openstack-dev] [nova] Order of n-api (placement) and n-sch upgrades for Ocata

On Thu, Jan 19, 2017 at 2:29 PM, Alex Schultz wrote: > > What are these issues? My original message was to highlight one > particular deployment type which is completely independent of how > things get packaged in the traditional sense of the word > (rpms/deb/tar.gz).

Re: [openstack-dev] [nova] Order of n-api (placement) and n-sch upgrades for Ocata

On Thu, Jan 19, 2017 at 11:45 AM, Jay Pipes wrote: > On 01/19/2017 01:18 PM, Alex Schultz wrote: >> >> On Thu, Jan 19, 2017 at 10:34 AM, Jay Pipes wrote: >>> >>> On 01/19/2017 11:25 AM, Alex Schultz wrote: On Thu, Jan 19, 2017 at 8:27 AM,

Re: [openstack-dev] [nova] Order of n-api (placement) and n-sch upgrades for Ocata

On 01/19/2017 12:59 PM, Eoghan Glynn wrote: I think Alex is suggesting something different than falling back to the legacy behaviour. The ocata scheduler would still roll forward to basing its node selection decisions on data provided by the placement API, but would be tolerant of the 3

Re: [openstack-dev] [nova] Order of n-api (placement) and n-sch upgrades for Ocata

On 01/19/2017 01:18 PM, Alex Schultz wrote: On Thu, Jan 19, 2017 at 10:34 AM, Jay Pipes wrote: On 01/19/2017 11:25 AM, Alex Schultz wrote: On Thu, Jan 19, 2017 at 8:27 AM, Matt Riedemann wrote: Sylvain and I were talking about how he's going

Re: [openstack-dev] [nova] Order of n-api (placement) and n-sch upgrades for Ocata

On Thu, Jan 19, 2017 at 10:34 AM, Jay Pipes wrote: > On 01/19/2017 11:25 AM, Alex Schultz wrote: >> >> On Thu, Jan 19, 2017 at 8:27 AM, Matt Riedemann >> wrote: >>> >>> Sylvain and I were talking about how he's going to work placement >>>

Re: [openstack-dev] [nova] Order of n-api (placement) and n-sch upgrades for Ocata

> >> Sylvain and I were talking about how he's going to work placement > >> microversion requests into his filter scheduler patch [1]. He needs to > >> make > >> requests to the placement API with microversion 1.4 [2] or later for > >> resource provider filtering on specific resource classes like

Re: [openstack-dev] [nova] Order of n-api (placement) and n-sch upgrades for Ocata

On 01/19/2017 11:25 AM, Alex Schultz wrote: On Thu, Jan 19, 2017 at 8:27 AM, Matt Riedemann wrote: Sylvain and I were talking about how he's going to work placement microversion requests into his filter scheduler patch [1]. He needs to make requests to the placement

Re: [openstack-dev] [nova] Order of n-api (placement) and n-sch upgrades for Ocata

Le 19/01/2017 17:00, Matt Riedemann a écrit : > On 1/19/2017 9:43 AM, Sylvain Bauza wrote: >> >> >> Le 19/01/2017 16:27, Matt Riedemann a écrit : >>> Sylvain and I were talking about how he's going to work placement >>> microversion requests into his filter scheduler patch [1]. He needs to >>>

Re: [openstack-dev] [nova] Order of n-api (placement) and n-sch upgrades for Ocata

On Thu, Jan 19, 2017 at 8:27 AM, Matt Riedemann wrote: > Sylvain and I were talking about how he's going to work placement > microversion requests into his filter scheduler patch [1]. He needs to make > requests to the placement API with microversion 1.4 [2] or later

Re: [openstack-dev] [nova] Order of n-api (placement) and n-sch upgrades for Ocata

On 1/19/2017 9:43 AM, Sylvain Bauza wrote: Le 19/01/2017 16:27, Matt Riedemann a écrit : Sylvain and I were talking about how he's going to work placement microversion requests into his filter scheduler patch [1]. He needs to make requests to the placement API with microversion 1.4 [2] or

Re: [openstack-dev] [nova] Order of n-api (placement) and n-sch upgrades for Ocata

Le 19/01/2017 16:27, Matt Riedemann a écrit : > Sylvain and I were talking about how he's going to work placement > microversion requests into his filter scheduler patch [1]. He needs to > make requests to the placement API with microversion 1.4 [2] or later > for resource provider filtering on