Skip to content

Latest commit

 

History

History
171 lines (131 loc) · 5.2 KB

README.md

File metadata and controls

171 lines (131 loc) · 5.2 KB
Raw

lustre-s3-copytool

A fork of this tool, called Estuary is now available for a better S3 support. Estuary is preferred for new deployment.

Features

  • Compression with LZ4
  • Stripping across multiple objects and buckets
  • Verifing checksum when restoring

Patching libs3

The copytool will segfault if libs3 is not patched, the fault mostly occur in large files restore (Writing on Lustre/Reading on S3).

This patch remove the low speed limit, that limit will normally cause a timeout if the transfer is slower than 1kb/s for 15 seconds.

$ git clone https://github.com/bji/libs3.git
$ cd libs3
$ patch -p1 < ~/lustre-obj-copytool/patches/libs3_low_speed_limit.patch

Building the copytool

After downloading the sources from the git repository, the autotools must be run to prepare the build environment :

$ aclocal
$ automake --add-missing
$ autoconf

The build can then be configured with the configure script. The location of the lustre source tree to compile against must be specified as well as the type of object interfaces to enable (s3 and/or rados):

$ ./configure --with-lustre=<location of lustre sources> --enable-s3

After running make, the binary of the copytool will be in ./src/

Configuration

General

Parameter Type Description
Chunk_size Int This represent the size of the largest object stored. A large file in Lustre will be stripped in multiple objects if the file size > chunk_size. Because compression is used, this parameter need to be set according to the available memory. Each thread will use twice the chunk_size. For incompressible data, each object will take a few extra bytes.

copytoolS3

A basic configuration is available in config.cfg.dist.s3, this file can be copied as config.cfg. The path of the config file can also be passed as a runtime parameter.

Parameter Type Description
access_key String AWS access key.
secret_key String AWS Secret key.
host String Hostname of the S3 endpoint.
bucket_count Int The number of buckets used to spread the indexing load. With radosgw, PUT operation will slow down proportionally to the number of objects in the same bucket. If a bucket_count > 2 is used, the bucket_prefix will be appended an ID.
bucket_prefix String This prefix will prepended to each bucketID. For example, if the bucket_prefix is hsm, then each bucket will named hsm_0, hsm_1, hsm_2 ...
ssl Bool If the S3 endpoint should use SSL.

copytoolRados

A basic configuration is available in config.cfg.dist.rados, this file can be copied as config.cfg. The path of the config file can also be passed as a runtime parameter.

Parameter Type Description
cluster_name String To select between multiple Ceph clusters
user_name String Select a key allowed to connect to the Ceph cluster and the HSM pool.
pool_name String A dedicated pool to store the objects created by HSM, can be erasure encoded.
config_file String Path to ceph.conf
chunk_size String A safe value used in Ceph RBD is 4MiB but it could be increased for this copytool.

Lustre HSM

Quick howto

Enable HSM on the MDS server

# lctl set_param mdt.lustre-MDT0000.hsm.max_requests=10
# lctl set_param mdt.lustre-MDT0000.hsm_control=enabled

Start the copytool on a DTN node

# ./copytoolS3 /lustre/
1456506103.926649 copytool_d[31507]: mount_point=/lustre/
1456506103.932785 copytool_d[31507]: waiting for message from kernel

You can use lfs hsm_state to get the current status of a file

Move a file to HSM and remove it from Lustre

# lfs hsm_state test
test: (0x00000000)
# lfs hsm_archive test
# lfs hsm_state
test: (0x00000009) exists archived, archive_id:1
# lfs hsm_release test
# lfs hsm_state test
test: (0x0000000d) released exists archived, archive_id:1

Restore the file implicitly

# md5sum test
33e3e3bdb7f6f847e06ae2a8abad0b85  test
# lfs hsm_state test
test: (0x00000009) exists archived, archive_id:1

Remove the file from S3

# lfs hsm_remove test
# lfs hsm_state test
test: (0x00000000), archive_id:1

Example with radosgw (S3)

Install radosgw as usual (http://docs.ceph.com/docs/master/radosgw/). The pool .rgw.buckets can be erasure coded.

Create the user used by HSM

# radosgw-admin user create --uid=lustre_hsm --display-name="lustre_hsm"
[...]
# radosgw-admin user modify --uid=lustre_hsm --max_buckets=10000
[...]

Grab the access_key and the secret_key from the previous command

Install and configure s3cmd (can also use any other s3 compatible tool)

Create some buckets with s3cmd

# for i in {0..256} ; do s3cmd mb s3://lustre_hsm_$i ; done
Bucket 's3://lustre_hsm_0/' created
[...]

Update the config.cfg

Start copytoolS3 Try it using the quick howto above

Example with rados (native ceph protocol)

Create a pool dedicated to the HSM storage, this can be a erasure coded pool.

# ceph osd pool create hsm 1024

Update the config.cfg

start copytoolRados

Try it using the quick howto above