5:51 p.m.
----- Original Message -----
From: "Simon Grinberg" <simon(a)redhat.com>
To: "Shireesh Anjal" <sanjal(a)redhat.com>
Cc: users(a)ovirt.org, "Alon Bar-Lev" <alonbl(a)redhat.com>
Sent: Friday, March 22, 2013 5:46:01 PM
Subject: Re: [Users] Package installation error
----- Original Message -----
> From: "Shireesh Anjal" <sanjal(a)redhat.com>
> To: "Alon Bar-Lev" <alonbl(a)redhat.com>
> Cc: "Simon Grinberg" <simon(a)redhat.com>, users(a)ovirt.org
> Sent: Friday, March 22, 2013 8:34:40 AM
> Subject: Re: [Users] Package installation error
>
> On 03/22/2013 12:11 AM, Alon Bar-Lev wrote:
> >
> > ----- Original Message -----
> >> From: "Simon Grinberg" <simon(a)redhat.com>
> >> To: "Alon Bar-Lev" <alonbl(a)redhat.com>
> >> Cc: users(a)ovirt.org, "Sahina Bose" <sabose(a)redhat.com>,
"Dave
> >> Neary" <dneary(a)redhat.com>
> >> Sent: Thursday, March 21, 2013 7:40:17 PM
> >> Subject: Re: [Users] Package installation error
> >>
> >>
> >>
> >> ----- Original Message -----
> >>> From: "Alon Bar-Lev" <alonbl(a)redhat.com>
> >>> To: "Dave Neary" <dneary(a)redhat.com>
> >>> Cc: users(a)ovirt.org, "Sahina Bose" <sabose(a)redhat.com>,
"Simon
> >>> Grinberg" <simon(a)redhat.com>
> >>> Sent: Thursday, March 21, 2013 6:35:56 PM
> >>> Subject: Re: [Users] Package installation error
> >>>
> >>> Simon?
> >>>
> >>> ----- Original Message -----
> >>>> From: "Dave Neary" <dneary(a)redhat.com>
> >>>> To: "Sahina Bose" <sabose(a)redhat.com>
> >>>> Cc: "Alon Bar-Lev" <alonbl(a)redhat.com>,
users(a)ovirt.org
> >>>> 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.
So if I'll try to sum up (with reference to other emails on this
thread).
1. Default should be virt only
2. Keep the question and better explain what is the Gluster option
(preferable a link to the relevant page)
3. Add a config option to easily change the selection later
Need to think about the implication of the third option in case the
change conflicts with hosts/clusters that are already configured
other wise.
Example: Initial selection was Virt and now adding dual mode - always
OK
Example: Initial selection was Virt, no host in the setup, and now
changing to Gluster mode - OK
Example: Initial selection was Virt, Hosts already in the setup
installed in virt mode, and now changing to Gluster mode - What will
we do?
My take,
Config option can only set to dual mode, never the other way around.
This will save the need to add sophisticated logic
Sounds right?
Yes, but I am unsure that this is a single config option...
Maybe I did not understand you properly, but I think this should be an option in the UI.
And... if this option is in UI, then... why do we need anything at setup...? user can log
into the system and configure the cluster in any way he likes.
I am thinking into the future that when first login into the admin console there should be
some wizard, instead of performing this at setup time.
>
> >
> >>>> (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
> > Users(a)ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
>
>