[Openstack-operators] [nova][placement] Placement requests and caching in the resource tracker
openstack at fried.cc
Fri Nov 2 19:22:53 UTC 2018
Based on a (long) discussion yesterday  I have put up a patch 
whereby you can set [compute]resource_provider_association_refresh to
zero and the resource tracker will never* refresh the report client's
provider cache. Philosophically, we're removing the "healing" aspect of
the resource tracker's periodic and trusting that placement won't
diverge from whatever's in our cache. (If it does, it's because the op
hit the CLI, in which case they should SIGHUP - see below.)
- When we initially create the compute node record and bootstrap its
- When the virt driver's update_provider_tree makes a change,
update_from_provider_tree reflects them in the cache as well as pushing
them back to placement.
- If update_from_provider_tree fails, the cache is cleared and gets
rebuilt on the next periodic.
- If you send SIGHUP to the compute process, the cache is cleared.
This should dramatically reduce the number of calls to placement from
the compute service. Like, to nearly zero, unless something is actually
Can I get some initial feedback as to whether this is worth polishing up
into something real? (It will probably need a bp/spec if so.)
In the Queens release, our friends at CERN noticed a serious spike in
the number of requests to placement from compute nodes, even in a
stable-state cloud. Given that we were in the process of adding a ton of
infrastructure to support sharing and nested providers, this was not
unexpected. Roughly, what was previously:
became more like:
# In Queens/Rocky, this would still just return the compute RP
# In Queens/Rocky, this would return nothing
for each provider returned above: # i.e. just one in Q/R
In a cloud the size of CERN's, the load wasn't acceptable. But at the
time, CERN worked around the problem by disabling refreshing entirely.
(The fact that this seems to have worked for them is an encouraging sign
for the proposed code change.)
We're not actually making use of most of that information, but it sets
the stage for things that we're working on in Stein and beyond, like
multiple VGPU types, bandwidth resource providers, accelerators, NUMA,
etc., so removing/reducing the amount of information we look at isn't
really an option strategically.
More information about the OpenStack-operators