On 10/23/2014 05:00 PM, Gianluca Cecchi wrote:
On Thu, Oct 23, 2014 at 9:04 AM, Jiri Moskovcak jmosk...@redhat.com
mailto:jmosk...@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
On 10/23/2014 04:00 PM, Gianluca Cecchi wrote:
On Thu, Oct 23, 2014 at 9:04 AM, Jiri Moskovcak jmosk...@redhat.com
mailto:jmosk...@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
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 jmosk...@redhat.com
mailto:jmosk...@redhat.com wrote:
On 10/22/2014 03:52 PM, Gianluca Cecchi wrote:
Hello,
now with oVirt 3.5 there
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
On Thu, Oct 23, 2014 at 9:04 AM, Jiri Moskovcak jmosk...@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
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
6 matches
Mail list logo
