Neutron DB Migration Refactor
Currently the neutron database schema is dependent on the neutron configuration. It differs depending on core plugin and services configured. This makes DB migrations not idempotent, as configurations can change between versions.
We need to make the database schema independent of configuration, and heal old versions to the independent schema after Icehouse.
Proposal:
- Include all tables (all service tables and all plugin tables) unconditionally from now on
- Provide a "healing" script and/or migration to convert an existing Icehouse DB to the new schema
Also:
- Improve Unit and Functional testing for migrations
Blueprint information
- Status:
- Complete
- Approver:
- Kyle Mestery
- Priority:
- Essential
- Drafter:
- Henry Gessau
- Direction:
- Approved
- Assignee:
- Henry Gessau
- Definition:
- Approved
- Series goal:
- Accepted for juno
- Implementation:
-
Implemented
- Milestone target:
-
2014.2
- Started by
- Kyle Mestery
- Completed by
- Kyle Mestery
Related branches
Related bugs
Sprints
Whiteboard
2-Jun (mestery): Picking Juno-2 as the target for this work.
Gerrit topic: https:/
Addressed by: https:/
WIP: Script
Addressed by: https:/
WIP: Add module providing icehouse models
Addressed by: https:/
WIP: Implement ModelsMigration
Addressed by: https:/
Move brocade db models to separate file
Addressed by: https:/
Move bigswitch db models to separate file
Addressed by: https:/
Move cisco db models to separate file
Addressed by: https:/
Move embrane db models to separate file
Addressed by: https:/
Move hyperv db models to separate file
Addressed by: https:/
Move linuxbridge db models to separate file
Addressed by: https:/
Move metaplugin db models to separate file
Addressed by: https:/
Move ml2 db models to separate file
