+++ 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
I've been running almost exclusively with a postgresql backend for months without any problems w/ Quantum. I've primarily tested with devstack, though, so I'll do a quick check on RHOS as well.
I just tested quantum net/subnet/port/router create/delete commands on RHOS with a postgresql back end and had no issues.
It's good that it worked for you, but we also want QE to include this in their test plans and verify as part of QE runs. So we should move this bug to ON_QA and let QE move to VERIFIED later
Since packstack doesn't support postgres and we don't have Manuel steps to install it, I'm moving it back to ON_DEV until we have support for it
I am closing this RFE since I can't see any specific request for postgres support at this time. We will reopen this and consider QE testing if such a request will come. -Nir