Bug 1042971

Summary:	[RFE][oslo]: Provide the toplevel OpenStack support for running on DB2
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	RFEs	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	markmc, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/oslo/+spec/openstack-db2-support
Whiteboard:	upstream_milestone_none upstream_status_unknown upstream_definition_new
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-19 17:36:53 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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