Track post-Diablo database evolution using migrations

Registered by Dolph Mathews on 2011-10-28

Schema & data migrations should be provided to ease the maintenance cost of running keystone in a production-quality environment.

Because we're using sqlalchemy as our ORM, implementing sqlalchemy-migrations (http://code.google.com/p/sqlalchemy-migrate/) is the obvious solution.

Addressed by https://review.openstack.org/#change,1200

Blueprint information

Status:
Complete
Approver:
Joe Savak
Priority:
Undefined
Drafter:
Dolph Mathews
Direction:
Approved
Assignee:
Dolph Mathews
Definition:
Approved
Series goal:
Accepted for essex
Implementation:
Implemented
Milestone target:
milestone icon 2012.1
Started by
Joe Savak on 2011-11-01
Completed by
Joe Savak on 2011-11-08

Related branches

Sprints

Whiteboard

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

Addressed by: https://review.openstack.org/1200
    Track post-Diablo database evolution using migrations (BP: database-migrations)

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.