Bug 1042971 - [RFE][oslo]: Provide the toplevel OpenStack support for running on DB2
Summary: [RFE][oslo]: Provide the toplevel OpenStack support for running on DB2
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/oslo...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-13 16:49 UTC by RHOS Integration
Modified: 2015-03-19 17:36 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 17:36:53 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description RHOS Integration 2013-12-13 16:49:39 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/oslo/+spec/openstack-db2-support.

Description:

IBM needs to provide the high level support for OpenStack to run on DB2.  This doesn't require OSLO code changes but it was recommended by the Cinder PTL that changes to the database infrastructure first go through OSLO.  What is needed to satisfy this BluePrint is for IBM to provide the following to enable OpenStack on DB2:   Support in sqlalchemy and sqlalchemy-migrate to provide OpenStack access to DB2 databases.  IBM shall also add DB2-Express-C (freely available to the community) to the OpenStack Jenkins infrastructure.  Third party DB2 tests shall be provided for the testing infrastructure and IBM shall provide the hardware infrastructure to host the third party testing.  Finally, IBM shall provide BluePrints for all the OpenStack projects which have code changes to support DB2, shall implement the necessary code and appropriate unit test cases to support the newly developed code.  The BluePrints for the specific projects will be dependent upon the successful completion of this BluePrint.

Specification URL (additional information):

None


Note You need to log in before you can comment on or make changes to this bug.