From: Alex Elsayed <eternaleye@gmail.com>
To: ceph-devel@vger.kernel.org
Subject: Re: AIX client for ceph cluster?
Date: Sat, 04 May 2013 21:15:05 -0700 [thread overview]
Message-ID: <km4mc6$9ea$1@ger.gmane.org> (raw)
In-Reply-To: 001501ce47ce$236a09b0$6a3e1d10$@com.cn
dennis chen wrote:
> Hi All,
>
> Recently I want to use IBM AIX as the ceph client to take use of the
> cephFS and rbd service from ceph,
> but after some investigation, seem there's no support for AIX as the
> ceph client. Is there some clues about this? or is there some workaround
> that I can map a block device created
> from ceph cluster to the AIX system client?
If you have a reasonably-recent Linux box and are using the v1 metadata
format for RBD, you ought to be able to use the RBD kernel driver and re-
export the RBD device over some variant of SCSI (iSCSI, SCSI over FC, etc).
If you are using v2 metadata or don't have a recent Linux box, you may be
able to run a QEMU virtual machine, using the QEMU RBD support to bring the
disk into the VM and Linux's SCSI target code to export it as above.
Another possible solution would be to use qemu-nbd to bypass needing a
virtual machine, but I'm not at all sure of its performance/stability
characteristics, nor whether AIX has the ability to access NBD devices.
Note that all of these are almost certain to impair both resilience and
performance compared to accessing it directly, but there really isn't much
for AIX.
As far as CephFS goes, there is a FUSE client, although I suspect AIX
doesn't support FUSE. The only other option I can think of is to reexport it
as another filesystem from another machine - there's ongoing efforts to
support exporting CephFS via the Ganesha NFS server and the Samba SMB/CIFS
server.
prev parent reply other threads:[~2013-05-05 4:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5183625B.8080509@tnsoft.com.cn>
2013-05-03 7:16 ` AIX client for ceph cluster? dennis chen
2013-05-05 4:15 ` Alex Elsayed [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='km4mc6$9ea$1@ger.gmane.org' \
--to=eternaleye@gmail.com \
--cc=ceph-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.