Re: [openstack-dev] [nova] What do we lose if the reshaper stuff doesn't land in Rocky?

2018-07-12 Thread Jay Pipes
DB work is now pushed for the single transaction reshape() function: https://review.openstack.org/#/c/582383 Note that in working on that, I uncovered a bug in AllocationList.delete_all() which needed to first be fixed: https://bugs.launchpad.net/nova/+bug/1781430 A fix has been pushed here:

Re: [openstack-dev] [nova] What do we lose if the reshaper stuff doesn't land in Rocky?

2018-07-12 Thread Jay Pipes
Let's just get the darn thing done in Rocky. I will have the DB work up for review today. -jay On 07/12/2018 10:45 AM, Matt Riedemann wrote: Continuing the discussion from the nova meeting today [1], I'm trying to figure out what the risk / benefit / contingency is if we don't get the reshape

[openstack-dev] [nova] What do we lose if the reshaper stuff doesn't land in Rocky?

2018-07-12 Thread Matt Riedemann
Continuing the discussion from the nova meeting today [1], I'm trying to figure out what the risk / benefit / contingency is if we don't get the reshaper stuff done in Rocky. In a nutshell, we need reshaper to migrate VGPU inventory for the libvirt and xenapi drivers from the root compute node