[Engine-devel] Autorecovery feature plan for review

Laszlo Hornyak lhornyak at redhat.com
Tue Feb 14 12:16:58 UTC 2012



----- Original Message -----
> From: "Livnat Peer" <lpeer at redhat.com>
> To: "Yaniv Kaul" <ykaul at redhat.com>
> Cc: engine-devel at ovirt.org
> Sent: Tuesday, February 14, 2012 1:00:35 PM
> Subject: Re: [Engine-devel] Autorecovery feature plan for review
> 
> On 14/02/12 11:45, Yaniv Kaul wrote:
> > On 02/14/2012 09:59 AM, Yair Zaslavsky wrote:
> >> On 02/14/2012 09:48 AM, Omer Frenkel wrote:
> >>>
> >>> ----- Original Message -----
> >>>> From: "Yair Zaslavsky"<yzaslavs at redhat.com>
> >>>> To: engine-devel at ovirt.org
> >>>> Sent: Tuesday, February 14, 2012 9:20:10 AM
> >>>> Subject: Re: [Engine-devel] Autorecovery feature plan for review
> >>>>
> >>>> On 02/14/2012 08:59 AM, Itamar Heim wrote:
> >>>>> On 02/14/2012 08:57 AM, Livnat Peer wrote:
> >>>>>> On 14/02/12 05:56, Itamar Heim wrote:
> >>>>>>> On 02/13/2012 12:32 PM, Laszlo Hornyak wrote:
> >>>>>>>> Hi,
> >>>>>>>>
> >>>>>>>> Please review the plan document for autorecovery.
> >>>>>>>> http://www.ovirt.org/wiki/Features/Autorecovery
> >>>>>>> why would we disable auto recovery by default? it sounds like
> >>>>>>> the
> >>>>>>> preferred behavior?
> >>>>>>>
> >>>>>> I think that by default Laszlo meant in the upgrade process to
> >>>>>> maintain
> >>>>>> current behavior.
> > 
> > Why? Why not improve their user experience and provide them with
> > such
> > feature? Current behaviour sucks - as your system admin.
> > 
> 
> I don't have objections either way.
> Laszlo - let's update the wiki to upgrade by default to true, if
> we'll
> get good reason why not to upgrade to true then we can open it again
> for
> discussion.

So be it, I changed the wikipage.

> 
> 
> >>>>>>
> >>>>>> I agree that for new entities the default should be true.
> >>>>> i think the only combination which will allow this is for db to
> >>>>> default
> >>>>> to false and code to default to true for this property?
> >>>> Why can't we during upgrade process set to all existing entities
> >>>> in
> >>>> DB
> >>>> the value to false, but still have the column defined as
> >>>> "default
> >>>> true"?
> >>> why all the trouble? i think this field should be mandatory as
> >>> any
> >>> other field,
> >>> user has to specify it during the entity creation, right where he
> >>> provide the name and any other field for the new entity.
> >> Fine by me.
> > 
> > I'm not sure I see the reason a user would want to turn it off, on
> > a
> > per-object basis.
> > If it's in the 'Advanced' settings of a host/storage, fine, but
> > otherwise, it's just another cryptic feature to turn on/off.
> > Y.
> > 
> >>
> >>>>> _______________________________________________
> >>>>> Engine-devel mailing list
> >>>>> Engine-devel at ovirt.org
> >>>>> http://lists.ovirt.org/mailman/listinfo/engine-devel
> >>>> _______________________________________________
> >>>> Engine-devel mailing list
> >>>> Engine-devel at ovirt.org
> >>>> http://lists.ovirt.org/mailman/listinfo/engine-devel
> >>>>
> >> _______________________________________________
> >> Engine-devel mailing list
> >> Engine-devel at ovirt.org
> >> http://lists.ovirt.org/mailman/listinfo/engine-devel
> > 
> > _______________________________________________
> > Engine-devel mailing list
> > Engine-devel at ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/engine-devel
> 
> _______________________________________________
> Engine-devel mailing list
> Engine-devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/engine-devel
> 



More information about the Engine-devel mailing list