As a follow up on this topic, the specification for this change has been proposed to the openstack-specs (cross-project) specifications repository: https://review.openstack.org/#/c/152337/
Feedback from the operators would be greatly appreciated. —Morgan -- Morgan Fainberg On January 30, 2015 at 11:41:02 AM, Jesse Keating (j...@bluebox.net) wrote: On 1/30/15 11:37 AM, Tim Bell wrote: > Any ideas how are the online upgrade teams looking to address this ? Not an > easy problem to solve. The direction is additive migrations. Create new columns and tables for new place for the data, but support pulling data from old locations as well. Once all the consumers/producers can read the new table, background data migration starts. Eventually the old tables can be dropped, but that can be an admin action later. Expand / contract is the term being throw around for this. Of course, each project is tackling it on their own, and I'm mostly speaking about Nova. -- -jlk _______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
_______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
