OpenStack Storage (Swift)
Python
Permalink
Failed to load latest commit information.
api-ref/source improve prefix/delimiter api docs Aug 1, 2018
bin Merge "Experimental swift-ring-composer CLI to build composite rings" Jun 15, 2018
doc Merge "Update saio sample config files" Aug 13, 2018
etc Merge "Add keymaster to fetch root secret from KMIP service" Jul 25, 2018
examples display swift services in apache2 Mar 7, 2017
releasenotes Imported Translations from Zanata Aug 9, 2018
swift Merge "Stop holding on to sys.exc_info tuples quite so much" Aug 13, 2018
test Merge "Disallow uploads with x-amz-tagging headers set" Aug 11, 2018
tools Remove contentdir hack Jul 25, 2018
.alltests Apply bash error handling consistently in all bash scripts Oct 11, 2016
.coveragerc Show missing branches in coverage report. Dec 14, 2017
.functests Improved usage of args in .functests Feb 14, 2018
.gitignore Add some reno artifacts to .gitignore Jul 30, 2018
.gitreview Add .gitreview config file for gerrit. Oct 24, 2011
.mailmap authors/changelog update for 2.18.0 release May 29, 2018
.manpages Script for checking sanity of manpages Feb 10, 2016
.probetests Allow specify arguments to .probetests script Dec 24, 2013
.testr.conf Fix func test --until-failure and --no-discover options Dec 16, 2015
.unittests Fix coverage report for newer versions of coverage Apr 24, 2014
.zuul.yaml Add probetests to gate jobs Aug 6, 2018
AUTHORS authors/changelog update for 2.18.0 release May 29, 2018
CHANGELOG made changelog section breaks more consistent Jun 1, 2018
CONTRIBUTING.rst removed specific reference to two core reviewers May 30, 2018
LICENSE Convert LICENSE to use unix style line endings. Dec 19, 2012
MANIFEST.in Include s3api schemas in sdists Jul 11, 2018
README.rst Update doc building instructions in Development Guidelines Jul 6, 2018
REVIEW_GUIDELINES.rst added a quote Jan 5, 2017
babel.cfg add pybabel setup.py commands and initial .pot Jan 27, 2011
bandit.yaml Updating Bandit config file Sep 16, 2016
bindep.txt Add Alpine Linux suuprt to bindep Jul 5, 2018
lower-constraints.txt add lower-constraints job Jul 27, 2018
requirements.txt Lower the required version of ipaddress Jul 24, 2018
setup.cfg Add keymaster to fetch root secret from KMIP service Jul 3, 2018
setup.py taking the global reqs that we can May 21, 2014
test-requirements.txt Set lower bounds on all requirements and test-requirements Jun 15, 2018
tox.ini add lower-constraints job Jul 27, 2018

README.rst

Team and repository tags

Swift

A distributed object storage system designed to scale from a single machine to thousands of servers. Swift is optimized for multi-tenancy and high concurrency. Swift is ideal for backups, web and mobile content, and any other unstructured data that can grow without bound.

Swift provides a simple, REST-based API fully documented at https://docs.openstack.org/swift/latest/.

Swift was originally developed as the basis for Rackspace's Cloud Files and was open-sourced in 2010 as part of the OpenStack project. It has since grown to include contributions from many companies and has spawned a thriving ecosystem of 3rd party tools. Swift's contributors are listed in the AUTHORS file.

Docs

To build documentation run:

pip install -r requirements.txt -r doc/requirements.txt
sphinx-build -W -b html doc/source doc/build/html

and then browse to doc/build/html/index.html. These docs are auto-generated after every commit and available online at https://docs.openstack.org/swift/latest/.

For Developers

Getting Started

Swift is part of OpenStack and follows the code contribution, review, and testing processes common to all OpenStack projects.

If you would like to start contributing, check out these notes to help you get started.

The best place to get started is the "SAIO - Swift All In One". This document will walk you through setting up a development cluster of Swift in a VM. The SAIO environment is ideal for running small-scale tests against Swift and trying out new features and bug fixes.

Tests

There are three types of tests included in Swift's source tree.

  1. Unit tests
  2. Functional tests
  3. Probe tests

Unit tests check that small sections of the code behave properly. For example, a unit test may test a single function to ensure that various input gives the expected output. This validates that the code is correct and regressions are not introduced.

Functional tests check that the client API is working as expected. These can be run against any endpoint claiming to support the Swift API (although some tests require multiple accounts with different privilege levels). These are "black box" tests that ensure that client apps written against Swift will continue to work.

Probe tests are "white box" tests that validate the internal workings of a Swift cluster. They are written to work against the "SAIO - Swift All In One" dev environment. For example, a probe test may create an object, delete one replica, and ensure that the background consistency processes find and correct the error.

You can run unit tests with .unittests, functional tests with .functests, and probe tests with .probetests. There is an additional .alltests script that wraps the other three.

To fully run the tests, the target environment must use a filesystem that supports large xattrs. XFS is strongly recommended. For unit tests and in- process functional tests, either mount /tmp with XFS or provide another XFS filesystem via the TMPDIR environment variable. Without this setting, tests should still pass, but a very large number will be skipped.

Code Organization

  • bin/: Executable scripts that are the processes run by the deployer
  • doc/: Documentation
  • etc/: Sample config files
  • examples/: Config snippets used in the docs
  • swift/: Core code
    • account/: account server
    • cli/: code that backs some of the CLI tools in bin/
    • common/: code shared by different modules
      • middleware/: "standard", officially-supported middleware
      • ring/: code implementing Swift's ring
    • container/: container server
    • locale/: internationalization (translation) data
    • obj/: object server
    • proxy/: proxy server
  • test/: Unit, functional, and probe tests

Data Flow

Swift is a WSGI application and uses eventlet's WSGI server. After the processes are running, the entry point for new requests is the Application class in swift/proxy/server.py. From there, a controller is chosen, and the request is processed. The proxy may choose to forward the request to a back-end server. For example, the entry point for requests to the object server is the ObjectController class in swift/obj/server.py.

For Deployers

Deployer docs are also available at https://docs.openstack.org/swift/latest/. A good starting point is at https://docs.openstack.org/swift/latest/deployment_guide.html There is an ops runbook that gives information about how to diagnose and troubleshoot common issues when running a Swift cluster.

You can run functional tests against a Swift cluster with .functests. These functional tests require /etc/swift/test.conf to run. A sample config file can be found in this source tree in test/sample.conf.

For Client Apps

For client applications, official Python language bindings are provided at https://github.com/openstack/python-swiftclient.

Complete API documentation at https://developer.openstack.org/api-ref/object-store/

There is a large ecosystem of applications and libraries that support and work with OpenStack Swift. Several are listed on the associated projects page.


For more information come hang out in #openstack-swift on freenode.

Thanks,

The Swift Development Team