Deprecate db_driver config option
Previously this let you replace our SQLAlchemy database layer with your own. This approach is deprecated. Deployments that felt the need to use the facility are encourage to work with upstream Nova to address db driver concerns in the main SQLAlchemy code paths. Change-Id: If195a6bc399c8b1e2bfb0ea5579f2be21d0bc126
This commit is contained in:
parent
0fcec69a23
commit
c87ae92be5
@ -19,9 +19,16 @@
|
||||
from oslo_config import cfg
|
||||
from oslo_utils import importutils
|
||||
|
||||
db_driver_opt = cfg.StrOpt('db_driver',
|
||||
default='nova.db',
|
||||
help='The driver to use for database access')
|
||||
# NOTE(sdague): we know of at least 1 instance of out of tree usage
|
||||
# for this config in RAX. They used this because of performance issues
|
||||
# with some queries. We think the right path forward is fixing the
|
||||
# SQLA queries to be more performant for everyone.
|
||||
db_driver_opt = cfg.StrOpt(
|
||||
'db_driver',
|
||||
default='nova.db',
|
||||
help='DEPRECATED: The driver to use for database access',
|
||||
deprecated_for_removal=True)
|
||||
|
||||
|
||||
CONF = cfg.CONF
|
||||
CONF.register_opt(db_driver_opt)
|
||||
|
@ -0,0 +1,8 @@
|
||||
---
|
||||
deprecations:
|
||||
|
||||
- Deprecate the ``db_driver`` config option. Previously this let you
|
||||
replace our SQLAlchemy database layer with your own. This approach
|
||||
is deprecated. Deployments that felt the need to use the facility
|
||||
are encourage to work with upstream Nova to address db driver
|
||||
concerns in the main SQLAlchemy code paths.
|
Loading…
x
Reference in New Issue
Block a user