On 03/22/2013 12:11 AM, Alon Bar-Lev wrote:
----- Original Message -----
From: "Simon Grinberg" <[email protected]>
To: "Alon Bar-Lev" <[email protected]>
Cc: [email protected], "Sahina Bose" <[email protected]>, "Dave Neary"
<[email protected]>
Sent: Thursday, March 21, 2013 7:40:17 PM
Subject: Re: [Users] Package installation error
----- Original Message -----
From: "Alon Bar-Lev" <[email protected]>
To: "Dave Neary" <[email protected]>
Cc: [email protected], "Sahina Bose" <[email protected]>, "Simon
Grinberg" <[email protected]>
Sent: Thursday, March 21, 2013 6:35:56 PM
Subject: Re: [Users] Package installation error
Simon?
----- Original Message -----
From: "Dave Neary" <[email protected]>
To: "Sahina Bose" <[email protected]>
Cc: "Alon Bar-Lev" <[email protected]>, [email protected]
Sent: Thursday, March 21, 2013 6:34:56 PM
Subject: Re: [Users] Package installation error
Hi,
On 03/19/2013 05:24 AM, Sahina Bose wrote:
You are right - Gluster 3.4 is only required to manage gluster
clusters.
Currently the question asked at setup is this :
"The engine can be configured to present the UI in three
different
application modes. virt [Manage virtualization only], gluster
[Manage
gluster storage only],
and both [Manage virtualization as well as gluster storage]"
where
both
is the default.
If this is confusing to the user, we can change this message.
Suggestions?
I would either:
(a) put "Virt" as the default, or
I would go for this one, this keeps backwards compatibility.
Is there an easy method to change this configuration later?
Yes, changing the cluster settings.
No - you can change the cluster settings (virt service/gluster service)
only if the application mode is "both". In virt only mode, the cluster
is virt only, and same with gluster-only. So if you want user to be able
to change the mode *after* installation, this config (ApplicationMode)
must be exposed in the engine-config tool.
(b) remove this question entirely - if someone is installing
oVirt,
assume they want to manage virt. If someone is installing
Gluster,
have
an option during the Gluster install to have the oVirt management
console.
We do want people to get exposed to the Gluster option.
If someone wants to manage both their Gluster bricks and their
virt
with
oVirt, I would make that a post-install option to oVirt - perhaps
with
an extra package to install (which would depend on the later
version
of
Gluster).
Cheers,
Dave.
On 03/19/2013 01:41 PM, Dave Neary wrote:
Hi,
On 03/19/2013 08:16 AM, Alon Bar-Lev wrote:
Now I am confused....
Do you or don't you need vdsm-gluster on your system?
Allow me to clarify.
There have been several messages from users since the oVirt
3.2
release asking why they need Gluster 3.4 pre-releases to run
oVirt.
My understanding is that you don't need Gluster 3.4 unless you
want to
manage a Gluster cluster with oVirt.
So my question is: are we sure that we are not leading users
wrong,
and confusing them during the installation & set-up process?
Thanks,
Dave.
--
Dave Neary - Community Action and Impact
Open Source and Standards, Red Hat - http://community.redhat.com
Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13
_______________________________________________
Users mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/users
