HTML: https://anticdent.org/placement-update-19-14.html Placement update 19-14 is here. There will be no 15, 16 or 17 due to various bits of travel. There will be some PTG-related summaries. # Most Important The [Virtual Pre-PTG](http://lists.openstack.org/pipermail/openstack-discuss/2019-March/004225.htm...) is in full swing and making some good progress towards making sure that we only hit the hard stuff at the in-person PTG. Apologies if it has been a bit overwhelming. The hope is that by paying the price of a bit more whelm now we will have less whelm at the PTG. If you have questions, please ask. Links to all the threads are in the PTG etherpads: * <https://etherpad.openstack.org/p/placement-ptg-train> * <https://etherpad.openstack.org/p/ptg-train-xproj-nova-placement> There's also a [retrospective etherpad](https://etherpad.openstack.org/p/placement-ptg-train-retrospective). # What's Changed * The [0.12.0 release of os-traits](https://review.openstack.org/652079) is pending. It switches that package to using the independent release policy. os-resource-classes will get the same treatment when we next need to release it. # Specs/Features There are four specs in flight in the placement repo and one pending to be ported over from nova: * <https://review.openstack.org/649992> support any trait in allocation candidates * <https://review.openstack.org/649368> support mixing required traits with any traits * <https://review.openstack.org/650476> Allocation Candidates: Subtree Affinity. There's discussion related to this happening in [email](http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004782.htm...) as part of the pre-PTG. * <https://review.openstack.org/651113> Support filtering by multiple trees. * <https://review.openstack.org/597601> Request group mapping spec is still in Nova, but discussion is happening in [email](http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004819.htm...) generating a plan for how to proceed. There are also several nova-specs that were visited in the [nova spec review day](http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004484.htm...) earlier this week. Some are listed below. # Bugs * StoryBoard stories in [the placement group](https://storyboard.openstack.org/#!/project_group/placement): 15. Up by 9. 0 are [untagged](https://storyboard.openstack.org/#!/worklist/580). Part of the reason for the increase is because Matt did the fine work of moving osc-placement bugs over from launchpad. * Placement related [bugs not yet in progress](https://goo.gl/TgiPXb) on launchpad: 13. No change. * [In progress placement bugs](https://goo.gl/vzGGDQ) on launchpad: 4. -1. Those that remain are placement-related, but in nova. # osc-placement osc-placement is currently behind by 13^w11 microversions. -1 since last week. Support for 1.19 has just merged. Oh wait, no, -3. 1.21 has just merged. There was nothing to do for 1.20. Pending changes: * <https://review.openstack.org/#/c/640898/> Add 'resource provider inventory update' command (that helps with aggregate allocation ratios). * <https://review.openstack.org/#/c/651783/> Add support for 1.22 microversion * <https://review.openstack.org/586056> Provide a useful message in the case of 500-error * <https://review.openstack.org/650257> Remove unused cruft from doc and releasenotes config * <https://review.openstack.org/652100> Improve aggregate version check error messages with min_version * <https://review.openstack.org/651939> Use PlacementFixture in functional tests. Result of discussion in [email](http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004731.htm...) in the pre-PTG # Main Themes More work remains in the pre-PTG discussions to try to drive towards some themes. The specs above capture some of it, but it appears like a lot of the work will be a) supporting other projects doing things with Placement, b) fixing bugs they discover. # Other Placement Mostly specs in progress (listed above) for now. * <https://review.openstack.org/#/c/645255/> This is a start at unit tests for the PlacementFixture. It is proving a bit "fun" to get right, as there are many layers involved. Making sure seemingly unrelated changes in placement don't break the nova gate is important. Besides these unit tests, there's discussion on the PTG etherpad of running the nova functional tests, or a subset thereof, in placement's check run. On the one hand this is a pain and messy, but on the other consider what we're enabling: Functional tests that use the real functionality of an external service (real data, real web requests), not stubs or fakes. There's a pre-PTG [thread](http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004880.htm...) for this. * <https://review.openstack.org/641404> Use ``code`` role in api-ref titles * <https://review.openstack.org/#/q/topic:refactor-classmethod-diaf> A sequence of refactorings, based off discussion in yet another pre-PTG [thread](http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004722.htm...). # Other Service Users New discoveries are added to the end. Merged stuff is removed. * <https://review.openstack.org/552924> Nova: Spec: Proposes NUMA topology with RPs * <https://review.openstack.org/622893> Nova: Spec: Virtual persistent memory libvirt driver implementation * <https://review.openstack.org/641899> Nova: Check compute_node existence in when nova-compute reports info to placement * <https://review.openstack.org/601596> Nova: spec: support virtual persistent memory * <https://review.openstack.org/#/q/topic:bug/1790204> Workaround doubling allocations on resize * <https://review.openstack.org/555081> Nova: Spec: Standardize CPU resource tracking * <https://review.openstack.org/645316> Nova: Pre-filter hosts based on multiattach volume support * <https://review.openstack.org/606199> Ironic: A fresh way of looking at step retrieval * <https://review.openstack.org/647396> Nova: Add flavor to requested_resources in RequestSpec * <https://review.openstack.org/633204> Blazar: Retry on inventory update conflict * <https://review.openstack.org/640080> Nova: Use aggregate_add_host in nova-manage * <https://review.openstack.org/#/q/topic:bp/count-quota-usage-from-placement> Nova: count quota usage from placement * <https://review.openstack.org/#/q/topic:bug/1819923> Nova: nova-manage: heal port allocations * <https://review.openstack.org/624335> puppet-tripleo: Initial extraction of the Placement service from Nova * <https://review.openstack.org/648665> Nova: Spec for a new nova virt driver to manage an RSD * <https://review.openstack.org/#/c/642067/> Helm: Allow more generic overrides for nova placement-api * <https://review.openstack.org/609960> Support filtering of allocation_candidates by forbidden aggregates * <https://review.openstack.org/625284> Cyborg: Initial readme for nova pilot * <https://review.openstack.org/629142> Tempest: Add QoS policies and minimum bandwidth rule client * <https://review.openstack.org/641994> Nova-spec: Re-approve AMD SEV support for Train * <https://review.openstack.org/648687> Nova-spec: Add PENDING vm state * <https://review.openstack.org/#/q/topic:bug/1777591> Nova: use in_tree in RequestGroup * <https://review.openstack.org/650856> kolla-ansible: Remove placement migration code * <https://review.openstack.org/650188> nova-spec: Allow compute nodes to use DISK_GB from shared storage RP * <https://review.openstack.org/651024> nova-spec: RMD Plugin: Energy Efficiency using CPU Core P-State control * <https://review.openstack.org/651455> puppet: Debian: Add support for placement-api over uwsgi * <https://review.openstack.org/650963> nova-spec: Proposes NUMA affinity for vGPUs. This describes a legacy way of doing things because affinity in placement may be a ways off. But it also [may not be](https://review.openstack.org/650476). * <https://review.openstack.org/649882> nova-spec: Separate the vCPUs into different pools based on priority * <https://review.openstack.org/#/q/topic:heal_allocations_dry_run> Nova: heal allocations, --dry-run * <https://review.openstack.org/642527> Neutron: Fullstack test for placement sync # End There's a lot going on. -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent