On 01/11/2017 01:11 PM, Chris Dent wrote:
On Fri, 6 Jan 2017, Chris Dent wrote:
## can_host, aggregates in filtering
There's still some confusion (from at least me) on whether the
can_host field is relevant when making queries to filter resource
providers. Similarly, when requesting resource
On Wed, 11 Jan 2017, Chris Dent wrote:
The basis for this conclusion is from three assumptions:
* The value of 'local_gb' on the compute_node object is any disk the
compute_node can see/use and the concept of associating with shared
disk by aggregates is not something that is real yet[0].
*
On 01/09/2017 05:29 AM, Chris Dent wrote:
On Fri, 6 Jan 2017, Chris Dent wrote:
* CORS support in placement API:
https://review.openstack.org/#/c/392891/
This is one we should probably get in in Ocata because it enables
the sole piece of configurability that is present in the WSGI
On Fri, 6 Jan 2017, Chris Dent wrote:
## can_host, aggregates in filtering
There's still some confusion (from at least me) on whether the
can_host field is relevant when making queries to filter resource
providers. Similarly, when requesting resource providers to satisfy a
set of resources, we
On Fri, 6 Jan 2017, Chris Dent wrote:
* CORS support in placement API:
https://review.openstack.org/#/c/392891/
This is one we should probably get in in Ocata because it enables
the sole piece of configurability that is present in the WSGI
middleware stack used for the placement API. Unlike
Welcome to the first placement/resource providers update for 2017.
There's a lot in progress, including plenty of work from new
contributors. Is great to see that.
# What Matters Most
The main priority remains the same: Getting the scheduler using a
filtered list of resource providers. That
