HTML: https://anticdent.org/placement-update-18-43.html
A placement update for you.
# Most Important
Same as last week: The major factors that need attention are
managing database migrations and associated tooling and getting the
ball rolling on properly producing documentation. More on both of
these things in the extraction section below.
Matt has sent out [an
email](http://lists.openstack.org/pipermail/openstack-dev/2018-October/136075.html)
seeking volunteers from OpenStack Ansible or TripleO to get
placement upgrade tooling in one of those projects.
# Bugs
I guess it is because of various people doing upgrades, and some of
the downstream projects starting to take more advantage of
placement, but there's been a raft of interesting bugs recently.
Many related to some of the more esoteric aspects of the
ProviderTree handling in the resource tracker, the SQL in the
placement service, or management of global state in WSGI servers.
Initially this is a bit frustrating, but it's also a good thing:
Finding and fixing bugs is the beating heart of an open source
project. So thanks to everyone finding and fixing them.
* Placement related [bugs not yet in progress](https://goo.gl/TgiPXb): 15.
-1.
* [In progress placement bugs](https://goo.gl/vzGGDQ) 11.
# Specs
The spec review sprint happened and managed to get some specs
merged, so this list should have shrunk some.
* <https://review.openstack.org/#/c/544683/>
Account for host agg allocation ratio in placement
(Still in rocky/)
* <https://review.openstack.org/#/c/595236/>
Add subtree filter for GET /resource_providers
* <https://review.openstack.org/#/c/597601/>
Resource provider - request group mapping in allocation candidate
* <https://review.openstack.org/#/c/549067/>
VMware: place instances on resource pool
(still in rocky/)
* <https://review.openstack.org/#/c/555081/>
Standardize CPU resource tracking
* <https://review.openstack.org/#/c/599957/>
Allow overcommit of dedicated CPU
(Has an alternative which changes allocations to a float)
* <https://review.openstack.org/#/c/591037/>
Modelling passthrough devices for report to placement
* <https://review.openstack.org/#/c/603585/>
Spec: allocation candidates in tree
* <https://review.openstack.org/#/c/603805/>
[WIP] generic device discovery policy
* <https://review.openstack.org/#/c/603955/>
Nova Cyborg interaction specification.
* <https://review.openstack.org/#/c/601596/>
supporting virtual NVDIMM devices
* <https://review.openstack.org/#/c/603352/>
Spec: Support filtering by forbidden aggregate
* <https://review.openstack.org/#/c/552924/>
Proposes NUMA topology with RPs
* <https://review.openstack.org/#/c/569011/>
Count quota based on resource class
* <https://review.openstack.org/#/c/607989/>
WIP: High Precision Event Timer (HPET) on x86 guests
* <https://review.openstack.org/#/c/571111/>
Add support for emulated virtual TPM
* <https://review.openstack.org/#/c/141219/>
Adds spec for instance live resize
* <https://review.openstack.org/#/c/612497/>
Provider config YAML file
# Main Themes
## Making Nested Useful
Work on getting nova's use of nested resource providers happy and
fixing bugs discovered in placement in the process. This is creeping
ahead. We recently confirmed that end-to-end success with nested
providers is priority one for resource provider related work.
* <https://review.openstack.org/#/q/topic:bp/use-nested-allocation-candidates>
There's a topic for reshaper that still has some open patches:
* <https://review.openstack.org/#/q/topic:bp/reshape-provider-tree+status:open>
## Extraction
There continue to be three main tasks in regard to placement
extraction:
1. upgrade and integration testing
2. database schema migration and management
3. documentation publishing
There's been some good progress here. The [grenade job
works](https://review.openstack.org/#/c/604454/) and is ready to
merge independent of other things. The related [devstack
change](https://review.openstack.org/#/c/600162/) is still waiting
on the database management that's part of (2). As mentioned above,
volunteers from OSA or TripleO are being recruited.
That db management is making some good headway with a [working
alembic setup](https://review.openstack.org/#/c/611441/) but the
tooling to use it needs to be formalized. The [command line
hack](https://review.openstack.org/#/c/600161/) has been updated to
use the alembic setup.
We have work in progress to tune up the documentation but we are not
yet publishing documentation (3). The plan here is to incrementally
improve things as we have attention and discover things. One goal
with this is to keep the process moving and use followups to avoid
nitpicking each other too much.
# Other
Various placement changes out in the world.
* <https://review.openstack.org/#/c/601866/>
Generate sample policy in placement directory
(This is a bit stuck on not being sure what the right thing to do
is.)
* <https://review.openstack.org/#/q/topic:bp/initial-allocation-ratios>
Improve handling of default allocation ratios
*
<https://review.openstack.org/#/q/topic:minimum-bandwidth-allocation-placement-api>
Neutron minimum bandwidth implementation
* <https://review.openstack.org/#/c/602160/>
Add OWNERSHIP $SERVICE traits
* <https://review.openstack.org/#/c/604182/>
Puppet: Initial cookiecutter and import from nova::placement
* <https://review.openstack.org/#/c/586960/>
zun: Use placement for unified resource management
* <https://review.openstack.org/#/q/topic:bug/1799727>
Update allocation ratio when config changes
* <https://review.openstack.org/#/q/topic:bug/1799892>
Deal with root_id None in resource provider
* <https://review.openstack.org/#/q/topic:bug/1795992>
Use long rpc timeout in select_destinations
* <https://review.openstack.org/#/c/529343/>
Cleanups for scheduler code
* <https://review.openstack.org/#/q/topic:bp/bandwidth-resource-provider>
Bandwith Resource Providers!
* <https://review.openstack.org/#/q/topic:bug/1799246>
Harden placement init under wsgi
* <https://review.openstack.org/#/q/topic:cd/gabbi-tempest-job>
Using gabbi-tempest for integration tests.
* <https://review.openstack.org/#/c/613118/>
Make tox -ereleasenotes work
* <https://review.openstack.org/#/c/613343/>
placement: Add a doc describing a quick live environment
# End
It's tired around here.
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode: cdent tw: @anticdent
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
