Add DB2 as an option for backend database
Current OpenStack supports multiple open source database as the backend database, for example: MySQL, SQLite, PostgreSQL are the default supported database for the community.
I plan to contribue changes to Nova to allow the use of DB2 as the backing database, and doing so will require me to:
1. Update Nova project to support DB2 initialization and access by updating the SQLALchemy-migrate code.
2. Run tempest on a DB2 installed environment
Blueprint information
- Status:
- Complete
- Approver:
- John Garbutt
- Priority:
- Low
- Drafter:
- Matt Riedemann
- Direction:
- Approved
- Assignee:
- Matt Riedemann
- Definition:
- Approved
- Series goal:
- Accepted for liberty
- Implementation:
-
Implemented
- Milestone target:
-
12.0.0
- Started by
- Matt Riedemann
- Completed by
- Matt Riedemann
Related branches
Related bugs
Sprints
Whiteboard
To be clear, I think publicly running CI using DB2 should be a requirement before this can be merged --russellb
Depends on sqlalchemy-migrate DB2 blueprint completion:
https:/
Gerrit topic: https:/
Addressed by: https:/
Use the utils code in the 212 migration script
Gerrit topic: https:/
Addressed by: https:/
DB2: Handle ibm_db_sa in modify_indexes
Addressed by: https:/
WIP: Add DB2 migration support
Gerrit topic: https:/
Currently blocked on getting CI running on this. --russellb
Unapproved - please re-submit via nova-spec --johnthetubagy (20th March 2014)
Removed from next, as next is now reserved for near misses from the last milestone --johnthetubaguyTo be clear, I think publicly running CI using DB2 should be a requirement before this can be merged --russellb
Depends on sqlalchemy-migrate DB2 blueprint completion:
https:/
Gerrit topic: https:/
Addressed by: https:/
Use the utils code in the 212 migration script
Gerrit topic: https:/
Addressed by: https:/
DB2: Handle ibm_db_sa in modify_indexes
Addressed by: https:/
WIP: Add DB2 migration support
Gerrit topic: https:/
Currently blocked on getting CI running on this. --russellb
Unapproved - please re-submit via nova-spec --johnthetubagy (20th March 2014)
Removed from next, as next is now reserved for near misses from the last milestone --johnthetubaguy
Marking this blueprint as definition: Drafting. If you are still working on this, please re-submit via nova-specs. If not, please mark as obsolete, and add a quick comment to describe why. --johnthetubaguy (20th April 2014)To be clear, I think publicly running CI using DB2 should be a requirement before this can be merged --russellb
Depends on sqlalchemy-migrate DB2 blueprint completion:
https:/
Gerrit topic: https:/
Addressed by: https:/
Use the utils code in the 212 migration script
Gerrit topic: https:/
Addressed by: https:/
DB2: Handle ibm_db_sa in modify_indexes
Addressed by: https:/
WIP: Add DB2 migration support
Gerrit topic: https:/
Currently blocked on getting CI running on this. --russellb
Unapproved - please re-submit via nova-spec --johnthetubagy (20th March 2014)
Removed from next, as next is now reserved for near misses from the last milestone --johnthetubaguyTo be clear, I think publicly running CI using DB2 should be a requirement before this can be merged --russellb
Depends on sqlalchemy-migrate DB2 blueprint completion:
https:/
Gerrit topic: https:/
Addressed by: https:/
Use the utils code in the 212 migration script
Gerrit topic: https:/
Addressed by: https:/
DB2: Handle ibm_db_sa in modify_indexes
Addressed by: https:/
WIP: Add DB2 migration support
Gerrit topic: https:/
Currently blocked on getting CI running on this. --russellb
Unapproved - please re-submit via nova-spec --johnthetubagy (20th March 2014)
Removed from next, as next is now reserved for near misses from the last milestone --johnthetubaguy
Marking this blueprint as definition: Drafting. If you are still working on this, please re-submit via nova-specs. If not, please mark as obsolete, and add a quick comment to describe why. --johnthetubaguy (20th April 2014)
Marking this blueprint as definition: Drafting. If you are still working on this, please re-submit via nova-specs. If not, please mark as obsolete, and add a quick comment to describe why. --johnthetubaguy (20th April 2014)
Addressed by: https:/
Add support for DB2 as a backend database
Addressed by: https:/
WIP: Enforce unique instance uuid in data model
Its not obvious all the code is actually ready for review here, please tidy up the list of patches before moving back to NeedsCodeReview. Not all the reviews have +2s and are not all are close to approval, so moving to juno-3. But please move this back to juno-2, should you get your patches approved in time. --johnthetubaguy 21st July 2014
Sorry, this does not have enough positive reviews to make it for juno-3, please resubmit for kilo. For more information, please contact me (johnthetubaguy) via IRC or email. --johnthetubaguy 2nd September 2014
Addressed by: https:/
WIP: Separate test for migration 266
Addressed by: https:/
(Re)Propose "Add DB2 as an option for backend database"
Addressed by: https:/
(Re)Propose "Add DB2 as an option for backend database"
Work Items
Work items:
Unit Tests: INPROGRESS
Migration Scripts: INPROGRESS
Sync oslo-incubator db.api changes: DONE
CI with Tempest: INPROGRESS
User Documentation: TODO
Dependency tree
* Blueprints in grey have been implemented.
