From: Mike Christie <mchristi@redhat.com>
To: Marat A Akhmetianov <vmm@solarcom.ch>, ceph-devel@vger.kernel.org
Subject: Re: Supporting CEPH with VMware
Date: Mon, 12 Feb 2018 12:27:30 -0600 [thread overview]
Message-ID: <5A81DC92.3090307@redhat.com> (raw)
In-Reply-To: <20180212091834.A111.48078FD1@solarcom.ch>
On 02/12/2018 12:18 AM, Marat A Akhmetianov wrote:
> Hi.
>
> I recently asked VMware Support if they officially support CEPH as a Storage. They told us no, but we can ask CEPH team if you are supporting CEPH with VMware solutions.
>
> So, I have several questions:
> 1) Does CEPH officially support VMware?
It does for iscsi, but there are limitations.
1. We do not yet support distributed PGRs, so the common setup of using
windows clustering in vmware VMs, is not supported.
2. There is a issue with vsphere HA when sharing a LUN between multiple
VMs and one loses their primary connection, but other VMs using the LUN
do not:
https://github.com/open-iscsi/tcmu-runner/issues/341
Setup instructions are here:
http://docs.ceph.com/docs/master/rbd/iscsi-initiator-esx/
> 2) What use cases for CEPH as a Storage are the best for VMware: NFS or iSCSI?
For iscsi, it is currently non initiator side HA type of workloads due
to the issues mentioned in #1.
> 3) Does CEPH with iSCSI work with VMware ESXi 6.0 and VMFS5 or only with ESXi 6.5 and VMFS6 (I found the link here that CEPH only supports ESXi 6.5 http://docs.ceph.com/docs/master/rbd/iscsi-target-cli/)?
Like the doc says 6.5 and vmfs 6.
> 4) Does iSCSI use case has the problem with 'Abort Task' loop that can cause targets to be restarted and some VMs crashing (here is the link http://lists.ceph.com/pipermail/ceph-users-ceph.com/2016-October/013610.html)?
>
With ESXi 6.5 and vmfs 6 and using the config options described in the docs
http://docs.ceph.com/docs/master/rbd/iscsi-requirements/
http://docs.ceph.com/docs/master/rbd/iscsi-initiator-esx/
and using gwcli then we have not seen it.
However, we are hitting the CAW/ATS as heartbeat related hang mentioned
on the target-devel list a while back:
https://www.spinics.net/lists/target-devel/msg12071.html
tcmu-runner issue for the same issue
https://github.com/open-iscsi/tcmu-runner/issues/315.
Internally, when using the ceph offloaded ATS/CAW feature or using the
esx side VMFS3/UseATSForHBOnVMFS5 workaround we have not seen the issue.
However, all the needed pieces for the offload feature are only in ceph
v13 and up, and our QE team has not completed testing the offload
feature with vmware yet.
next prev parent reply other threads:[~2018-02-12 18:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 6:18 Supporting CEPH with VMware Marat A Akhmetianov
2018-02-12 18:27 ` Mike Christie [this message]
[not found] ` <232b962964cf99b889630f913a433d8f@petasan.org>
2018-02-13 15:09 ` Marat A Akhmetianov
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=5A81DC92.3090307@redhat.com \
--to=mchristi@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=vmm@solarcom.ch \
/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.