[placement] update 19-28
This is pupdate 19-28. Next week is the Train-2 milestone.
# Most Important
Based on the discussion on the [PTG attendance
and the notes on the [related
I'm going to tell the Foundation there will be approximately seven
Placement team members at Shanghai but formal space or scheduling
will not be required. Instead any necessary discussions will be
arranged on premise. If you disagree with this, please speak up
The main pending feature is consumer types, see below.
# What's Changed
* A bug in the resource class cache used in the placement server was
found and [fixed](https://review.opendev.org/671341). It will be
interesting to see how this impacts performance. While it
increases database reads by one (for most requests) it removes a
process-wide lock, so things could improve in threaded servers.
released, adding FPGA and PGPU resource classes.
It's been discussed in IRC that we may wish to make 1.x releases
of both os-resource-classes and os-traits at some point to make
it clear that they are "real". If we do this, I recommend we do
it near a cycle boundary.
* An [integrated-gate-placement](https://review.opendev.org/669309)
zuul template has merged. A [placement change to use
it](https://review.opendev.org/671257) is ready and waiting to
merge. This avoids running some tests which are unrelated; for
example, cinder-only tests.
Since spec freeze for most projects is next week and placement has
merged all its specs, until U opens, I'm going to skip this section.
(Numbers in () are the change since the last pupdate.)
There are 22 (-1) stories in [the placement
0 (0) are [untagged](https://storyboard.openstack.org/#!/worklist/580).
2 (-1) are [bugs](https://storyboard.openstack.org/#!/worklist/574). 5 (0)
are [cleanups](https://storyboard.openstack.org/#!/worklist/575). 10
(-1) are [rfes](https://storyboard.openstack.org/#!/worklist/594).
4 (0) are [docs](https://storyboard.openstack.org/#!/worklist/637).
If you're interested in helping out with placement, those stories
are good places to look.
* Placement related nova [bugs not yet in progress](https://goo.gl/TgiPXb)
on launchpad: 17 (1).
* Placement related nova [in progress bugs](https://goo.gl/vzGGDQ) on
launchpad: 4 (0).
osc-placement is currently behind by 11 microversions.
Add support for multiple member_of. There's been some useful
discussion about how to achieve this, and a consensus has emerged
on how to get the best results.
# Main Themes
## Consumer Types
Adding a type to consumers will allow them to be grouped for various
purposes, including quota accounting.
This is currently the migration to add the necessary table and
Cleanup is an overarching theme related to improving documentation,
performance and the maintainability of the code. The changes we are
making this cycle are fairly complex to use and are fairly complex
to write, so it is good that we're going to have plenty of time to
clean and clarify all these things.
As mentioned for a few weeks, one of the important cleanup tasks
that is not yet in progress is updating the
that creates the nested topology that's used in nested performance
testing. We've [asked the startlingx
Another cleanup that needs to start is satisfying the community wide
goal of [PDF doc
did some experimenting on this and while I was able to get a book
created, the number of errors, warnings, and manual interventions
required meant I gave up until there's time to do a more in-depth
exploration and learn the tools.
# Other Placement
Miscellaneous changes can be found in [the usual
There are two [os-traits
being discussed. And zero [os-resource-classes
# Other Service Users
New discoveries are added to the end. Merged stuff is removed.
Anything that has had no activity in 4 weeks has been removed.
Nova: nova-manage: heal port allocations
nova-spec: Allow compute nodes to use DISK_GB from shared storage RP
Cyborg: Placement report
helm: add placement chart
Nova: Use OpenStack SDK for placement
Nova: Spec: Provider config YAML file
libvirt: report pmem namespaces resources by provider tree
Nova: Remove PlacementAPIConnectFailure handling from AggregateAPI
Nova: support move ops with qos ports
Nova: get_ksa_adapter: nix by-service-type confgrp hack
Blazar: Create placement client for each request
nova: Support filtering of hosts by forbidden aggregates
blazar: Send global_request_id for tracing calls
Nova: Update HostState.\*\_allocation_ratio earlier
Nova: WIP: Add a placement audit command
zun: [WIP] Use placement for unified resource management
neutron: Filter placement API endpoint by type too
OSA: Install placement osc plugin on utility machines
Kayobe: Build placement images by default
blazar: Fix placement operations in multi-region deployments
If you've done any performance or scale testing with placement, I'd
love to hear about your observations. Please let me know.
Chris Dent Ù©â??Ì¯â??Û¶ https://anticdent.org/