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 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: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
