[nova] FFU : When should we remove reshape support for a feature ?
sbauza at redhat.com
Tue Mar 31 14:49:28 UTC 2020
On Tue, Mar 31, 2020 at 4:43 PM Eric Fried <openstack at fried.cc> wrote:
> It may be worth taking into account that we had a work item to write a
> FFU hook for this, but it was never done.
OK, I already provided my thoughts for the virtual PTG etherpad in
I'll add those links and see whether I can volunteer for it in the next
> On 3/31/20 7:35 AM, Sylvain Bauza wrote:
> > Hola,
> > In Stein, I provided a new feature  that was checking inventories
> > from multiple children resource providers (RP). Since in Rocky, those
> > inventories were only on the root RP, I had to provide both :
> > #1 : an upgrade support for RPs that were not having a parent RP (that
> > was the case of Stein compute nodes) 
> > #2 : a reshape method in the libvirt driver for moving allocations
> > from a root RP to children RPs 
> > Now, we're in the Ussuri timeframe and as I was usually doing, I removed
> > the upgrade support (in #1) since we're 100% sure that all compute nodes
> > are either Train or Ussuri 
> > This is cool, but now the reshape code I wrote for #2 no longer works
> > (which is normal, since the 'non-Stein' support was removed) 
> > Soooooo. Can I also then remove the reshape support ? That would mean
> > that upgrading from Rocky to Train would work, but Rocky to Ussuri
> > wouldn't. I'm personally OK with this, but I guess other people could
> > have concerns with.
> > Do we have any consensus about how longer we would support a reshape ? I
> > think honestly that a 3-releases time window is enough but I can hear
> > some disagreements about this strawman proposal. If so, please voice.
> > -Sylvain
> >  https://blueprints.launchpad.net/nova/+spec/vgpu-stein
> >  https://review.opendev.org/#/c/636591/
> >  https://review.opendev.org/#/c/599208/
> >  https://review.opendev.org/#/c/715489/
> > 
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the openstack-discuss