CephObjectStorage
Last updated
Last updated
This guide describes how to configure Alluxio with Ceph Object Storage as the under storage system. Alluxio supports two different clients APIs to connect to using :
(preferred)
The Alluxio binaries must be on your machine. You can either , or .
A Ceph bucket can be mounted to Alluxio either at the root of the namespace, or at a nested directory.
Configure Alluxio to use under storage systems by modifying conf/alluxio-site.properties
. If it does not exist, create the configuration file from the template.
Modify conf/alluxio-site.properties
to include:
If using a Ceph release such as hammer (or older) specify alluxio.underfs.s3.signer.algorithm=S3SignerType
to use v2 S3 signatures. To use GET Bucket (List Objects) Version 1 specify alluxio.underfs.s3.list.objects.v1=true
.
Modify conf/alluxio-site.properties
to include:
Replace <bucket>/<folder>
with an existing Swift container location. Possible values of <swift-use-public>
are true
, false
. Specify <swift-auth-model>
as swiftauth
if using native Ceph RGW authentication and <swift-auth-url>
as http://<rgw-hostname>:<rgw-port>/auth/1.0
.
Issue the following command to use the S3 interface:
Similarly, to use the Swift interface:
Start up Alluxio locally to see that everything works.
Run a simple example program:
Visit your bucket to verify the files and directories created by Alluxio exist.
You should see files named like:
To stop Alluxio, run:
An Ceph location can be mounted at a nested directory in the Alluxio namespace to have unified access to multiple under storage systems. Alluxio's can be used for this purpose.
This should start an Alluxio master and an Alluxio worker. You can see the master UI at .
If Alluxio security is enabled, Alluxio enforces the access control inherited from underlying Ceph Object Storage. Depending on the interace used, refer to or for more information.