Index ¦ Archives ¦ Atom

Placement Update 19-35

Let's have a placement update 19-35. Feature freeze is this week. We have a feature in progress (consumer types, see below) but it is not critical.

Most Important

Three main things we should probably concern ourselves with in the immediate future:

  • We are currently without a PTL for Ussuri. There's some discussion about the options for dealing with this in an email thread. If you have ideas (or want to put yourself forward), please share.

  • We need to work on useful documentation for the features developed this cycle.

  • We need to create some cycle highlights. To help with that I've started an etherpad. If I've forgotten anything, please make additions.

What's Changed

  • osc-placement 1.7.0 has been released. This adds support for managing allocation ratios via aggregates, but adding a few different commands and args for inventory manipulation.

  • Work on consumer types exposed that placement needed to be first class in grenade to make sure database migrations are run. That change has merged. Until then placement was upgraded as part of nova.


(Numbers in () are the change since the last pupdate.)

There are 24 (-1) stories in the placement group. 0 (0) are untagged. 5 (0) are bugs. 4 (0) are cleanups. 11 (-1) are rfes. 4 (0) are docs.

If you're interested in helping out with placement, those stories are good places to look.


  • 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.

  • --amend and --aggregate on resource provider inventory has merged and been release 1.7.0 (see above).

Main Themes

Consumer Types

Adding a type to consumers will allow them to be grouped for various purposes, including quota accounting.


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.

Performance related explorations continue:

One outcome of the performance work needs to be something like a Deployment Considerations document to help people choose how to tweak their placement deployment to match their needs. The simple answer is use more web servers and more database servers, but that's often very wasteful.

Other Placement

Miscellaneous changes can be found in the usual place.

  • Merge request log and request id middlewares is worth attention. It makes sure that all log message from a single request use a global and local request id.

There are three os-traits changes being discussed. And zero os-resource-classes changes.

Other Service Users

This week (because of feature freeze) I will not be adding new finds to the list, just updating what was already on the list.



© Chris Dent. Built using Pelican. Theme by Giulio Fidente on github.