9:52 a.m.
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?
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)?
Is there any plan to add for example in 3.6 another storage domain type
such as local posixfs, or some other type to be able to realize sort of
vSphere vSAN infrastructure for small/labs environments?
Gianluca
3:04 a.m.
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
Is there any plan to add for example in 3.6 another storage domain
type
such as local posixfs, or some other type to be able to realize sort of
vSphere vSAN infrastructure for small/labs environments?
Yes, so far we have a plan to add fiber channel support in 3.6 but maybe
we throw in even other popular storage backends, but nothing specific is
decided yet. You can file a feature request in our bugzilla [1]if you
have a good use case for some storage backend we will definitely
consider it.
Regards,
Jirka
[1] https://bugzilla.redhat.com/enter_bug.cgi?product=oVirt
Gianluca
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
10 a.m.
On Thu, Oct 23, 2014 at 9:04 AM, Jiri Moskovcak <jmoskovc(a)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?
Thanks
Gianluca
2:31 a.m.
On 10/23/2014 04:00 PM, Gianluca Cecchi wrote:
On Thu, Oct 23, 2014 at 9:04 AM, Jiri Moskovcak
<jmoskovc(a)redhat.com
<mailto:jmoskovc@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
2:34 a.m.
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(a)redhat.com
> <mailto:jmoskovc@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(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
7:12 p.m.
On 10/23/2014 05:00 PM, Gianluca Cecchi wrote:
On Thu, Oct 23, 2014 at 9:04 AM, Jiri Moskovcak
<jmoskovc(a)redhat.com
<mailto:jmoskovc@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?
we didn't add gluster due to concerns about how it works without replica
3. we're looking with the gluster team around making sure this works
together going forward
3711
days inactive
3714
days old
5 comments
3 participants
participants (3)
-
Gianluca Cecchi -
Itamar Heim -
Jiri Moskovcak