Online schema migration

Registered by Grzegorz Grasza on 2015-11-12

Future incompatible changes in sqlalchemy migrations, like removing, renaming columns and tables can break rolling upgrades (upgrades when multiple Keystone instances are run at different versions).

To address this, we can ban schema changes which cause incompatibilities, specifically drops and alters, like in Nova:

https://github.com/openstack/nova/blob/stable/liberty/nova/tests/unit/db/test_migrations.py#L224-L225

Blueprint information

Status:
Complete
Approver:
Steve Martinelli
Priority:
Low
Drafter:
Grzegorz Grasza
Direction:
Approved
Assignee:
Grzegorz Grasza
Definition:
Approved
Series goal:
Accepted for newton
Implementation:
Implemented
Milestone target:
milestone icon newton-1
Started by
Steve Martinelli on 2016-06-20
Completed by
Steve Martinelli on 2016-06-20

Related branches

Sprints

Whiteboard

https://review.openstack.org/#/c/241603/

Gerrit topic: https://review.openstack.org/#q,topic:bug/1509944,n,z

Addressed by: https://review.openstack.org/241603
    Unit test for checking that migrations don't cause downtime

Gerrit topic: https://review.openstack.org/#q,topic:bp/online-schema-migration,n,z

Addressed by: https://review.openstack.org/245186
    Online schema migration

Addressed by: https://review.openstack.org/259153
    Shadow users: unified identity - data migration

Addressed by: https://review.openstack.org/265252
    Online schema migration documentation

Gerrit topic: https://review.openstack.org/#q,topic:bug/1524124,n,z

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.