On 7/30/2018 1:55 PM, Jay Pipes wrote:
ack. will review shortly. thanks, Chris.
For those on the edge of their seats at home, we have merged [1] in
Stein and assuming things don't start failing in weird ways after some
period of time, we'll probably backport it. OVH is already running with it
ack. will review shortly. thanks, Chris.
On 07/30/2018 02:20 PM, Chris Dent wrote:
On Mon, 30 Jul 2018, Jay Pipes wrote:
On 07/26/2018 12:15 PM, Chris Dent wrote:
The `in_tree` calls happen from the report client method
`_get_providers_in_tree` which is called by
`_ensure_resource_provider` w
On Mon, 30 Jul 2018, Jay Pipes wrote:
On 07/26/2018 12:15 PM, Chris Dent wrote:
The `in_tree` calls happen from the report client method
`_get_providers_in_tree` which is called by
`_ensure_resource_provider` which can be called from multiple
places, but in this case is being called both times
On 07/26/2018 12:15 PM, Chris Dent wrote:
The `in_tree` calls happen from the report client method
`_get_providers_in_tree` which is called by
`_ensure_resource_provider` which can be called from multiple
places, but in this case is being called both times from
`get_provider_tree_and_ensure_root`
HTML: https://anticdent.org/novas-use-of-placement.html
A year and a half ago I did some analysis on how [nova uses
placement](http://lists.openstack.org/pipermail/openstack-dev/2017-January/110953.html).
I've repeated some of that analysis today and here's a brief summary
of the results. Note