[ovirt-users] Self-Hosted Engine Deploy - CephFS Not a Storage Option

Martin Sivak msivak at redhat.com
Tue May 16 08:32:13 UTC 2017


Hi,

I do not think there is any active effort to bring Ceph support to
hosted engine. Care to open an RFE in the bugzilla?

But we do not have any Ceph experts on the oVirt team at the moment so
I can't promise anything... Is there maybe a way to export Ceph using
some kind of proxy (multipath iscsi for example) that could be used
before the proper support is added?

Best regards

--
Martin Sivak
SLA / oVirt

On Mon, May 15, 2017 at 8:50 PM, Michael Poat <mpoat at bnl.gov> wrote:
> Hello,
>
> I currently have a 30 node ~200TB Raw Ceph storage primarily used as a
> CephFS POSIX Complaint storage for my enclave. Currently I am working on
> setting up a dual node High Availability ovirt 4.1 cluster. Considering
> avoiding any single points of failure, I would like to use CephFS as my
> storage domains and want to use the Self-Hosed Engine feature.
>
> When setting up the Self-Hosted Engine and reaching the steps for
> "Configuring Storage",  POSIX Compliant FS or CephFS is not an option...
>
> Prompt:
>
>  During customization use CTRL-D to abort.
>  Please specify the storage you would like to use (glusterfs, iscsi, fc,
> nfs3, nfs4)[nfs3]:
>
> Is there a work around for this or any future POSIX FS/CephFS Support for
> the Self-Hosted-Engine setup? I was able to create CephFS Domains within
> Ovirt and they work great. I was also wondering if it would be possible to
> migrate the self-hosted VM to the CephFS storage but this would require
> shutting down the VM itself, sort of a catch-22.
>
> Thanks,
>
> -Michael
>
>
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>


More information about the Users mailing list