[placement] update 19-09

Matt Riedemann mriedemos at gmail.com
Fri Mar 8 17:35:11 UTC 2019

On 3/8/2019 8:51 AM, Chris Dent wrote:
> We need to decide if we want to do what amounts to a feature freeze
> exception for Tetsuro's negative member-of handling linked below and
> work out how/when to fit Mel's allocation ratio work on
> osc-placement (also below) into the world so people can use it.

Probably not surprisingly I'm a -1 on pushing this stuff in after 
feature freeze. We have two weeks to RC1 and people should be focusing 
on testing, bug triage, release notes and other feature documentation.
Also, I'm pretty sure there is nothing in either nova or blazar that is 
currently not going to merge in stein if this doesn't land in Stein, so 
based on that it can wait until Train IMO.

As for the osc-placement change, I think we can also defer that to 
Train. It's been talked about since the Dublin PTG and is just now 
getting implemented, which is good, but also means it's apparently low 
priority for people and therefore can wait until Train (we won't have 
another osc-placement release in Stein anyway since clients are frozen 
now). Also, since it's a client, it will work with older versions of the 
placement API anyway, i.e. osc-placement in Train should work fine with 
placement from Queens, so again I don't see a rush here.

> There were no nibbles on last week's plea, so I'll say again: If
> anyone reading this is in a position to provide third party CI with
> fancy hardware for NUMA, NFV, FPGA, and GPU related integration
> testing with nova, there's a significant need for that.

There is some discussion happening in OpenLab about this:





More information about the openstack-discuss mailing list