Placement update 25. Only 75 more to reach 100.
# What Matters Most
Claims against the placement API remain the highest priority. There's
plenty of other work in progress too which needs to advance. Lots of
# What's Changed
The entire shared resource providers stack has merged. This doesn't
mean we have support for them yet, but rather that it is possible to
express a query of the placement db that will include results
that are associated (via aggregates) with shared resource providers.
A new version of the os-traits library was required because the
routine it was using to walk modules could escape the local package,
leading to either brokenness or at least weirdness.
Work has begun on having project and user id information included in
allocations (see below).
Incremental progress across many other areas.
# Help Wanted
(This section _has_ changed since last time, removing some bug links
because the fixes have been started and are now linked below.)
Areas where volunteers are needed.
* General attention to bugs tagged placement:
* Helping to create api documentation for placement (see the Docs
# Main Themes
## Claims in the Scheduler
Work is in progress on having the scheduler make resource claims.
The current choice for how to do this is to pass instance uuids as a
separate parameter in the RPC call to select_destinations. This
information is required to be able to make the claims/allocations
(which are identified by consumer uuid).
The main API is in place. Debate raged on how best to manage updates
of standard os-traits. Eventually a simple sync done once per
process seemed like the way to go, without having a cache:
This needs to address some concurrency issues.
There's also a small cleanup to the os-traits library:
## Shared Resource Providers
The stack that makes the database side of things start to work has
This will allow work on the API and resource-tracker/scheduler side
to move along.
Lots of placement-related api docs in progress on a few different
We should a) probably get that stuff on the same topic, b) make sure
work is not being duplicated.
## Nested Resource Providers
Work has resumed on nested resource providers.
Currently having some good review discussion on data structures and
graph traversal and search. It's a bit like being back in school.
## User and Project IDs in Allocations
This will allow placement allocations to be considered when doing
resource accounting for things like quota. User id and project id
information is added to allocation records and a new API resource is
added to be able to get summaries of usage by user or project.
# Other Code/Specs
Use DELETE inventories method in report client.
Add a status check for legacy filters in nova-status.
Handle new hosts for updating instance info in scheduler
Currently in merge conflict.
Don't send instance updates from compute if not using filter
Work has started on an osc-plugin that can provide a command
line interface to the placement API.
It's quite likely that this code is going to need to be adopted by
Devstack change to install that plugin. This has two +2, but no
Cleanups for _schedule_instances()
Update placement.rst to link to more specs
Provide more information about installing placement
Disambiguate resource provider conflict message
Adjust resource provider links by microversion
I was unable to go digging for things as much as usual this week due
to other business. If I've missed something, my apologies, please
add it to the thread in a followup.
Your prize is some cornish clotted cream.
Chris Dent ┬──┬◡ﾉ(° -°ﾉ) https://anticdent.org/
freenode: cdent tw: @anticdent
OpenStack Development Mailing List (not for usage questions)