Reset DB migrations

Bug #1072949 reported by Angus Salkeld
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat
Grizzly
Fix Released
High
Zane Bitter

Bug Description

The database schema has been undergoing rapid evolution in the early stages of the project. Once the database and API are relatively stable, we should remove the current database schema migrations and start from scratch. This would require deletion and re-creation of database contents, but some of our current migrations already require an empty database anyway. This would be a breaking change, but from that point onwards we should support full migration of data across schema upgrades.

We should wait for the completion of the transition to per-tenant (rather than per-user) management of stacks and final resolution of how HA should authenticate with nova before making this change.

sdake
=====
Agree. Work should hold until we sort out how the metadata server should change as well.

Angus Salkeld (asalkeld)
Changed in heat:
status: New → Triaged
importance: Undecided → Low
Steven Dake (sdake)
Changed in heat:
milestone: none → grizzly-3
Steven Dake (sdake)
no longer affects: heat
Revision history for this message
Zane Bitter (zaneb) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.