[nova] [placement] [packaging] placement extraction check in meeting

Bal√°zs Gibizer balazs.gibizer at ericsson.com
Thu Jan 17 11:16:08 UTC 2019

On Wed, Jan 16, 2019 at 8:29 PM, Matt Riedemann <mriedemos at gmail.com> 
> Nested providers / reshaper / VGPU:
> * VGPU reshaper work for nested resource providers in libvirt and 
> xenapi drivers has stalled and there is still hesitation to move 
> forward with extracting placement before that reshape flow, including 
> in an upgrade, is tested to know that nova does not need any last 
> minute data migrations which require direct access to the placement 
> database. In other words, we have not yet confirmed that the 
> placement reshaper API will be fully sufficient until a real driver 
> is using it.
> * Matt (me!) has agreed to rebase and address the comments on the 
> libvirt patch [3] to try and push that forward.
> * We still need someone to write a functional test which creates a 
> server with a flat resource structure, reshapes that to nested, and 
> then creates another server against the same provider tree.

There is a functional test [1] that uses a fake virt driver and 
simulates rehape. My first attempt was to add an extra instance 
creation after the end of the reshape. But this test reshapes the 
provider tree to a way that the resulting tree uses sharing disk 
provider and doesn't have inventory on the compute node RP any more 
(cpu and mem moved under NUMA). Unfortunately nova does not yet support 
scheduling against such tree.

Shall I try to add a new functional test with the fake virt driver or 
try to add a functional test with the libvirt driver top of the VGPU 
reshaper patch?


[1] nova.tests.functional.test_servers.ProviderTreeTests#test_reshape

More information about the openstack-discuss mailing list