Hi,
When we are evaluating migrating object storage cluster from swift
to ceph, all technical stuff goes fine except swift middleware. To be
honest swift middleware (and WSGI Pipeline) provide lots of
flexibility and easy customization to enterprise user, we have some
home made middleware together with some from community. Now the
challenge for me is how to migrate such customization into ceph.
One straightforward approach is re-implement such middleware
directly inside RGW code, but this is the least desire approach as we
need to maintain and build our own RGW package every new ceph release,
including own QA infrastructure.
Second approach is having a swift-to-rgw WSGI-proxy for RGW, it
was discussed in ML 2 years ago
(http://permalink.gmane.org/gmane.comp.file-systems.ceph.devel/24320)
and POC code implementation on (https://github.com/rzarzynski/rgwift).
It doesn't attract too much attention but I would like to reraise it,
see if it is the way we want to go. Pros on this approach is
simplicity , user doesn't need to re-write existing logical in swift
middleware, and the swift API is not changing actively so it is not
too burden for community to maintain such WSGI proxy. Cons including
deployment complexity.
Third one, could we have similar extension mechanism for RGW?
Would be nice if we can have customizable pipeline but some hook on
certain stage (pre-access, core-rgw, post-access) could also be a good
start ?
Xiaoxi
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
