Hi there,
We are providing Openstack based cloud solution to customers. We have read
the technical papers on Ceph, and our colleague
also consulted the comparision between Ceph and Swift from the ceph-user
mailing list. Given the advantages of Ceph over
Swift, such as scalability, performance and the all-in-one design, we wanna
replace swift with ceph in our openstack
solution. However, since the client applications are developed based on Swift
API, as far as we know, currently only a subset of
Swift API is implemented by Ceph. And furthermore, it seems to us that the S3
compatability owns a higher priority or done
earlier in Ceph, the Swift compatibility code is fixed with S3 code, and kind
of, yield to the S3 compatibility framework
and S3 semantics, which hamper us to add some Swift specific features into
Radosgw. And with the developing of Swift as
well as S3, we think the current framework will suffer from the code elegance
and larger API divergence. We do wanna use
Ceph and also wanna make technical contributions to it. We are considering to
revise the current framework to split the
Swift code with the S3 code, to allow a more friendly support to Swift API and
make it easier to add Swift specific
features, such as custom metadata, expiring object, negative acl rule, so what
is the Ceph community's response?
Cheers,
Li Wang
