This topic describes how to configure object storage on the Object Storage Gateway
(OSG) for the backend of your choice.
The OSG passes requests to object storage providers and talks to the persistence
layer (DB) to authenticate requests. You can use Walrus, Riak CS, or Ceph-RGW as the
object storage provider.
- Riak Cloud Storage (CS) - an open source scalable general purpose
data platform created by Basho Technologies. It is intended for deployments
which have heavy S3 usage requirements where a single-host system like
Walrus would not be able to serve the volume of operations and amount of
- Ceph Rados Gateway (RGW) - an object storage interface built on top
of Librados to provide applications with a RESTful gateway to Ceph Storage
Clusters. Ceph-RGW uses the Ceph Object Gateway daemon (radosgw), which is a
FastCGI module for interacting with a Ceph Storage Cluster. Since it
provides interfaces compatible with OpenStack Swift and Amazon S3, the Ceph
Object Gateway has its own user management. Ceph Object Gateway can store
data in the same Ceph Storage Cluster used to store data from Ceph
Filesystem clients or Ceph Block Device clients. The S3 and Swift APIs share
a common namespace, so you may write data with one API and retrieve it with
Note: Ceph RGW is a Controlled Availability feature. For information about Controlled Availability features in
Eucalyptus, see Special Status Release Features.
You must configure the OSG to use one of the backend provider options.
Note: If OSG has been registered but not yet properly configured, it will be listed in
the broken state when listed with the euserv-describe-services
command. For example:
[root@g-26-03 ~]# euserv-describe-services --show-headers --filter service-type=objectstorage
SERVICE TYPE ZONE NAME STATE
SERVICE objectstorage user-api-1 user-api-1.objectstorage broken