On Wed, Feb 24, 2016 at 01:06:48PM -0500, Sage Weil wrote: > On Wed, 24 Feb 2016, Ken Dreyer wrote: > > I'm really interested in getting our various bundled libraries into > > separate packages. > > > > Does ceph's rocksdb have a lot of changes from rocksdb upstream? If > > so, I'm leaning towards packaging this as "ceph-rocksdb" until those > > changes are present in an upstream rocksdb release. > > There are a few that aren't upstream yet, but they'll merge eventually. > That said, I fully expect that we'll make other changes in the future that > we'll want to build/test/ship before they go upstream... so a special > package name probably makes sense. > > sage > > > > > > - Ken > > ... and I'm eliding what I posted originally to conserve electrons. When I looked at upstream rocksdb I couldn't find anything we had that they didn't have. I believe it should not be hard to work towards a target of using the unmodified distribution version in production environments. Looks like: * debian - has rocksdb (=4.1.0); appears to be very recent. Has no current packages that use rocksdb. There appear to be plans to use rocksdb with osquery. * ubuntu. Looks to be the identical state to debian, same maintainer. * fedora. No rocksdb currently. I think we could be the maintainer here, if we want. All this is going to be very distribution specific, involve maintainers, upstream, &etc. Still, this looks like it could be very tractable. What we do locally with "build/test/ship" is another matter entirely. I can see a world where the gitbuilders just install "our" rocksdb as another build dependency for ceph. Conceivably if we want to get fancy those gitbuilders (or others?) could also be building rocksdb (presumably from our repo), producing packages that after additional vetting (teuthology etc.) can be made available to the ceph git builders. The only real complexity I can see is it might be useful sometimes to steer different rocksdb packages towards different ceph branches. -Marcus Watts -- 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
