RETIRED, further work has moved to Debian project infrastructure
Go to file
Tim Burke b958466a72 More port number cleanup
Closes-Bug: #1671896
Related-Change: Ie4fee05b5f7e0c0879a7b42973bca459f7c85408
Change-Id: I18db1937a0991497027a4d096fb95cdda81f7d68
2017-03-10 18:28:04 +00:00
api-ref/source More port number cleanup 2017-03-10 18:28:04 +00:00
bin Fix swift-get-nodes arg parsing for missing ring 2017-02-06 07:57:12 +00:00
doc Merge "Support EC policy for in process functional tests" 2017-03-10 04:38:12 +00:00
etc EC Fragment Duplication - Foundational Global EC Cluster Support 2017-02-22 10:56:13 -08:00
examples Add a user variable to templates 2013-09-17 11:46:04 +10:00
install-guide/source More port number cleanup 2017-03-10 18:28:04 +00:00
releasenotes 2.13.0 authors/changelog updates 2017-02-15 16:16:49 -08:00
swift Merge "Optimize ec duplication and its md5 hashing" 2017-03-09 21:55:56 +00:00
test Merge "Support EC policy for in process functional tests" 2017-03-10 04:38:12 +00:00
.alltests Apply bash error handling consistently in all bash scripts 2016-10-11 22:13:06 +02:00
.coveragerc Fix .coveragrc to prevent nose tests error 2015-09-21 10:06:29 +01:00
.functests Merge "Apply bash error handling consistently in all bash scripts" 2016-10-14 18:03:04 +00:00
.gitignore Add .eggs/* to .gitignore 2016-03-22 11:53:49 +00:00
.gitreview Add .gitreview config file for gerrit. 2011-10-24 15:05:49 -04:00
.mailmap Update .mailmap 2017-03-10 10:50:33 +00:00
.manpages Script for checking sanity of manpages 2016-02-10 14:16:56 -08:00
.probetests Allow specify arguments to .probetests script 2013-12-24 01:18:19 -08:00
.testr.conf Fix func test --until-failure and --no-discover options 2015-12-16 15:28:25 +00:00
.unittests Fix coverage report for newer versions of coverage 2014-04-24 16:50:03 +00:00
AUTHORS 2.13.0 authors/changelog updates 2017-02-15 16:16:49 -08:00
babel.cfg add pybabel setup.py commands and initial .pot 2011-01-27 00:01:24 +00:00
bandit.yaml Updating Bandit config file 2016-09-16 09:20:34 -07:00
bindep.txt fix bindep file to enable func test in centos 2017-02-28 15:54:53 -05:00
CHANGELOG Replace references to swift.openstack.org 2017-03-08 09:46:41 -06:00
CONTRIBUTING.rst Rework the contributor docs 2016-05-05 22:02:47 -07:00
LICENSE Convert LICENSE to use unix style line endings. 2012-12-19 12:48:27 -05:00
MANIFEST.in Fix locale directory in MANIFEST.in 2016-05-19 15:56:15 +02:00
README.rst Show team and repo badges on README 2016-11-25 16:36:49 +01:00
requirements.txt Update pyeclib dependency to 1.3.1 2016-10-06 11:22:26 -07:00
REVIEW_GUIDELINES.rst added a quote 2017-01-05 10:24:09 -08:00
setup.cfg Make Sphinx treat warnings as errors 2017-03-06 23:55:40 +00:00
setup.py taking the global reqs that we can 2014-05-21 09:37:22 -07:00
test-requirements.txt Make Sphinx treat warnings as errors 2017-03-06 23:55:40 +00:00
tox.ini Support EC policy for in process functional tests 2017-03-09 10:42:34 +00:00

Team and repository tags

image

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 http://docs.openstack.org/.

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 install sphinx (pip install sphinx), run python setup.py build_sphinx, and then browse to /doc/build/html/index.html. These docs are auto-generated after every commit and available online at http://docs.openstack.org/developer/swift/.

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.

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 http://docs.openstack.org/developer/swift/. A good starting point is at http://docs.openstack.org/developer/swift/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 http://github.com/openstack/python-swiftclient.

Complete API documentation at http://docs.openstack.org/api/openstack-object-storage/1.0/content/

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