Online schema migration
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:
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:
-
newton-1
- Started by
- Steve Martinelli
- Completed by
- Steve Martinelli
Related branches
Sprints
Whiteboard
https:/
Gerrit topic: https:/
Addressed by: https:/
Unit test for checking that migrations don't cause downtime
Gerrit topic: https:/
Addressed by: https:/
Online schema migration
Addressed by: https:/
Shadow users: unified identity - data migration
Addressed by: https:/
Online schema migration documentation
Gerrit topic: https:/
