[ovirt-users] Self hosted engine and storage domain limitations
Jiri Moskovcak
jmoskovc at redhat.com
Fri Oct 24 06:31:43 UTC 2014
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?
--Jirka
> Thanks
> Gianluca
More information about the Users
mailing list