Re: [ceph-users] Red Hat clients
On 10/30/2013 02:35 PM, Gruher, Joseph R wrote: > I have CentOS 6.4 running with the 3.11.6 kernel from elrepo and it includes the rbd module. I think you could make the same update on RHEL 6.4 and get rbd. Mmm... I think RHEL means "paid support" means you can't run an elrepo kernel. Plus I didn't have much luck with their -ml kernels (also centos 6.current) -- half of them wouldn't boot on our supermicros and the latest crop won't boot on my dell pc. So yeah, if by RHEL you mean centos/scilinux and you find an -ml kernel that actually works on your hardware... then you get rbd. As long as you don't 'yum update' the kernel. -- Dimitri Maziuk Programmer/sysadmin BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu signature.asc Description: OpenPGP digital signature ___ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
Re: [ceph-users] Red Hat clients
I have CentOS 6.4 running with the 3.11.6 kernel from elrepo and it includes the rbd module. I think you could make the same update on RHEL 6.4 and get rbd. From there it is very simple to mount an rbd device. Here are a few notes on what I did. Update kernel: sudo rpm --import http://elrepo.org/RPM-GPG-KEY-elrepo.org sudo rpm -Uvh http://elrepo.org/elrepo-release-6-5.el6.elrepo.noarch.rpm sudo yum -y update sudo yum -y --enablerepo=elrepo-kernel install kernel-ml sudo vim /boot/grub/menu.lst (update default to zero) reboot Create rbd device: rbd create {name} --size {size_in_MB} sudo modprobe rbd sudo rbd map {name} --pool {pool_name} Device appears at /dev/rbd/rbd/name From: ceph-users-boun...@lists.ceph.com [mailto:ceph-users-boun...@lists.ceph.com] On Behalf Of alistair.whit...@barclays.com Sent: Wednesday, October 30, 2013 11:48 AM To: ceph-users@lists.ceph.com Subject: [ceph-users] Red Hat clients Now that my ceph cluster seems to be happy and stable, I have been looking at different ways of using it. Object, block and file. Object is relatively easy and I will use different ones to test with Ceph. When I look at block, I'm getting the impression from a lot of Googling that deploying clients on Red Hat to connect to a Ceph cluster can be complex. As I understand it, the rbd module is not currently in the Red Hat kernel (and I am not allowed to make changes to our standard kernel as is suggested in places as a possible solution). Does this mean I can't connect a Red Hat machine to Ceph as a block client? ___ This message is for information purposes only, it is not a recommendation, advice, offer or solicitation to buy or sell a product or service nor an official confirmation of any transaction. It is directed at persons who are professionals and is not intended for retail customer use. Intended for recipient only. This message is subject to the terms at: www.barclays.com/emaildisclaimer<http://www.barclays.com/emaildisclaimer>. For important disclosures, please see: www.barclays.com/salesandtradingdisclaimer<http://www.barclays.com/salesandtradingdisclaimer> regarding market commentary from Barclays Sales and/or Trading, who are active market participants; and in respect of Barclays Research, including disclosures relating to specific issuers, please see http://publicresearch.barclays.com. ___ ___ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
Re: [ceph-users] Red Hat clients
If you were to run your Red Hat based client in a vm you could run run unmodified an unmodified kernel. if you are using rhel 6.4 then you get the extra goodies in the virtio-scsi qemu driver. On Oct 30, 2013, at 2:47 PM, wrote: > Now that my ceph cluster seems to be happy and stable, I have been looking at > different ways of using it. Object, block and file. > > Object is relatively easy and I will use different ones to test with Ceph. > > When I look at block, I’m getting the impression from a lot of Googling that > deploying clients on Red Hat to connect to a Ceph cluster can be complex. > As I understand it, the rbd module is not currently in the Red Hat kernel > (and I am not allowed to make changes to our standard kernel as is suggested > in places as a possible solution). Does this mean I can’t connect a Red Hat > machine to Ceph as a block client? > > ___ > > This message is for information purposes only, it is not a recommendation, > advice, offer or solicitation to buy or sell a product or service nor an > official confirmation of any transaction. It is directed at persons who are > professionals and is not intended for retail customer use. Intended for > recipient only. This message is subject to the terms at: > www.barclays.com/emaildisclaimer. > > For important disclosures, please see: > www.barclays.com/salesandtradingdisclaimer regarding market commentary from > Barclays Sales and/or Trading, who are active market participants; and in > respect of Barclays Research, including disclosures relating to specific > issuers, please see http://publicresearch.barclays.com. > > ___ > > ___ > ceph-users mailing list > ceph-users@lists.ceph.com > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com ___ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
[ceph-users] Red Hat clients
Now that my ceph cluster seems to be happy and stable, I have been looking at different ways of using it. Object, block and file. Object is relatively easy and I will use different ones to test with Ceph. When I look at block, I'm getting the impression from a lot of Googling that deploying clients on Red Hat to connect to a Ceph cluster can be complex. As I understand it, the rbd module is not currently in the Red Hat kernel (and I am not allowed to make changes to our standard kernel as is suggested in places as a possible solution). Does this mean I can't connect a Red Hat machine to Ceph as a block client? ___ This message is for information purposes only, it is not a recommendation, advice, offer or solicitation to buy or sell a product or service nor an official confirmation of any transaction. It is directed at persons who are professionals and is not intended for retail customer use. Intended for recipient only. This message is subject to the terms at: www.barclays.com/emaildisclaimer. For important disclosures, please see: www.barclays.com/salesandtradingdisclaimer regarding market commentary from Barclays Sales and/or Trading, who are active market participants; and in respect of Barclays Research, including disclosures relating to specific issuers, please see http://publicresearch.barclays.com. ___ ___ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com