964869accc
mechanisim => mechanism
http://docs.openstack.org/developer/swift/cors.html
overridde => override
http://docs.openstack.org/developer/swift/deployment_guide.html
extentsions => extensions
http://docs.openstack.org/developer/swift/development_ondisk_backends.html
reuqest => request
http://docs.openstack.org/developer/swift/logs.html
suport => support
http://docs.openstack.org/developer/swift/overview_architecture.html
mininum => minimum
http://docs.openstack.org/developer/swift/overview_erasure_code.html
$ git diff | diffstat
cors.rst | 2 +-
deployment_guide.rst | 2 +-
development_ondisk_backends.rst | 2 +-
logs.rst | 2 +-
overview_architecture.rst | 2 +-
overview_erasure_code.rst | 2 +-
6 files changed, 6 insertions(+), 6 deletions(-)
Change-Id: I8e095f4c216b2cfae48dff1e17d387048349f73c
Closes-Bug: #1477877
1.4 KiB
Pluggable On-Disk Back-end APIs
The internal REST API used between the proxy server and the account, container and object server is almost identical to public Swift REST API, but with a few internal extensions (for example, update an account with a new container).
The pluggable back-end APIs for the three REST API servers (account, container, object) abstracts the needs for servicing the various REST APIs from the details of how data is laid out and stored on-disk.
The APIs are documented in the reference implementations for all three servers. For historical reasons, the object server backend reference implementation module is named diskfile, while the account and container server backend reference implementation modules are named appropriately.
This API is still under development and not yet finalized.
Back-end API for Account Server REST APIs
swift.account.backend
Back-end API for Container Server REST APIs
swift.container.backend
Back-end API for Object Server REST APIs
swift.obj.diskfile