On Fri, May 17, 2019 at 12:24 AM Milind Changire <mchangir@xxxxxxxxxx> wrote: > > The idea is to use sqlite3 to work around the disk size constraint for > individual objects and/or their attributes (key-value pairs) so that > the Ceph implementation can manage/stripe the underlying data blocks > across OSDs seamlessly. > > The implementation would be an sqlite3 VFS back-end interface to Ceph. > eg. metadata server (MDS) could create an sqlite3 database using this > new back-end to manage objects spread across OSDs > > So, do I use the RadosStriper or the Filer class for the implementation ? > > Or, do I need to tweak current implementation of some class(es) to get > the desired functionality in place to be used in the sqite3 VFS > interface implementation. It's not clear to me exactly what functionality you're looking for to plug into the sqlite backend. I will say that the Filer, messy though it can be, is used extensively by CephFS and by the RBD mirroring functionality, whereas RadosStriper was contributed (from CERN?) as part of a specific "lite rados FS" concept and is mostly orphaned AFAIK. IIRC the RadosStriper may also go to some effort to try and keep the striping objects consistent across multiple accessors, whereas the Filer assumes a higher layer is dealing with that. -Greg > > -- > Milind
