Reserve database migrations for stable/icehouse backports

Registered by Dolph Mathews on 2014-01-30

Following the lead of Nova, keystone should "reserve" several migrations numbers in the master branch at the beginning of the Juno cycle for the purpose of backporting database migrations to stable/icehouse if necessary. This should remain true as long as we're using sqlalchemy-migrate instead of alembic.

On two occasions, keystone has sorely needed this functionality (most recently, https://review.openstack.org/#/c/69884/ ), although Nova has never taken advantage of the option (AFAIK).

Blueprint information

Status:
Complete
Approver:
None
Priority:
Low
Drafter:
Dolph Mathews
Direction:
Needs approval
Assignee:
Dolph Mathews
Definition:
New
Series goal:
Accepted for juno
Implementation:
Implemented
Milestone target:
milestone icon 2014.2
Started by
Dolph Mathews on 2014-01-30
Completed by
Dolph Mathews on 2014-06-04

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/reserved-db-migrations-icehouse,n,z

Addressed by: https://review.openstack.org/70153
    Add placeholders for reserved migrations

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.