[placement] update 19-35
Here's placement update 19-36. There won't be one next week, I will
be away. Because of my forthcoming "less time available for
OpenStack" I will also be stopping these updates at some point in
the next month or so so I can focus the limited time I will have on
reviewing and coding. There will be at least one more.
# Most Important
The big news this week is that after returning from a trip (that
meant he was away during the nomination period) Tetsuro has stepped
up to be the PTL for placement in Ussuri. Thanks very much to him
for taking this up, I'm sure he will be excellent.
We need to work on useful documentation for the features developed
I've also made a [now
StoryBoard to draw attention to placement project stories that are
relevant to the next few weeks, making it easier to ignore those
that are not relevant now, but may be later.
(Numbers in () are the change since the last pupdate.)
There are 23 (-1) stories in [the placement
0 (0) are [untagged](https://storyboard.openstack.org/#!/worklist/580).
5 (0) are [bugs](https://storyboard.openstack.org/#!/worklist/574). 4 (0)
are [cleanups](https://storyboard.openstack.org/#!/worklist/575). 10
(-1) are [rfes](https://storyboard.openstack.org/#!/worklist/594).
5 (1) 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 (0).
* Placement related nova [in progress bugs](https://goo.gl/vzGGDQ) on
launchpad: 6 (0).
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 has some good comments on it from melwitt. I'm going to be
away next week, so if someone else would like to address them that
would be great. If it is deemed fit to merge, we should, despite
feature freeze passing, since we haven't had much churn lately. If
it doesn't make it in Train, that's fine too. The goal is to have
it ready for Nova in Ussuri as early as possible.
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:
Refactor initialization of research context. This puts the code
that might cause an exit earlier in the process so we can avoid
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.
These are the patches for meeting the build pdf docs goal for the
various placement projects.
# Other Placement
Miscellaneous changes can be found in [the usual
There are three [os-traits
being discussed. And two [os-resource-classes
The latter are docs-related.
# Other Service Users
New reviews are added to the end of the list. Reviews that haven't
had attention in a long time (boo!) or have merged or approved
(yay!) are removed.
helm: add placement chart
Nova: WIP: Add a placement audit command
tempest: Add placement API methods for testing routed provider nets
Nova: cross cell resize
Nova: Scheduler translate properties to traits
Nova: single pass instance info fetch in host manager
Nova: using provider config file for custom resource providers
Nova: clean up some lingering placement stuff
OSA: Add nova placement to placement migration
Charms: Disable nova placement API in Train
Nova: stop using @safe_connect in report client
Chris Dent Ù©â??Ì¯â??Û¶ https://anticdent.org/