The details are buried in this advisory (search for Ceph): http://rhn.redhat.com/errata/RHSA-2013-1754.html My understanding is this is not in RHEL (the product), but is available in the RHEL platform code that RHEV and RHEL-OSP build on. Neil On Tue, Feb 4, 2014 at 9:59 AM, Karanbir Singh <mail-lists at karan.org> wrote: > hi Neil, > > On 02/04/2014 05:55 PM, Neil Levine wrote: > > The bulk of the Ceph packaging is server side only. The main component > > which creates the client dependencies is the librbd package, which can > > be held in other repos alongside specific versions of Xen, Qemu, KVM > > etc. With the RHEL-OSP/RHEV3.3-based code for qemu, there is explicit > > dynamic loading of the library too so it doesn't need to be at build > > time either so that might give more flexible around cloud repo code. > > > > ah, i didnt know we could ship qemu modules out like this, it might > change the whole problem space ( ie. who owns and manages this qemu ). > > -- > Karanbir Singh > +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh > GnuPG Key : http://www.karan.org/publickey.asc > _______________________________________________ > CentOS-devel mailing list > CentOS-devel at centos.org > http://lists.centos.org/mailman/listinfo/centos-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20140204/c9f0cfd6/attachment-0007.html>