[Openstack-operators] [all] SQL Schema Downgrades: A Good Idea?

Morgan Fainberg morgan.fainberg at gmail.com
Sun Feb 8 18:19:35 UTC 2015

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 Fainberg

On January 30, 2015 at 11:41:02 AM, Jesse Keating (jlk at 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.  


OpenStack-operators mailing list  
OpenStack-operators at lists.openstack.org  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20150208/3334ea76/attachment.html>

More information about the OpenStack-operators mailing list