Split backends off swift/common/db.py

Code Issues Proposed changes

The main purpose of this patch is to lay the groundwork for allowing
the container and account servers to optionally use pluggable backend
implementations. The backend.py files will eventually be the module
where the backend APIs are defined via docstrings of this reference
implementation. The swift/common/db.py module will remain an internal
module used by the reference implementation.
We have a raft of changes to docstrings staged for later, but this
patch takes care to relocate ContainerBroker and AccountBroker into
their new home intact.
Change-Id: Ibab5c7605860ab768c8aa5a3161a705705689b04

This commit is contained in:

Pete Zaitcev

2013年09月10日 13:30:28 -06:00

parent 21c322c35d

commit d4b024ad7d

18 changed files with 2699 additions and 2572 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

16
doc/source/backends.rst Normal file

View File

@@ -0,0 +1,16 @@

======================================

Pluggable Back-ends: API Documentation

======================================

.. automodule:: swift.account.backend

:private-members:

:members:

:undoc-members:

.. automodule:: swift.container.backend

:private-members:

:members:

:undoc-members:

.. automodule:: swift.obj.diskfile

:members:

1
doc/source/index.rst

View File

@@ -66,6 +66,7 @@ Developer Documentation

development_guidelines

development_saio

development_auth

backends

Administrator Documentation

===========================