Support multiple SQL migration repos

Registered by Adam Young on 2013-05-22

SQL Migrations are currently served out of a single repo that lives in keystone/common/sql/migrate_repo. Plugins that are not core should not be modifying this repo, but should instead have their own repos, and should have no SQL constraints on tables defined in other repos.

The table migrate_version in the database has a column for the repo, which is the path to where the migrations live.

Each of the plugins needs to advertise to the CLI that it has database migrations to perform. Then running keystone-manage db_sync will migrate all of the registered repos.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Low
Drafter:
Adam Young
Direction:
Needs approval
Assignee:
Adam Young
Definition:
New
Series goal:
Accepted for havana
Implementation:
Implemented
Milestone target:
milestone icon 2013.2
Started by
Dolph Mathews on 2013-08-06
Completed by
Dolph Mathews on 2013-08-18

Related branches

Sprints

Whiteboard

What about parts that aren't referenced in the config file other than paste middleware? I think the ec2 tokens might work this way.

Gerrit topic: https://review.openstack.org/#q,topic:bp/multiple-sql-migrate-repos,n,z

Addressed by: https://review.openstack.org/36731
    extension migrations

Addressed by: https://review.openstack.org/36371
    Register Extensions

Gerrit topic: https://review.openstack.org/#q,topic:kds-multi-repo,n,z

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.