On Thu, May 31, 2018 at 7:44 PM, Chris Dent <[email protected]> wrote:
> On Thu, 31 May 2018, Dan Smith wrote: > > I kinda think we need to either: >> >> 1. Make everything perform the pivot on compute node start (which can be >> re-used by a CLI tool for the offline case) >> > > This sounds effectively like: validate my inventory and allocations > at compute node start, correcting them as required (including the > kind of migration stuff related to nested). Is that right? > > That's something I'd like to be the norm. It takes us back to a sort > of self-healing compute node. > > Or am I missing something (forgive me, I've been on holiday). > I think I understand the same as you. And I think it's actually the best approach. Wow, Dan, you saved my life again. Should I call you Mitch Buchannon ? > > I just think that forcing people to take down their data plane to work >> around our own data model is kinda evil and something we should be >> avoiding at this level of project maturity. What we're really saying is >> "we know how to translate A into B, but we require you to move many GBs >> of data over the network and take some downtime because it's easier for >> *us* than making it seamless." >> > > If we can do it, I agree that being not evil is good. > > -- > Chris Dent ٩◔̯◔۶ https://anticdent.org/ > freenode: cdent tw: @anticdent > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
