Scality offers a software-based storage solution that provides great performance across content distribution and other media workloads.

Standard storage interfaces for files and objects like NFS, HTTP, SCP, and OpenStack enable applications to run without modification.

In the following section shows how to work with the HTTP interface, similar to S3/Azure/GCE as described above.

Scality RING supports the standard HTTP commands as well as range requests.

Available commands are:

Command Description
PUT Write or update an object, providing data, and optionally, metadata.
HEAD Retrieves object metadata only.
GET Retrieves the contents and metadata of an object.
DELETE Sent to delete an object on the Ring.


An example with tears-of-steel from Verify Your Setup looks like the following:

PUT the content:


curl -v -XPUT -H "Expect:" \
  --data-binary @tears-of-steel/tears-of-steel.ism \

Similar to the Azure Storage, files have to be copied individually to their location.

GET the content:


curl -v http://localhost:81/proxy/mychord/tears-of-steel/tears-of-steel.ism

Once the content is copied to the RING it can be accessed by the origin just like with S3, Azure or GCE.

The configuration of the origin is similar (this assumes RING listening on localhost port 81):

<Location "/">
  UspHandleIsm on
  UspEnableSubreq on
  IsmProxyPass http://localhost:81/proxy/mychord/

<Proxy "http://localhost:81/proxy/mychord">
  ProxySet connectiontimeout=5 enablereuse=on keepalive=on retry=0 timeout=30 ttl=300

The URL to the content then becomes the following, for instance for MPEG-DASH:

where is the webserver running USP and has the previous vhost snippet (and the tears-of-steel content in 'your-bucket' used with both IsmProxPass and Proxy directives.


In this case access to Scality RING has been setup as a proxy on localhost with port 81. This will be explained in the Scality documentation and is not part the Unified documentation.