api-ref
bin
doc
manpages
s3api
saio
source
_extra
admin
figures
index.rst
objectstorage-EC.rst
objectstorage-account-reaper.rst
objectstorage-admin.rst
objectstorage-arch.rst
objectstorage-auditors.rst
objectstorage-characteristics.rst
objectstorage-components.rst
objectstorage-features.rst
objectstorage-intro.rst
objectstorage-large-objects.rst
objectstorage-monitoring.rst
objectstorage-replication.rst
objectstorage-ringbuilder.rst
objectstorage-tenant-specific-image-storage.rst
objectstorage-troubleshoot.rst
api
images
install
ops_runbook
account.rst
admin_guide.rst
apache_deployment_guide.rst
associated_projects.rst
conf.py
container.rst
cors.rst
crossdomain.rst
db.rst
deployment_guide.rst
development_auth.rst
development_guidelines.rst
development_middleware.rst
development_ondisk_backends.rst
development_saio.rst
first_contribution_swift.rst
getting_started.rst
howto_installmultinode.rst
index.rst
logs.rst
middleware.rst
misc.rst
object.rst
overview_acl.rst
overview_architecture.rst
overview_auth.rst
overview_backing_store.rst
overview_container_sharding.rst
overview_container_sync.rst
overview_encryption.rst
overview_erasure_code.rst
overview_expiring_objects.rst
overview_global_cluster.rst
overview_large_objects.rst
overview_policies.rst
overview_reaper.rst
overview_replication.rst
overview_ring.rst
policies_saio.rst
proxy.rst
ratelimit.rst
replication_network.rst
ring.rst
ring_background.rst
ring_partpower.rst
s3_compat.rst
test-cors.html
requirements.txt
docker
etc
examples
releasenotes
roles
swift
test
tools
.alltests
.coveragerc
.dockerignore
.functests
.gitignore
.gitreview
.mailmap
.manpages
.probetests
.testr.conf
.unittests
.zuul.yaml
AUTHORS
CHANGELOG
CONTRIBUTING.rst
Dockerfile
Dockerfile-py3
LICENSE
MANIFEST.in
README.rst
REVIEW_GUIDELINES.rst
babel.cfg
bandit.yaml
bindep.txt
lower-constraints.txt
py2-constraints.txt
requirements.txt
setup.cfg
setup.py
test-requirements.txt
tox.ini
24 lines
1.2 KiB
ReStructuredText
24 lines
1.2 KiB
ReStructuredText
![]() |
==============================
|
||
|
Introduction to Object Storage
|
||
|
==============================
|
||
|
|
||
|
OpenStack Object Storage (swift) is used for redundant, scalable data
|
||
|
storage using clusters of standardized servers to store petabytes of
|
||
|
accessible data. It is a long-term storage system for large amounts of
|
||
|
static data which can be retrieved and updated. Object Storage uses a
|
||
|
distributed architecture
|
||
|
with no central point of control, providing greater scalability,
|
||
|
redundancy, and permanence. Objects are written to multiple hardware
|
||
|
devices, with the OpenStack software responsible for ensuring data
|
||
|
replication and integrity across the cluster. Storage clusters scale
|
||
|
horizontally by adding new nodes. Should a node fail, OpenStack works to
|
||
|
replicate its content from other active nodes. Because OpenStack uses
|
||
|
software logic to ensure data replication and distribution across
|
||
|
different devices, inexpensive commodity hard drives and servers can be
|
||
|
used in lieu of more expensive equipment.
|
||
|
|
||
|
Object Storage is ideal for cost effective, scale-out storage. It
|
||
|
provides a fully distributed, API-accessible storage platform that can
|
||
|
be integrated directly into applications or used for backup, archiving,
|
||
|
and data retention.
|