Hi, On Mon, 26 Dec 2016 19:25:29 +0000 Robin H. Johnson wrote: > On Mon, Dec 26, 2016 at 10:45:26AM +0300, Andrew Savchenko wrote: > > 8 packages are using either rbd or rados USE flag for Rados > > Block Device support: > RBD != RADOS.
Thanks for pointing this out. > RBD is the block-device-mapper on top of Ceph/RADOS. > > There are other pieces to put on top of Ceph, such as CephFS & RADOSGW > (S3/Swift access to RADOS) > > That said, I think at the growth of Ceph, we will have usage for both of > the USE flags. Then how about the following list for rbd: app-emulation/ganeti:rbd - Enable rados block device support via sys-cluster/ceph app-emulation/libvirt:rbd - Enable rados block device support via sys-cluster/ceph app-emulation/qemu:rbd - Enable rados block device backend support, see http://ceph.newdream.net/wiki/QEMU-RBD net-libs/xrootd:rbd - Enable rados block device support via sys-cluster/ceph sys-block/fio:rbd - Enable Rados block device support via sys-cluster/ceph sys-block/tgt:rbd - Add support for ceph block devices Also it seems that USE=rados is also invalid, because according to Ceph architecture [1] librados != rados and what these packages use is really librados: app-backup/bareos:rados - Enable rados storage backend net-analyzer/rrdtool:rados - Enable support for librados from sys-cluster/ceph So I propose to rename these USE flags to librados to be consistent. [1] http://docs.ceph.com/docs/master/architecture/ Looks like docs.ceph.com is down right now, so here is another copy: http://www.virtualtothecore.com/wp-content/uploads/2015/02/ceph-architecture-1.png Best regards, Andrew Savchenko
pgpfrCeeBI54m.pgp
Description: PGP signature
