openstack/nova
Code Issues Proposed changes

Nova db/api.py docstring cleanups...

Browse Source 
We no longer use LazyPluggable for the db_backend, and
dbapi_use_tpool options. These now come from
nova.openstack.common.db.api.

Also, removed doc about enable_new_services which seemed a bit
lonely without the rest and probably isn't needed since the
config option help explains it well enough.

Change-Id: I14d00e013a1a0c0dfc80e0bba8ad82e97940d6ac
This commit is contained in:
Dan Prince
2013-10-23 16:46:50 -04:00
parent 0c5ffc818b
commit a9e3784c1b
1 changed files with 0 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
nova/db/api.py
View File

@@ -19,8 +19,6 @@
"""Defines interface for DB access. """Defines interface for DB access.
The underlying driver is loaded as a :class:`LazyPluggable`.
Functions in this module are imported into the nova.db namespace. Call these Functions in this module are imported into the nova.db namespace. Call these
functions from nova.db namespace, not the nova.db.api namespace. functions from nova.db namespace, not the nova.db.api namespace.
@@ -29,18 +27,6 @@ interface. Currently, many of these objects are sqlalchemy objects that
implement a dictionary interface. However, a future goal is to have all of implement a dictionary interface. However, a future goal is to have all of
these objects be simple dictionaries. these objects be simple dictionaries.
**Related Flags**
:db_backend: string to lookup in the list of LazyPluggable backends.
`sqlalchemy` is the only supported backend right now.
:connection: string specifying the sqlalchemy connection to use, like:
`sqlite:///var/lib/nova/nova.sqlite`.
:enable_new_services: when adding a new service to the database, is it in the
pool of available hardware (Default: True)
""" """
from oslo.config import cfg from oslo.config import cfg