[ovirt-users] Self hosted engine and storage domain limitations

[Jiri Moskovcak]

On 10/24/2014 08:31 AM, Jiri Moskovcak wrote:
> On 10/23/2014 04:00 PM, Gianluca Cecchi wrote:
>> On Thu, Oct 23, 2014 at 9:04 AM, Jiri Moskovcak <jmoskovc at redhat.com
>> <mailto:jmoskovc at redhat.com>> wrote:
>>
>>     On 10/22/2014 03:52 PM, Gianluca Cecchi wrote:
>>
>>         Hello,
>>         now with oVirt 3.5 there is also iSCSI with NFS as backed
>>         storage for
>>         Hosted Engine.
>>         What is the limitation about the storage domain? The
>> integration in
>>         setup scripts or due to storage type itself in engine mgmt?
>>
>>
>>     Both ;) The storage is managed via vdsm so whatever vdsm supports HE
>>     should support, but it requires some work in setup and the agent
>> code.
>>
>>
>>         What I mean is: if in some way one initially configures the
>>         engine on an
>>         external server (physical or virtual), could then be feasible
>>         migrating
>>         it "manually" in the oVirt environment (with backup/restore
>> steps)?
>>
>>
>>     - yes
>>
>>
>> Sorry,
>> do you mean that I can have a Gluster storage domain, with an external
>> engine and then backup/restore the egine inside a vm on this Gluster
>> environment as a self hosted engine?
>>
>
> - yes, moving the engine to the vm is not different from moving it to
> another physical machine, is it?
>

- altough gluster doesn't work well with the hosted engine, the 
migration is possible, but the actual usage of hosted engine on top of 
gluster is known to cause problems.

--Jirka

> --Jirka
>
>> Thanks
>> Gianluca
>
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users