I haven't seen much talk about direct integration with oVirt. Obviously it
kind of comes down to oVirt being interested in participating. But, is the
only hold-up getting development time toward an integration or is there
some kind of friction between the dev teams?
We use Ceph Kraken with oVirt
Thank you for the clarification. I'm excited to give it a shot.
On Jul 25, 2017 3:24 AM, "David" wrote:
> My understanding was Cinder is needed to create/delete/manage etc. on
> volumes but I/O to the volumes is direct from the hypervisors. In theory
> you could lose your Cinder service and VMs
Cinder is used as a management gateway only while hypervisors (QEMU) are
directly communicating with Ceph cluster passing RBD volumes to VMs (without
mapping/mounting RBD on hypervisor level).
> 25 июля 2017 г., в 6:18, Brady Deetz написал(а):
>
> Thanks for pointing to some documentation. I'd
My understanding was Cinder is needed to create/delete/manage etc. on
volumes but I/O to the volumes is direct from the hypervisors. In theory
you could lose your Cinder service and VMs would stay up.
On 25 Jul 2017 4:18 a.m., "Brady Deetz" wrote:
Thanks for pointing to some documentation. I'd s
Thanks for pointing to some documentation. I'd seen that and it is
certainly an option. From my understanding, with a Cinder deployment, you'd
have the same failure domains and similar performance characteristics to an
oVirt + NFS + RBD deployment. This is acceptable. But, the dream I have in
my he
oVirt 3.6 added Cinder/RBD integration [1] and it looks like they are
currently working on integrating Cinder within a container to simplify
the integration [2].
[1]
http://www.ovirt.org/develop/release-management/features/storage/cinder-integration/
[2]
http://www.ovirt.org/develop/release-mana
Funny enough, I just had a call with Redhat where the OpenStack engineer
was voicing his frustration that there wasn't any movement on RBD for
oVirt. This is important to me because I'm building out a user-facing
private cloud that just isn't going to be big enough to justify OpenStack
and its admi
I was as much as told by Redhat in a sales call that they push Gluster
for oVirt/RHEV and Ceph for OpenStack, and don't have any plans to
change that in the short term. (note this was about a year ago, i
think - so this isn't super current information).
I seem to recall the hangup was that oVirt h
I haven't seen much talk about direct integration with oVirt. Obviously it
kind of comes down to oVirt being interested in participating. But, is the
only hold-up getting development time toward an integration or is there
some kind of friction between the dev teams?
