On Thu, Jan 24, 2013 at 9:45 AM, Dimitri Maziuk <dmaziuk@xxxxxxxxxxxxx> wrote: > > One other question I have left (so far) is: I read and tried to follow > http://ceph.com/docs/master/install/rpm/ and > http://ceph.com/docs/master/start/quick-start/ on centos 6.3. > > mkcephfs step fails without rbd kernel module. > > I just tried to find "libvirt", "kernel", "module", and "qemu" on those > pages: "kernel" occurs in "add ceph packages" section and "module" occurs in > the header, footer, and the side menu. 0 hits for the others. > > So when I read "after learning that qemu uses librbd (and thus doesn't rely > on the rbd kernel module) I was happy to stick with the stock CentOS kernel > for my servers (with updated qemu and libvirt builds)" -- forgive me for > being dense, but I have no context for this. Where in ceph.conf do I tell it > to use qemu and librbd instead of kernel module? Or does it mean I'm to set > up my OSDs in virtual machines? Seems I'm missing an important piece of > information here (possibly because it's blatantly obvious and is staring me > in the face -- woudn't be the first time). > > So what is it that I'm missing? Setting up ceph is separate from setting up qemu to use librbd. That's why the instructions at http://ceph.com/docs/master/rbd/rbd-openstack/ say you need to have your ceph cluster already running. You can just setup ceph without any specific config parameters for qemu or librbd, and then follow the instructions there to get librbd working with openstack. Because librbd runs in userspace, you don't need the rbd kernel module, or a modified kernel, so the stock centos kernel (or another distro's kernel) should work for you. Does that make sense? -sam > > TIA > Dima > > > -- > 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 -- 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
