On Thu, Feb 4, 2016 at 8:12 PM, Armando M. <arma...@gmail.com> wrote: > Technically we can make this as sophisticated and seamless as we want, but > this is a one-off, once it's done the pain goes away, and we won't be doing > another migration like this ever again. So I wouldn't over engineer it.
Frankly, I was worried that going the other way was over-engineering it. It will be more difficult for us to manage this transition. I'm still struggling to see what makes this particular migration different than other cases where we change the database schema and the code a bit and we automatically migrate everyone to it as part of the routine migration. What is it about this case that necessitates giving the operator the option? Carl __________________________________________________________________________ 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
