Hi, I've implemented initial version of Ceph [1] cache store [2]. Cache entries

Hi, I've implemented initial version of Ceph [1] cache store [2]. Cache entries are stored into Ceph pools [3], one pool per cache if not configured otherwise. The cache store leverages librados [4] java binding for direct communication with Ceph cluster/RADOS (see e.g. Ceph architecture overview [5] for high-level understanding what is difference between accessing RADOS via RADOS gateway or POSIX file system client and librados). Would be there any interest in such cache store? If yes, any recommendations for improvements are welcome. Thanks Vojta [1] http://ceph.com/ [2] https://github.com/vjuranek/infinispan-cachestore-ceph [3] http://docs.ceph.com/docs/jewel/rados/operations/pools/ [4] http://docs.ceph.com/docs/hammer/rados/api/librados-intro/ [5] http://docs.ceph.com/docs/hammer/architecture/ _______________________________________________ infinispan-dev mailing list infinispan-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev

Hi Sebastian, sorry for late reply. > The only thing that comes into my mind is to test it with > Kubernetes/OpenShift Ceph volumes [6]. I'm not very familiar with k8s and its doc page doesn't provide any detail how it works under the hood, but AFAICT (looking on the source code [1]), it uses Ceph FS, not directly librados which is used by cache store, so IMHO there's not much to test. Single file store or soft index files store would be more appropriate to test with k8s Ceph volume. But what I'd like to do definitely in the future is some performance comparison between Ceph store using directly librados, cloud store using Ceph via RadosGW and single file store using Ceph via CephFS. Thanks Vojta [1] https://github.com/kubernetes/kubernetes/blob/master/pkg/ volume/cephfs/cephfs.go _______________________________________________ infinispan-dev mailing list infinispan-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev