Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 890182

Summary:	postgres support for database - nova
Product:	Red Hat OpenStack	Reporter:	Perry Myers <pmyers>
Component:	openstack-nova	Assignee:	David Ripton <dripton>
Status:	CLOSED NOTABUG	QA Contact:	Gabriel Szasz <gszasz>
Severity:	low	Docs Contact:
Priority:	low
Version:	1.0 (Essex)	CC:	ajeain, apevec, kchamart, markmc, nobody, ohochman, sgordon, tvvcox
Target Milestone:	ga	Keywords:	FutureFeature, TestOnly, Triaged
Target Release:	5.0 (RHEL 7)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:	816316	Environment:
Last Closed:	2014-01-21 17:21:25 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	816316

Description Perry Myers 2012-12-25 15:07:25 UTC

+++ This bug was initially created as a clone of Bug #816316 +++

Description of problem:
Presently upstream OpenStack primarily utilizes mysql for its database.  We'd like to expand this to include postgres in addition.  There are probably some integration issues/small problems with running Postgres w/ Essex today, and these bugs will need to be tracked and individually resolved separately.

This bug is specifically for tracking the overall support of Postgres, and as such is a TestOnly bug.

--- Additional comment from Perry Myers on 2012-04-25 15:14:39 EDT ---

Related bugs:
https://bugs.launchpad.net/glance/+bug/953159
https://bugs.launchpad.net/glance/+bugs?field.tag=postgresql

--- Additional comment from Alan Pevec on 2012-12-13 14:33:21 EST ---

Dan, how well does Folsom work with PostgreSQL?
Any blocking issues preventing us fully support postgres for RHOS 2.1 GA?

Comment 1 Kashyap Chamarthy 2013-03-15 10:45:02 UTC

Any update here ? It's been a while.

Comment 2 David Ripton 2013-03-15 13:09:58 UTC

We use SQLAlchemy as a DB portability layer.  We run the upstream devstack-gate test suite using postgres for every proposed commit, and the code isn't allowed in until it passes.  And whenever someone proposes doing something MySQL-specific, we make sure there's a fallback path for postgres.

So I think postgres support is in pretty good shape right now.  That said, there may be edge cases that nobody has thought to test.